Fix Windows Cumulative Update Stuck on Windows 11

Issue type: Windows Update | Applies to: Windows 10, Windows 11

If a windows cumulative update stuck message or frozen percentage stays on screen for a long time, do not force a restart immediately. Cumulative updates can sit at one number while Windows stages files, verifies packages, or prepares a rollback point in the background. The safest fix is to confirm whether the update is truly frozen, then repair the exact stage that stopped: download, install, restart, or final cleanup.

The percentage alone is not enough. A cumulative update stuck at 0 percent usually points to a download or service problem. A cumulative update stuck at 20–30 percent may still be staging files. A cumulative update stuck at 100 percent usually means Windows is trying to finalize the install, clean temporary files, or commit changes before showing the desktop again. Treat each stage differently instead of applying random update fixes.

Before you change anything, open Task Manager with Ctrl + Shift + Esc if Windows still responds. Check Disk, CPU, and Network activity. If disk activity is still moving, the update may be slow rather than broken. If everything has been idle for a long time, the steps below move from safe checks to deeper repair.

What to Do First: Windows Cumulative Update Stuck

1. Wait at least 30 minutes if the PC still shows disk activity or the fan is working.
2. Check Task Manager for Disk, CPU, and Network activity before assuming the update is frozen.
3. Confirm that the system drive has at least 15–20 GB of free space.
4. Use Pause updates and Resume updates if Windows is stuck before the restart phase.
5. Reset the Windows Update cache if the update freezes at the same point again.
6. Run SFC and DISM if the cache reset does not change the result.

Know Which Stage Is Stuck Before You Fix It

A stuck Windows cumulative update usually belongs to one of four stages. Matching the fix to the stage saves time and lowers the risk of damaging the installation.

1. Download stuck at 0 percent: Windows Update may not be reaching Microsoft servers, or update services may not be running correctly.
2. Install stuck before restart: Windows may be unpacking files, checking compatibility, or failing to stage the package.
3. Restart stuck at a percentage: Windows is applying system changes outside the normal desktop environment.
4. Stuck at 100 percent: Windows is often finalizing or cleaning up, and a forced restart here can be risky.

If your update never begins downloading, use the steps in our guide to Windows Update not downloading in Windows 11. If the update says it is ready but never moves forward, compare it with Windows Update pending install, because pending install is a different state from a frozen cumulative update.

Try Pause and Resume Before Running Commands

Pause and Resume is the cleanest first fix when Windows is stuck before the reboot phase. It forces Windows Update to re-check the current job without deleting update folders or touching system files.

1. Open Settings.
2. Go to Windows Update.
3. Select Pause updates.
4. Wait two to three minutes.
5. Select Resume updates.
6. Restart the PC and check for updates again.

If the update continues from where it stopped, the issue was probably a temporary update-service state. If it freezes at the exact same percentage again, the cached update files may be damaged.

Free Enough Space for the Update to Stage Files

Cumulative updates need working space. A PC can show a few gigabytes free and still fail because Windows needs room to download, unpack, verify, and stage files before applying them. Aim for at least 15–20 GB free on the system drive before deeper troubleshooting.

1. Open Settings > System > Storage.
2. Use Temporary files to remove Windows Update cleanup files, delivery optimization files, and temporary items.
3. Move large personal files to another drive if the system drive is nearly full.
4. Empty the Recycle Bin.
5. Restart Windows after freeing space.
6. Try the update again.

Do not use random “PC cleaner” tools for this. Windows Storage settings and Disk Cleanup are safer because they understand update-related files and avoid deleting active system components.

Reset the Windows Update Cache

If the same cumulative update gets stuck at the same point after a restart, reset the update cache. The SoftwareDistribution and catroot2 folders store downloaded update files and package signatures. If one of those files is damaged, Windows may keep retrying the same bad package.

Open Command Prompt as administrator and run:

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 wuauserv
net start bits
net start cryptsvc
net start msiserver

Restart the PC after the commands finish, then check for updates again. Renaming the folders is safer than deleting them because Windows will rebuild clean folders automatically while the old versions remain available temporarily.

Run SFC and DISM if the Update Still Freezes

