Technical Anshu
Tutorials Blog
🔄 Windows Update Fix

Windows Update Stuck at One Percentage Reset It from CMD

An update frozen for hours, or one that downloads, fails and starts again in a loop — usually the update's own cache or its services are stuck. The technician's fix is a controlled reset: stop the services, clear the cache, start fresh.

✍️ Technical Anshu🪟 Windows 10 / 11⏱️ 5 minute fix
🎥 Service control commands like these run through the whole CMD toolkit video — watch it for the full set

Windows Update works using background services, mainly wuauserv (Windows Update) and bits (Background Intelligent Transfer Service), and it stores downloaded update files in a cache folder called SoftwareDistribution. If a download is interrupted or a cached file is damaged, every new attempt trips over the same bad cache — that is the loop most users get stuck in. The reset below stops the services, renames the old cache so Windows is forced to build a clean one, and starts the services again. Nothing about your personal files is touched. Open Command Prompt as Administrator (right-click Start → Terminal (Admin) or Command Prompt (Admin)) — service commands will not work without it — and type each command exactly, pressing Enter after each.

Settings — Windows Update
Windows Update
⚠️ Error encountered
Some update files are missing or have problems. We'll try to download the update again later.
Error code: (0x80070002)
👆 The problem, exactly as Windows shows it — a failed update with error code 0x80070002 (Settings panel recreated with the real Windows wording)
1

Stop the Update Services

  1. net stop wuauserv
  2. net stop bits
  3. net stop cryptsvc
  4. Each command should confirm the service was stopped. If one says the service is not started, that is fine — continue
Administrator: Command Prompt
C:\Windows\System32>net stop wuauserv The Windows Update service is stopping. The Windows Update service was stopped successfully.
👆 What a successful service stop looks like (CMD window recreated with the real output wording)
2

Rename the Old Update Cache

Renaming (instead of deleting) forces Windows to create a fresh cache while keeping the old one as a backup you can remove later:

  1. ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
  2. ren C:\Windows\System32\catroot2 catroot2.old
3

Start the Services Again

  1. net start wuauserv
  2. net start bits
  3. net start cryptsvc
  4. Restart the PC once, so everything settles into the new state
4

Run the Update Again ⭐

  1. Go to Settings → Windows Update → Check for updates
  2. The first check will take longer than usual — Windows is rebuilding its cache and re-downloading what it needs. That is expected, not a fault
  3. If the update now completes, you can delete the two .old folders after a few days to reclaim disk space

Stopping services, renaming system folders and restarting cleanly are everyday moves in the CMD toolkit. The full video shows the complete service-management and repair command set with live examples.

⚠️ If updates still fail after this reset: run the system file repair pair next — DISM /Online /Cleanup-Image /RestoreHealth followed by sfc /scannow — because damaged system files also break updates. And give a genuinely slow update real time first: some feature updates legitimately sit at one percentage for a long while on older hardware. Reset only when it is clearly stuck for hours with no disk activity.

🎥 Watch the Complete CMD Toolkit

Services, repair, network, disks and users — the complete technician toolkit demonstrated live in one video.

▶️ Watch Full Video
❓ Frequently Asked Questions

Is renaming SoftwareDistribution safe? Will I lose anything?

Yes, it is the standard reset technicians use. The folder only holds downloaded update files and update history records. Windows builds a new one automatically. Your documents, apps and settings are stored elsewhere and are not affected. You will lose the visible update history list, nothing more.

The rename command says "Access is denied". What is wrong?

Almost always, a service is still running and holding the folder — repeat step 1 and confirm all three stop commands succeeded, or restart the PC, open CMD as Administrator immediately, and run the stop and rename commands before opening Windows Update.

How long should I wait before deciding an update is really stuck?

If the percentage has not moved for 2–3 hours and the disk activity light is idle, treat it as stuck and do the reset. On slow hard disks, however, big feature updates can legitimately take a very long time — if the disk is busy, let it work.

This guide is based on the Technical Anshu CMD Toolkit video • Stuck on a step? Ask in the video comments — you will get a reply 🙏