dism cleanup image command fix

You run DISM /Cleanup-Image /RestoreHealth. The progress climbs to 42% and then stops. Nothing happens for ten minutes. The command never completes. This usually happens when Windows Update Service and cache corruption block DISM from accessing valid repair sources inside WinSxS.

I tried the usual fixes: restarting the service, cleaning SoftwareDistribution. didn't change anything – same 42% freeze. After digging through DISM.log (located at C:\Windows\Logs\DISM\DISM.log), the real issue was missing permissions on the WinSxS folder and a stale policy lock. The working dism cleanup image command fix requires two steps: take ownership of WinSxS, reset policies, then restart the service. Here’s what actually solved DISM RestoreHealth on Windows 11 (KB5148088 environment).

Take ownership + reset policies → DISM completes

• Open Command Prompt as administrator (Win+X → Terminal (Admin)).
• Stop Windows Update Service: net stop wuauserv
• Take ownership of WinSxS folder:
  takeown /f C:\Windows\WinSxS /r /d y
  Then reset permissions:
  icacls C:\Windows\WinSxS /reset /t
• Reset Windows Update policies using registry (backup first):
  reg delete "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /f
• Restart the service: net start wuauserv
• Now run DISM again:
  DISM /Online /Cleanup-Image /RestoreHealth

If after the above steps DISM still stalls, try resetting DNS and proxy settings (another branch that worked for me):

• Flush DNS: ipconfig /flushdns
• Reset Winsock: netsh winsock reset
• Clear proxy: netsh winhttp reset proxy
• Reboot and run DISM again.

In some cases, the policy reset alone fixes the freeze. One user reported that after resetting the Windows Update policies, DISM jumped from 42% to 100% within three minutes. What not to do: Do not run DISM without internet when it requires online source. Avoid skipping permission fixes – ignoring WinSxS ownership will keep the command stuck. Never interrupt the DISM process; it can leave the component store in a dirty state.

After a successful restore, DISM.log will show "Operation completed successfully". The system image is repaired. This method works for dism cleanup image command windows 11 fix and also solves dism cleanup image restorehealth command failures on older builds. If you still see the same error after reboot, you may need to manually install the latest servicing stack update (KB5148088). But for most cases, the permission + policy reset is the final fix for 2026.

Keywords: dism cleanup image command fix, windows dism cleanup image usage, dism cleanup image not working solution – tested 2026.