Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
For most Windows 10 and Windows 11 repair attempts, open Command Prompt as administrator and run DISM first, then System File Checker (SFC):
DISM.exe /Online /Cleanup-Image /RestoreHealth
sfc /scannowWait for each command to finish. Microsoft recommends this order because DISM can repair the Windows component store that SFC relies on for replacement system files. A successful DISM operation does not guarantee that an unrelated crash, update, or application problem is fixed.
What DISM repairs—and what it does not
DISM stands for Deployment Image Servicing and Management. Windows includes DISM.exe in C:WindowsSystem32; you can run it from any Command Prompt location. It can service Windows images, including the currently running installation and offline images used in recovery or deployment.
For a normal desktop repair, DISM’s key role is checking and repairing the Windows image and component store. SFC has a different job: it checks protected Windows system files and replaces damaged files when possible. They are complementary tools, not interchangeable commands. DISM is not a general fix for every software, driver, malware, hardware, storage, or data-recovery problem.
#1 Best Overall
- Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
- Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
- Make the most of your screen space with snap layouts, desktops, and seamless redocking.
- Widgets makes staying up-to-date with the content you love and the news you care about, simple.
- Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)
See Microsoft’s DISM overview and System File Checker guidance.
Before running the commands
- Save open work.
- Open Start, search for Command Prompt, right-click it, choose Run as administrator, and approve the User Account Control prompt.
- For the standard online repair, keep the PC connected to the internet and allow access to Microsoft Update. DISM may need to obtain replacement files there.
- Let the operation complete. It can take several minutes; a slow-moving progress display alone does not mean it has failed.
If you get “Access is denied,” first check that the shell is elevated. If it persists, investigate the specific error and servicing logs rather than changing permissions blindly.
The standard DISM repair command
DISM.exe /Online /Cleanup-Image /RestoreHealthDISM.exestarts the servicing utility./Onlinetargets the Windows installation currently running./Cleanup-Imageselects image and component-store servicing operations./RestoreHealthscans for component-store corruption and attempts to repair it.
This is the usual starting point when your goal is repair. You do not have to run /CheckHealth or /ScanHealth first.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Choosing a DISM health command
| Command | What it does | When to use it |
|---|---|---|
DISM.exe /Online /Cleanup-Image /CheckHealth |
Checks whether corruption has already been flagged and whether it is considered repairable. It does not perform the full scan. | For a quick status check. |
DISM.exe /Online /Cleanup-Image /ScanHealth |
Performs a more extensive scan of the component store. It may take several minutes. | When you want to diagnose corruption before repairing. |
DISM.exe /Online /Cleanup-Image /RestoreHealth |
Scans for corruption and attempts repair automatically. | For the normal repair workflow. |
For a diagnostic-first sequence, run these commands in order, waiting for each one to finish:
DISM.exe /Online /Cleanup-Image /CheckHealth
DISM.exe /Online /Cleanup-Image /ScanHealth
DISM.exe /Online /Cleanup-Image /RestoreHealth
sfc /scannowThe first two commands are optional diagnostics. If you simply want to attempt repair, go straight to /RestoreHealth. Microsoft documents these image-repair options in its Windows image repair guidance.
Run SFC after DISM
After DISM reports that the operation completed successfully, run:
sfc /scannowWait until SFC reaches 100 percent and displays a result. Common outcomes include:
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsRank #2
- MICROSOFT WINDOWS 11 PRO (INGLES) FPP 64-BIT ENG INTL USB FLASH DRIVE
- “Windows Resource Protection did not find any integrity violations.” SFC found no damaged protected system files.
- Corrupt files were found and repaired. The exact wording can vary by Windows version; restart if appropriate and check whether the original symptom has cleared.
- Corrupt files were found but some could not be repaired. Review the SFC result and CBS log, confirm DISM completed, and consider a suitable repair source or further Windows recovery options.
- “Windows Resource Protection could not perform the requested operation.” Microsoft recommends trying the SFC scan in Safe Mode.
For the supported consumer sequence and SFC result guidance, see Microsoft’s System File Checker article.
If RestoreHealth cannot find source files
DISM needs a usable repair source. Normally it can use Windows Update; if that source is unavailable or cannot provide the required files, specify a known-good Windows repair source:
DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:RepairSourceWindows /LimitAccessReplace C:RepairSourceWindows with the actual path to the Windows files that will serve as the repair source.
/Source:<path>tells DISM where to look for replacement files./LimitAccessprevents DISM from contacting Windows Update. Use it when you intend to rely on the specified source; if that source is incomplete or incompatible, repair can fail.
A network example is:
DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:\ServerNamec$Windows /LimitAccessMicrosoft specifies that the source computer in this example should run the same operating-system version. As a practical compatibility precaution, choose repair files that also match the target’s architecture, edition, language, and build as closely as possible. Do not use a random ISO, copied DLL collection, or third-party repair package as a source. Microsoft describes supported source options and syntax in its image repair documentation and Windows Update corruption guidance.
Recommended Free Tools
Common errors and next steps
Error 0x800f081f or source files not found
This commonly means DISM could not locate the required repair files in its available source. Restore Windows Update connectivity and retry, or provide a valid, compatible source with /Source. Microsoft discusses 0x800f081f and related servicing errors.
Windows Update is unavailable or broken
If DISM cannot retrieve files online, use a known-good local or network source. A source can come from suitable Windows media or another working Windows installation; the correct choice depends on the repair scenario. Use /LimitAccess when you want to prevent fallback to Windows Update.
Access denied
Confirm Command Prompt was opened with Run as administrator. If it was, note the exact error and inspect servicing logs or the affected object before taking further action. Avoid broad permission changes that may weaken system security or damage servicing.
Rank #3
- STREAMLINED & INTUITIVE UI, DVD FORMAT | Intelligent desktop | Personalize your experience for simpler efficiency | Powerful security built-in and enabled.
- OEM IS TO BE INSTALLED ON A NEW PC with no prior version of Windows installed and cannot be transferred to another machine.
- OEM DOES NOT PROVIDE SUPPORT | To acquire product with Microsoft support, obtain the full packaged “Retail” version.
- PRODUCT SHIPS IN PLAIN ENVELOPE | Activation key is located under scratch-off area on label.
- GENUINE WINDOWS SOFTWARE IS BRANDED BY MIRCOSOFT ONLY.
DISM succeeds, but the symptom remains
Successful completion means the requested servicing operation completed; it does not prove the original problem was caused by component-store corruption. Review SFC’s result, retry Windows Update if relevant, and investigate recently installed drivers or software. Event Viewer, application-specific logs, and hardware or storage diagnostics may be more appropriate when symptoms point in those directions. Protect your data before considering a repair installation, reset, or reinstall.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Read results and verify a repair
| Result | Meaning and next step |
|---|---|
| Image reported healthy | The selected check did not identify repairable corruption. Investigate the original symptom’s likely cause rather than repeating repair commands without a reason. |
| Corruption is repairable | Run /RestoreHealth to attempt repair. |
| Corruption is reported as non-repairable | Microsoft’s guidance for image servicing says a non-repairable image may need to be discarded and recreated. That is particularly relevant to offline servicing; it is not an instruction for every consumer to wipe a working PC. Back up important data and assess repair installation, reset, or reinstall options carefully. |
| Restore completed successfully | Run sfc /scannow, restart if appropriate, and retest the original issue. |
| Required source files could not be found | Restore access to a usable Windows Update source or provide a valid compatible repair source. |
For additional verification, run:
DISM.exe /Online /Cleanup-Image /ScanHealthIf the issue persists, examine the servicing logs. They are typically at:
%windir%LogsCBSCBS.log
%windir%LogsCBSCBS.persist.logTo open the main log from Command Prompt, run notepad %windir%LogsCBSCBS.log. The log can contain a large amount of servicing detail; not every error is explained by one obvious line. Microsoft identifies CBS.log as a useful record of servicing issues in its Windows Update repair guidance.
Advanced: PowerShell and offline images
Administrators and scripts can use the PowerShell Repair-WindowsImage cmdlet as an alternative:
Repair-WindowsImage -Online -RestoreHealthWith a source:
Repair-WindowsImage -Online -RestoreHealth `
-Source "C:RepairSourceWindows" `
-LimitAccessIts parameters include health checks, repair, source, and access control. See Microsoft’s Repair-WindowsImage reference.
Offline servicing is for advanced recovery, deployment, or mounted images—not the default approach for an ordinary desktop user. In an offline command, /Image: replaces /Online and must point to the Windows image being serviced:
Dism /Image:C:offline /Cleanup-Image /ScanHealth
Dism /Image:C:offline /Cleanup-Image /RestoreHealth /Source:C:RepairSourceWindowsUse the actual mounted Windows path, not an arbitrary folder. For deployment work involving a mounted image that became corrupted during modification, Microsoft also documents:
Dism /Cleanup-MountpointsThis cleans up mount points; it does not unmount images that are still mounted and does not delete images recoverable with /Remount-Image. Consult the image repair reference before using mount-management commands.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
