Disk Cleanup Stuck on Windows Update Cleanup Fixes Guide

If Disk Cleanup appears to be stuck for an extended time with no disk activity, treat it as a servicing issue; cancel it, reboot, and move to repair steps before trying again. Ignoring a stuck cleanup can leave the component store unhealthy and make later Windows updates fail. This guide shows how to tell a slow pass from a broken servicing stack, then uses the lowest-risk fixes first.

What Disk Cleanup stuck on Windows Update Cleanup usually means

Disk Cleanup is a built-in Windows storage cleanup tool that can hang while it processes system files, not just temporary files. The Windows Update Cleanup category removes older update components, so it may need to check the Component Store, or WinSxS, and sometimes the Windows Modules Installer service before it can delete anything.

On Windows 10, this often appears in the classic Disk Cleanup workflow. On Windows 11, similar cleanup work can overlap with Storage settings and temporary files, but Disk Cleanup still runs into the same servicing checks when old update files are involved.

Why the Windows Update Cleanup stage runs longer than basic temp-file cleanup

Basic temp-file removal is simple file deletion. Windows Update Cleanup must verify which packages are superseded, which files are still needed, and whether TrustedInstaller can safely remove them. That verification step is why this stage can be far slower than deleting browser cache or Recycle Bin contents.

What 0 bytes, 99%, and Not responding can mean in practice

0 bytes or 99% does not automatically mean failure. A large update backlog can sit there while Windows checks component relationships. The stronger warning signs are no disk activity, no CPU activity, and a window that says Not responding for a long stretch after earlier progress has stopped.

How Windows 10 and Windows 11 differ here

Windows 10 users more often see Disk Cleanup as the main path for this job. Windows 11 users may also see related cleanup under Settings > System > Storage > Temporary files. The underlying servicing behavior is still tied to update components, so the same repair steps apply when the cleanup stalls.

Likely causes, ranked from most to least common

Most often, the delay is just a large superseded update backlog. Less commonly, TrustedInstaller is still processing update files, the servicing stack or component store is damaged, or the update cache in SoftwareDistribution is corrupted after a failed install or reboot.

Large update backlog in the Component Store

A long list of old cumulative update files can make cleanup slow without being broken. This is especially likely after several months of skipped maintenance or a major feature update. The safest move is to wait long enough to see whether the drive is still working before forcing anything closed.

1. Open Disk Cleanup as administrator: Start > type Disk Cleanup > right-click > Run as administrator.
2. Select the system drive, usually C:.
3. Choose Clean up system files.
4. Leave Windows Update Cleanup selected and watch for disk light activity and Task Manager activity.

TrustedInstaller or Windows Modules Installer is still working

The Windows Modules Installer service, also called TrustedInstaller, handles many update component changes. If it is busy or delayed, Disk Cleanup can appear frozen while it waits on servicing operations. If the process is still active, closing it too soon can interrupt a normal cleanup.

1. Open Task Manager and check whether Disk Cleanup still has CPU or disk activity.
2. Open services.msc.
3. Find Windows Modules Installer.
4. Confirm it is not disabled. If it is stopped, leave it unless Windows reports a servicing problem.

Corruption in the servicing stack or component store

If SFC or DISM finds damaged system files, Windows may fail while checking update remnants. That is when image repair belongs before another cleanup attempt. Run SFC first, then DISM, then try Disk Cleanup again.

1. Open Command Prompt as administrator.
2. Run: sfc /scannow
3. After SFC finishes, run: DISM /Online /Cleanup-Image /RestoreHealth
4. Restart the PC and retry Disk Cleanup as administrator.

Update cache corruption in SoftwareDistribution

The SoftwareDistribution folder stores Windows Update cache data. If that cache is damaged, Disk Cleanup may freeze while trying to reconcile old update files. Use the Windows Update troubleshooter first, then reset the cache only after image repair steps have run.

net stop wuauserv
net stop bits
net stop cryptsvc
ren %windir%\SoftwareDistribution SoftwareDistribution.bak
ren %windir%\System32\catroot2 catroot2.bak
net start wuauserv
net start bits
net start cryptsvc

1. Open Command Prompt as administrator.
2. Run the reset commands above.
3. Restart the PC.
4. Open Disk Cleanup again and recheck Windows Update Cleanup.

Is it stuck or just slow? Use this check first

Use time, activity, and window state together. If it has been running for less than about 30 minutes and the disk is still busy, it is often just slow. If it has been running for a long time with no clear CPU or disk activity and the window says Not responding, treat it as stuck and move on.

When leaving it overnight is reasonable

Leaving it running overnight is reasonable only if the drive light or Task Manager shows ongoing activity. A common first-time mistake is seeing 99% and killing the process after ten minutes, even though Windows is still validating a large set of old updates.

Suppose a 250 GB system drive has months of cumulative updates queued for removal. The cleanup can sit near the end for a long time while it checks whether each package is still needed. That is slow, but not necessarily broken.

Can I close Disk Cleanup if it is stuck on Windows Update Cleanup?

Yes, but only after you have checked for real activity. If there has been no CPU or disk use for a long stretch and the window is frozen, closing it is reasonable. If it still shows active disk work, let it continue a bit longer before you stop it.

1. Open Task Manager and confirm whether Disk Cleanup still shows disk or CPU activity.
2. If it is idle for a long stretch, close the window or end the task.
3. Restart the PC.
4. Run Disk Cleanup again as administrator.