If the cache reset does not help, the update may be stuck because Windows cannot repair or verify a component it needs. Run SFC first, then DISM, then SFC again.

sfc /scannow

When SFC completes, run:

DISM /Online /Cleanup-Image /RestoreHealth

Restart Windows, then run SFC once more:

sfc /scannow

This order matters. SFC checks system files. DISM repairs the component store that SFC uses as a repair source. Running SFC again after DISM gives Windows another chance to fix files that could not be repaired during the first pass.

Check for Update Service Problems

If Windows Update opens but never moves, one of the update services may be disabled or stuck. Open Services and check the main services before assuming the whole Windows installation is broken.

1. Press Windows + R.
2. Type services.msc and press Enter.
3. Find Windows Update and make sure it is not disabled.
4. Find Background Intelligent Transfer Service and make sure it is not disabled.
5. Find Cryptographic Services and make sure it is running.
6. Restart the PC and try Windows Update again.

Error codes such as 0x800705b4 can also point to update timeout behavior. If you see that code, check our guide for Windows Update error 0x800705b4 after completing the basic cache and service repair.

Install the Cumulative Update Manually

If Windows Update keeps freezing inside Settings, installing the same KB manually can bypass the stuck delivery stage. This is useful when the update downloads but the Windows Update interface will not finish the process.

1. Open Settings > Windows Update > Update history.
2. Copy the KB number of the failed cumulative update.
3. Open Microsoft Update Catalog in a browser.
4. Search for the KB number.
5. Download the package for your system, usually x64.
6. Run the downloaded MSU file and restart when prompted.

Manual installation does not fix every stuck update, but it is a good middle step before repair installs or resets. If the manual installer shows a different error code, use that code as the next diagnostic clue.

What to Do if It Is Stuck at 100 Percent

A Windows update stuck at 100 percent is frustrating because it looks finished but refuses to move forward. This stage is often cleanup, final verification, or final commit. Give it more time than you would give a stuck download, especially on slower drives.

If it stays at 100 percent for hours with no disk activity, the update may have hung during finalization. Our separate guide on why Windows Update is stuck at 100 percent covers that exact situation in more detail.

When a Forced Restart Is Reasonable

Forcing a restart should not be your first move. It is only reasonable when the PC has shown no disk activity, no network activity, and no visible progress for a long time. If Windows is still working, interrupting it can cause rollback loops or component damage.

1. Wait at least 30–60 minutes with no activity before deciding it is frozen.
2. Try Ctrl + Alt + Delete to see if Windows responds.
3. If the system is completely unresponsive, hold the power button for about 10 seconds.
4. Turn the PC back on and let Windows finish rollback or recovery.
5. After reaching the desktop, run sfc /scannow.

⚠️ Warning: Do not force-restart during active update installation just because the percentage has not changed for a few minutes. Force-restarting while Windows is writing system files can corrupt the installation and lead to startup repair or rollback problems.

Common Mistake

The most common mistake is assuming a cumulative update is broken because the percentage has not moved for 10 minutes; many updates pause visually while Windows continues staging files, so restarting too early can create the failure the user was trying to avoid.

Best Next Step

If the update remains stuck after waiting, freeing space, resetting the update cache, checking services, and running SFC/DISM, use Microsoft’s official troubleshoot problems updating Windows guide, then consider an in-place repair install before resetting the PC.

Frequently Asked Questions

How long should I wait before assuming a cumulative update is stuck?

Wait at least 30 minutes if there is disk activity. For slower PCs or large updates, waiting longer is safer than forcing a restart too early.

Why is my Windows cumulative update stuck at 0 percent?

That usually points to a download, network, firewall, VPN, or Windows Update service issue. Resetting update services and checking the connection are the best first steps.

Why is my update stuck at 100 percent?

That usually means Windows is trying to finish final verification, cleanup, or commit operations. Give it time first, then reset the update cache if it keeps happening repeatedly.

Will resetting the Windows Update cache delete my files?

No. It only affects temporary update files. It does not delete documents, apps, photos, desktop files, or personal settings.

Should I reset Windows if a cumulative update is stuck?

No, not as a first step. Try waiting, freeing space, resetting the cache, checking services, running SFC/DISM, and manual KB installation before considering a reset.