Windows Update Cleanup Stuck on Calculating? Fix in 5 Steps
Update cleanup stuck calculating? Same old bug since Windows 10 version 1909. I'll show you the quick fix, the normal fix, and the nuke-it fix.
Before You Do Anything – 30 Second Fix
First, the culprit here is almost always a corrupted Windows Update component store. Don't bother restarting the service or running SFC – that rarely helps when you're stuck on "calculating" in Disk Cleanup.
The quickest thing to try: just wait 5-10 minutes. I know, sounds dumb. But some older machines (especially spinning HDDs) genuinely take that long. If the progress bar moves even a pixel, let it finish. If it's dead still for 10 minutes, move on.
Also, check your System Reserved partition – if it's full, the cleanup gets into a loop. Open Disk Management (diskmgmt.msc) and look for a 100 MB or 500 MB partition. If it's flagged as full, skip to the advanced fix.
Moderate Fix – Run the Built-in Troubleshooter & Clear the Cache
If waiting didn't work, let's clear the cache manually. This takes about 5 minutes.
- Open an elevated Command Prompt (right-click Start > Command Prompt (Admin) or PowerShell (Admin)).
- Stop the update service:
net stop wuauserv - Stop the crypto service:
net stop cryptSvc - Stop the BITS service:
net stop bits - Stop the MSI installer:
net stop msiserver - Now rename the SoftwareDistribution folder – this is where the junk lives:
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old - Rename the Catroot2 folder too:
ren C:\Windows\System32\catroot2 Catroot2.old - Restart all services in reverse order:
net start msiserver net start bits net start cryptSvc net start wuauserv - Now run Disk Cleanup again – it should calculate instantly. Use cleanmgr /sageset:1 to enable the Windows Update Cleanup checkbox if it's missing.
This fix works about 80% of the time. If still stuck, move on.
Advanced Fix – The Nuclear Option (15+ Minutes)
This one's for when the cleanup tool is completely broken – usually after a failed feature update or a corrupted CBS (Component Based Servicing) store.
Step 1: Run DISM and SFC
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
Wait for DISM to finish – it can take 20 minutes on slow drives. A 3-5% hang is normal. If it fails with error 0x800f081f, you'll need your Windows ISO mounted (mount with right-click > Mount, then point DISM to the install.wim in the sources folder).
Step 2: Reset Windows Update Components Completely
If DISM passed, download the Windows Update Troubleshooter from Microsoft (KB4023814) and run it. But honestly, I've found it's faster to just use the Reset Windows Update Tool script from Microsoft's GitHub (search for "Windows Update PowerShell script").
Step 3: Manual Registry Cleanup (Only If You Know What You're Doing)
Open Regedit and delete these keys – but back up first:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing
Restart. This forces Windows Update to rebuild its state from scratch. You'll lose update history, but the stuck cleanup will disappear.
Step 4: Use Disk Cleanup with Direct Command-Line Switches
Skip the GUI. Run this in cmd:
cleanmgr /d C: /sagerun:1
This runs the cleanup with the saved settings from earlier. It bypasses the GUI calculation loop. If it still hangs, your Windows image is corrupt – time for an in-place upgrade repair.
Step 5: In-Place Upgrade Repair (Last Resort)
Download the Media Creation Tool from Microsoft, run it, select "Upgrade this PC now". Keep your files and apps. This takes about an hour but fixes 99% of stuck update cleanups.
What Causes This Bug?
Windows 10 build 1909 through 22H2 have a known issue where the Component Servicing (CBS) log grows huge – sometimes 2-4 GB. The cleanup tool tries to parse that log to calculate space, and it just chokes. Machines with little RAM (4 GB or less) hit this worse.
I've also seen it triggered by third-party antivirus (especially Norton and McAfee) locking the CBS files. Disable any real-time protection before running cleanup.
Quick Tips to Prevent This
- Run DISM /Online /Cleanup-Image /StartComponentCleanup once a month – this shrinks the CBS store.
- Keep your SSD with at least 20% free space. Full drives make cleanup slow.
- If you're on Windows 10 21H2 or 22H2, install the latest cumulative update – MS patched this in KB5005565.
That's it. Start with the 30-second wait, then the service restart, then the nuclear option. Skip the troubleshooter – it's a waste of time for this specific error.
Was this solution helpful?