Windows
Windows Update keeps failing
An update that fails, rolls back or loops at the same percentage is usually a blocked service, a corrupt cache or too little free space — not a broken PC.
Read before you start
Never cut an update short by holding the power button unless it has been stuck for more than an hour. A half-written update is what turns a slow PC into one that will not start.
This guide is for you if
- Windows Update shows the same error code every time
- The update installs to a percentage, then rolls back
- The PC keeps restarting with "reverting changes"
Step by step
Work top to bottom0 of 6 steps done
Clear the update cache
Open Services, stop the Windows Update service, delete everything inside C:\Windows\SoftwareDistribution\Download, then start the service again. That folder holds the half-downloaded package that keeps failing.
Run the Command Prompt as administrator or you will not be allowed to stop the service.
Make room on the drive
Updates need space to stage and unpack, and a feature update takes a lot of it. Free at least 20 GB before trying again.
Disk Cleanup > "Clean up system files" finds old update leftovers taking several gigabytes.
Repair the system files first
Run the DISM restore-health command, then System File Checker, and retry the update after the reboot. Both are built into Windows and take 10–20 minutes.
Keep the charger connected — a flat battery in the middle of this is worse than the original fault.
Reach for the standalone installer
Note the error code, then download that specific update from the Microsoft Update Catalog and install it by hand. This skips the update service entirely.
Check the code before forcing anything
A storage or driver error code means the update is exposing a hardware fault, not causing it. Fix that first or the next update fails in the same place.
Search the exact code with the build number — the first result is usually the right answer.
Know when to stop
If two attempts fail at the same point, bring it in. A feature update that will not complete is a symptom of a drive or driver problem that needs checking before another try.
Bring it in with the charger and your Microsoft account details if the PC is signed in with one.