Advertisement

Home Computer Hardware

How to Fix Windows Update Stuck at a Percentage and Get Your PC Updating Again

When a Windows update stalls at a certain percentage, it can be due to corrupted files or system conflicts. Start with easy fixes like restarting your PC and using the Windows Update Troubleshooter to resolve the issue safely.

5 min read
How to Fix Windows Update Stuck at a Percentage and Get Your PC Updating Again
Advertisement

When a Windows update gets stuck at a certain percentage, it means the process has encountered an issue preventing it from completing. Common causes include corrupted update files, conflicts with system services, or insufficient disk space. To fix this safely, start with simple steps like restarting your PC and running the Windows Update Troubleshooter, then move on to resetting update components if necessary.

How do I know if my Windows update is really stuck or just slow?

Windows updates can sometimes look frozen when they’re actually moving very slowly. To check, listen for hard drive or fan noise and watch the update percentage for any change after at least 30 minutes. You can also open Task Manager (Ctrl + Shift + Esc) and see if processes like "Windows Update" or "svchost.exe" are using CPU or disk resources. If there’s little system activity and the percentage hasn’t changed for hours, the update is likely stuck. But if resource use is steady and the percentage moves gradually, it’s best to wait until the update finishes.

What common problems cause Windows Update to freeze at a percentage?

Windows Update can freeze due to several reasons. Corrupted update files may stop installation from continuing. Problems with Windows services, such as the Windows Update service or the Background Intelligent Transfer Service (BITS), can interrupt the process. A lack of disk space can also prevent updates from completing. Occasionally, hardware issues like a failing hard drive or problematic drivers cause freezing during updates. Recognizing these causes helps decide which fix to apply first.

A Windows 11 laptop screen displaying a Windows Update progress stuck at a specific percentage.

Before you start

This guide applies to Windows 10 and Windows 11. You’ll need Administrator privileges to perform some steps. Before trying fixes, back up your important files to an external drive or cloud storage to prevent data loss. Avoid interrupting the update (such as force shutting down or unplugging your PC) unless it’s stuck for many hours. Start with the safest fixes first, and only proceed to more advanced steps if required.

What is the safest first step to try when Windows Update is stuck?

The safest first step is to restart your PC, which can clear temporary problems blocking updates. If the update resumes, let it finish. If not, run the Windows Update Troubleshooter: 1. Open Settings and go to Update & Security > Troubleshoot > Additional troubleshooters. 2. Select "Windows Update" and click "Run the troubleshooter." 3. Follow the prompts and apply any fixes suggested. This tool diagnoses and repairs common update issues without affecting your files.

How do I reset Windows Update components manually?

If basic fixes don’t work, resetting update components can remove corrupted data blocking progress. To do this with Administrator rights: 1. Open Command Prompt as Administrator (search "cmd", right-click, select "Run as administrator"). 2. Stop update services one by one:

net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
  1. Rename the folders that store update files:
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 Catroot2.old
  1. Restart the services:
net start wuauserv
net start cryptSvc
net start bits
net start msiserver
  1. Close Command Prompt and try Windows Update again. Renaming these folders forces Windows to recreate update data, often clearing stuck updates.

How can I verify that the update issue is resolved?

Check progress by opening Settings > Update & Security > Windows Update. If updates show progress or report successful installation, that’s a good sign. You can also view the update history to confirm the specific update completed. For more detail, open Event Viewer (search "Event Viewer") and go to Windows Logs > System. Look for recent Windows Update events showing success or failure. If updates install without freezing and no new errors appear, the problem is likely fixed.

What precautions should I take before attempting fixes on stuck Windows updates?

Always back up important data before you start any troubleshooting to avoid loss if something goes wrong. Avoid force shutting down or unplugging your PC during updates unless it’s stuck for many hours, as this can damage system files. Use built-in tools like the Update Troubleshooter first since they’re safe and non-destructive. If you perform manual resets, follow instructions carefully and monitor the process. If problems continue after several attempts, consider professional assistance to prevent further issues.

Conclusion

If your Windows update is stuck, first confirm whether it’s truly frozen or just slow. Restart your PC and run the Windows Update Troubleshooter to fix common issues. If needed, reset the update components manually to clear corrupted files. Always back up your data and avoid interrupting updates prematurely. Once the update moves forward normally, your system will be up to date again.

Frequently Asked Questions

Can I force restart my PC if the update is stuck?

Force restarting can help if the update hasn’t progressed for many hours, but it risks corrupting system files. It’s best to wait several hours and try safer fixes first before forcing a restart.

Will resetting Windows Update components delete my personal files?

No. Resetting update components only renames folders related to update data. Your personal files and applications remain unchanged.

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

This depends on the update size and your PC’s speed, but generally waiting 30 minutes to a couple of hours is reasonable before concluding the update is stuck.