Common issues during update installation on Windows
A Windows update that is stuck, failing, or showing an error usually needs a basic cleanup first: restart the PC, free some disk space, and try the update again. Many update problems are temporary and clear up after a clean reboot or a second attempt. If the same failure keeps coming back, the cause is more likely a driver conflict, damaged update files, or corrupted system files.
Before you start
This applies to Windows 10 and Windows 11 update installs, including both cumulative updates and feature updates. Most of the fixes below can be done from a standard account, but resetting Windows Update components and running DISM or sfc need Command Prompt opened as Administrator.
A restart is part of the troubleshooting process, and some steps may briefly stop update services. You do not need to back up the whole PC just to try the first fixes, but if you are about to change update components or repair system files, make sure your important files are saved first.
Before you start, check two safe things: that the PC has enough free space on C: and that Windows is not still actively installing in the background.
What the update is doing when it looks frozen
A Windows update can look frozen even when it is still working. Common signs are a percentage that sits at 0%, 30%, or 99% for a long time, a PC that restarts more than once, a black or blue screen with “Working on updates,” or a vague message like “Something didn’t go as planned.” Sometimes the computer seems idle, but the storage light still blinks or the fan keeps running, which often means the installer is still busy.
If the exact message varies, the error code matters more than the wording.
The part that matters is whether the screen has been unchanged for a short while or for hours. A long pause at 99% during install can be normal, especially on older hardware. A full freeze is more likely if the progress never changes, the mouse does nothing, and the machine never moves past the same screen after a long wait. If you see an error code, that is more useful than the wording. Codes usually point to the next step instead of leaving you guessing.
If the system keeps rebooting and then lands back on the desktop without any sign of the update, Windows may have rolled the update back because something failed during install.
When this problem usually happens
Update failures are more likely when the PC is short on storage, the internet drops during a download, or the machine already has a pending restart waiting in the background. Active antivirus tools can also get in the way, especially if they hook into file changes while Windows is replacing system components. Older drivers, especially for storage, graphics, or network hardware, can add another layer of trouble.
Say you left your laptop with only a few gigabytes free, then started a large feature update on Wi‑Fi that briefly cut out. Windows may download part of the update, pause, and then fail while it is trying to unpack files. Or imagine you installed a driver yesterday and never restarted. The next update may stall because Windows is trying to finish two different setup processes at once.
A temporary hiccup usually behaves like a one-time failure: it pauses, rolls back, or succeeds on the second try. A deeper issue tends to repeat the same code or stop at the same stage every time, even after a restart.
The first fixes to try in order
Start with the least risky steps first. You do not need to reset Windows for most update problems.
- Save your work and restart the PC.
A clean restart clears pending tasks and can finish a half-completed install.
If Windows says it is still installing, give it time before forcing a restart. If the screen has truly not changed for a long time, a restart is reasonable.
- Free some storage space.
Open File Explorer and check the system drive, usually C:. Remove temporary files, empty the Recycle Bin, and move large downloads or videos off the drive if space is tight. Windows updates often fail when the system drive is nearly full.
- Disconnect unnecessary peripherals.
Unplug printers, external drives, docks, and other accessories you do not need for the update. Leave only the keyboard, mouse, and power cable if you are on a laptop. A flaky USB device can interfere with setup.
- Try Windows Update again.
Open Settings and check for updates after the restart.
Settings > Windows Update > Check for updatesIf the update starts and finishes, the issue was probably temporary. If it fails again with the same code, you are probably past the point of a simple retry.
- Run the built-in Windows Update troubleshooter.
This is a safe next step because it checks common update settings and service problems without changing your personal files.
Settings > System > Troubleshoot > Other troubleshooters > Windows Update > RunIf it finds and fixes something, try Windows Update again right away. If it says it could not identify the problem, that does not mean nothing is wrong; it just means you may need a more targeted fix.
- If the same failure keeps happening, reset the Windows Update components.
This is still a normal repair step, but it is more invasive than the options above because it rebuilds update-related services and cache files. Use it after the basic checks, not before them.
Run Command Prompt as Administrator and enter the following commands one by one:
net stop wuauserv
net stop bits
net stop cryptsvc
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start msiserver
net start cryptsvc
net start bits
net start wuauservIf the rename commands succeed, Windows creates fresh update cache folders the next time it checks for updates. If one of the stop commands fails because a service is not running, that is usually fine. If the update still fails after this, the issue may be outside Windows Update itself, such as a bad driver or corrupted system files.
- If failures continue, look for system-file corruption.
Run Command Prompt as Administrator and check the system image and protected files.
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannowIf these commands complete and report repairs, restart and try the update again. If they report problems they could not fix, that points to a deeper system issue that may need more targeted repair before the update will install.
If you need the exact failure code, open Settings > Windows Update > Update history, then expand the failed entry. The code there is the one to use when searching for the real cause, because the short message on the main screen is often too vague.
How to know the update actually worked
The update is not done just because the progress bar disappears. Confirm it in three places.
First, check Windows Update history and make sure the failed entry is gone or shows as successful. Second, open winver to verify the Windows version changed if you were installing a feature update.
winverIf the About Windows box shows the expected version and build, the feature update likely installed correctly. Third, restart the PC once more. If it boots normally without showing the same install screen again, that is a good sign the update finished and is not stuck in a loop.
If the same update still appears in history as failed, or Windows keeps offering it again right after a reboot, the install did not really stick. In that case, use the error code from Update history and go after the specific cause instead of retrying blindly.
How to avoid the same problem next time
Keep enough free space on the system drive before starting a large update. If space is tight now, clear it before Patch Tuesday or before a feature upgrade appears. A stable power source matters too, so plug in a laptop during installation.
Use a reliable network connection for big updates. If possible, avoid hopping between weak Wi‑Fi networks while Windows is downloading. Restart the PC regularly so pending changes do not pile up for weeks at a time. That one habit prevents a lot of strange update behavior.
Do not force a shutdown during the install unless the machine has truly stopped responding for a long time. Interrupting setup can leave Windows with half-written files and make the next attempt harder. If you have a third-party antivirus or other low-level system tool, keep in mind that it may interfere during major updates, so if a pattern of failures starts right after you install such software, that is worth checking.
Conclusion
If the update still fails after the basic checks, stop repeating the same attempt and work from the error code in Update history. If Windows is having repeated server-side issues, pause and try again later, but keep the code and the failed update name so you can pick up from there.
Frequently Asked Questions
How long should I wait before calling a Windows update frozen?
If the screen is unchanged for a short time, wait. If it has stayed on the same percentage or the same restart screen for a long time and there is no sign of disk activity, a restart is reasonable.
Should I force the PC off if Windows Update is stuck?
Only if it appears truly hung for a long time and is not responding at all. Forcing power off can break a bad install loop, but it can also make the next attempt harder.
Where do I find the Windows update error code?
Open Settings > Windows Update > Update history and expand the failed item. That entry usually shows the code you need, such as a numeric or hexadecimal failure code.