How do I fix Disk Cleanup hanging on Windows Update Cleanup?

Start with the least risky fix: run Disk Cleanup as administrator, then repair Windows files with SFC and DISM, and only then reset the update cache if needed. That order matters because a broken component store can make cache resets fail or leave the cleanup path unchanged.

1. Run Disk Cleanup as administrator from Start.
2. Run sfc /scannow in an elevated Command Prompt.
3. Run DISM /Online /Cleanup-Image /RestoreHealth after SFC completes.
4. Restart the PC.
5. If the issue returns, run the SoftwareDistribution reset commands.
6. Retry Disk Cleanup.

Use the Windows Update troubleshooter after image repair

The Windows Update troubleshooter can help if update components are misregistered, but it should come after SFC and DISM when a cleanup hang points to servicing trouble. On Windows 10, open Settings > Update & Security > Troubleshoot > Additional troubleshooters. On Windows 11, open Settings > System > Troubleshoot > Other troubleshooters.

Can I delete Windows Update Cleanup in Disk Cleanup?

Yes. That is the point of the checkbox. It removes old update components that Windows no longer needs. Do not delete random system folders by hand, and do not try to remove WinSxS contents manually. Disk Cleanup and TrustedInstaller handle the supported removal path.

1. Open Disk Cleanup as administrator.
2. Select the Windows drive.
3. Choose Clean up system files.
4. Select Windows Update Cleanup.
5. Continue with the cleanup only after Windows finishes scanning.

What if Disk Cleanup never finishes after updates?

If the hang repeats after reboot and repair steps, the next escalation is to check the servicing services and then use an alternate cleanup path. At that point, the issue is more likely tied to the update stack than to ordinary disk clutter.

1. Open services.msc and check Windows Update, BITS, Cryptographic Services, and Windows Modules Installer.
2. Make sure none are disabled by policy or stuck stopped.
3. Try Settings > System > Storage > Temporary files on Windows 11, or Settings > System > Storage on Windows 10.
4. If the same hang returns, run the Windows Update troubleshooter and then the reset commands above.

What if the Windows Update service is disabled by policy?

Check Computer Configuration > Administrative Templates > Windows Components > Windows Update > Configure Automatic Updates in Group Policy, or the registry value HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU\NoAutoUpdate. Policy-based disabling can block update servicing and make cleanup tools behave oddly until the policy is corrected.

Can WinSxS cleanup or DISM fix a stuck cleanup?

Yes, sometimes. DISM can repair the component store that Disk Cleanup depends on, and that often helps when the hang is caused by servicing corruption rather than size or time. It will not fix every case, but it is the right step before more invasive repair.

1. Run sfc /scannow.
2. Run DISM /Online /Cleanup-Image /RestoreHealth.
3. Restart Windows.
4. Run Disk Cleanup as administrator again.

Is it safe to restart while Disk Cleanup is stuck?

Yes, if the cleanup has clearly stopped making progress and the drive is idle. A restart is safer than forcing random folder deletion. It is not ideal to interrupt an active cleanup, so check Task Manager first and avoid restarting if Windows is still processing update files.

1. Confirm there is no disk activity.
2. Close Disk Cleanup if it is frozen.
3. Restart the PC normally.
4. Retry the cleanup after the system is back at the desktop.

Frequently asked questions

Why is Disk Cleanup stuck on Windows Update Cleanup?

It usually means Windows is checking old update components in the Component Store or WinSxS before it can remove them. If the drive still has activity, wait. If the window is frozen with no activity for more than 30 minutes, move to SFC, DISM, and then a cache reset.

How long should Windows Update Cleanup take in Disk Cleanup?

There is no fixed time. A small update cache may finish quickly, while a large superseded update backlog can take much longer than temp-file cleanup. The practical cutoff is activity: if CPU or disk work is still happening, keep waiting; if both are idle for a long stretch, treat it as stuck.

Can I close Disk Cleanup if it is stuck on Windows Update Cleanup?

Yes, if it has shown no disk or CPU activity for a long time and the window is frozen. Close it, restart Windows, and retry with Disk Cleanup opened as administrator. If the hang returns, continue with SFC, DISM, and update cache repair.

Can I delete Windows Update Cleanup in Disk Cleanup?

Yes. That checkbox is the supported way to remove old update remnants. Do not delete WinSxS or SoftwareDistribution folders manually. Use Disk Cleanup, then repair the servicing stack if the cleanup itself stalls.

Does this happen on Windows 10 and Windows 11?

Yes. Windows 10 commonly shows the issue in the classic Disk Cleanup flow, while Windows 11 can show similar behavior through Disk Cleanup or Storage settings. The repair order is the same: confirm activity, run as administrator, then use SFC, DISM, and update cache reset if needed.

Can WinSxS cleanup or DISM fix a stuck cleanup?

Often, yes. DISM repairs the component store that update cleanup depends on, and that can clear a servicing hang. If DISM finishes cleanly but Disk Cleanup still freezes, move to Windows Update cache repair and service checks rather than repeating the same scan.

Still not working?

If the cleanup still fails after SFC, DISM, a reboot, and a SoftwareDistribution reset, the next step is deeper Windows repair or vendor support. On managed PCs, policy or update servicing controls may be involved. On personal systems, an in-place repair install is the usual next escalation before a reset.

Prevention: keep Windows updated regularly so the Component Store does not build a very large backlog of superseded files. That lowers the chance that Windows Update Cleanup will need to process a huge queue at once.