How to Use DISM RestoreHealth to Repair a Corrupted Windows Image

What DISM RestoreHealth repairs and when you need it

DISM (Deployment Image Servicing and Management) is the servicing tool Windows itself uses; the /Cleanup-Image /RestoreHealth combination points it at the running installation's component store. It verifies every component against its manifest hash and pulls a fresh copy of anything damaged from Windows Update — silently, without reinstalling Windows and without the slightest interest in your files. SFC draws its “known good” copies from this same store, which is why the two tools form a ladder: DISM repairs the store, then SFC repairs the system files from it.

You need RestoreHealth when sfc /scannow reports “unable to fix some of them”, when Windows Update keeps failing with store-related codes, or after third-party “optimizers” have been near the servicing folders. It is also the right first move after chkdsk has repaired disk errors, since a disk that was returning bad data can leave corrupted components behind.

• DISM /Online /Cleanup-Image /CheckHealth — seconds; reports only the corruption flag left by earlier operations
• DISM /Online /Cleanup-Image /ScanHealth — thorough scan without repair, 10–30 minutes, can be inconclusive
• DISM /Online /Cleanup-Image /RestoreHealth — the full scan-and-repair pass, 10–40 minutes with downloads
• The switches /Source:wim:X:\sources\install.wim:1 /LimitAccess — repair from a mounted ISO instead of Windows Update
• The log lives at C:\Windows\Logs\DISM\dism.log — the first place to look on any failure

Running RestoreHealth step by step

Open an elevated console with Win+X → Terminal (Admin). CheckHealth first is a free sanity check: it takes seconds and reports whether a corruption flag is set at all. Then run DISM /Online /Cleanup-Image /RestoreHealth and let it work — the progress bar sits at 20 or 40 percent for long stretches, which is normal, and on a slow line the operation may honestly take the better part of an hour.

The operation ends with one of two verdicts: “The restore operation completed successfully”, or an error code, of which 0x800f081f is the classic — the source files needed were neither in the local store nor reachable through Windows Update. Do not confuse RestoreHealth with StartComponentCleanup: the latter only removes superseded versions to save space and repairs nothing. After a successful restore, reboot and run sfc /scannow to finish the repair chain.

The ISO fallback for 0x800f081f

When RestoreHealth cannot source files through Windows Update, point it at an ISO that matches your edition and build: download the Windows 11 image from Microsoft, mount it by double-clicking and note the drive letter. Which edition index you need is shown by dism /Get-WimInfo /WimFile:X:\sources\install.esd (or install.wim); then run DISM /Online /Cleanup-Image /RestoreHealth /Source:esd:X:\sources\install.esd:1 /LimitAccess with the correct index substituted — the /LimitAccess switch forbids falling back to Windows Update and forces the local source.

The mismatched ISO is the classic trap: an image of a different edition or a different build lets the restore complete on paper but leaves the store subtly wrong. Always match the edition (Home/Pro), the architecture and, ideally, the build number of the installed system. If even a matching ISO fails, the honest endpoint is an in-place repair upgrade with “Keep personal files and apps”, which rebuilds the store outright.

Questions and Answers

Read next

All articles · FAQ