Run PowerShell as an administrator, use DISM to repair the Windows image, then run SFC to fix system files. That is the main recipe for repairing Windows 11 without wiping your apps, files, and sanity. DISM is Microsoft’s built-in tool for servicing and repairing Windows images [source: Microsoft].
TLDR: Open Windows Terminal as admin. Run DISM /Online /Cleanup-Image /RestoreHealth, then run sfc /scannow. For example, if Windows Update keeps failing with error 0x800f081f, this repair often fixes the damaged component store behind it. Expect about 15 to 45 minutes, depending on your drive and how grumpy Windows feels today.
What this repair actually does
Windows 11 has a hidden toolbox. Two tools matter most here:
- DISM: Repairs the Windows component store. Think of it as the parts warehouse.
- SFC: Checks active system files and replaces broken ones.
If the warehouse is bad, SFC may fail. So run DISM first. Then run SFC. Simple. Boring. Effective.
This does not reinstall Windows. It does not remove your personal files. It should not remove your apps either. Still, back up anything you cannot lose. Computers enjoy teaching painful lessons.
Step 1: Open PowerShell as administrator
- Right-click the Start button.
- Click Terminal Admin or Windows PowerShell Admin.
- Click Yes when Windows asks for permission.
You need admin rights. Without them, Windows will shrug and block the repair. Honestly, it feels like Windows waits until you are busy before asking for three permission clicks.
Step 2: Do a quick health check
Start with this command:
DISM /Online /Cleanup-Image /CheckHealth
This is the quick test. It checks if Windows already knows the image is damaged. It may finish in seconds.
If it says no corruption was detected, great. But do not stop yet if your PC still acts weird.
Step 3: Run the deeper scan
Now use:
DISM /Online /Cleanup-Image /ScanHealth
This scan is slower. It checks the component store more deeply. It may sit on one percentage for a while. The famous pause around 62.3% can look frozen. It usually is not.
Expect to waste time staring at a number that refuses to move. Give it at least 10 to 20 minutes before assuming it is stuck.
Step 4: Repair the Windows image
Now run the main command:
DISM /Online /Cleanup-Image /RestoreHealth
This tells Windows to repair the component store. By default, it may use Windows Update to get clean files. So keep the internet on.
If it finishes with “The restore operation completed successfully”, you are in good shape.
Step 5: Run SFC after DISM
Now repair the live system files:
sfc /scannow
SFC may say one of these:
- No integrity violations: Nice. Nothing broken was found.
- Found corrupt files and repaired them: Even better. It fixed stuff.
- Found corrupt files but could not fix some: Annoying. Run DISM and SFC again.
Yes, running them twice can help. Windows repair is not always elegant. Sometimes it is more like tapping a vending machine until the snack drops.
PowerShell version of the DISM repair
If you prefer PowerShell-style commands, use this:
Repair-WindowsImage -Online -CheckHealth
Then:
Repair-WindowsImage -Online -ScanHealth
Then:
Repair-WindowsImage -Online -RestoreHealth
These commands reach the same repair system. They just look more like native PowerShell.
If DISM says source files are missing
Sometimes DISM cannot download clean files. You may see 0x800f081f or a message about missing source files. This is where a Windows 11 ISO can help.
- Download a matching Windows 11 ISO from Microsoft.
- Right-click it and choose Mount.
- Check the new drive letter, such as E:.
- Look inside
sourcesforinstall.wimorinstall.esd.
If you have install.wim, try:
DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:E:\Sources\install.wim:1 /LimitAccess
If you have install.esd, try:
DISM /Online /Cleanup-Image /RestoreHealth /Source:ESD:E:\Sources\install.esd:1 /LimitAccess
Change E: to your real ISO drive letter. That little detail matters. Windows will not guess for you, because of course it will not.
What to do after the repair
- Restart your PC.
- Run Windows Update again.
- Open your problem app and test it.
- Check if crashes, failed updates, or strange errors are gone.
You can also check DISM logs here:
C:\Windows\Logs\DISM\dism.log
Most people will not need that file. It is useful when the repair fails and you want the exact error.
When this is worth trying
Use this method when Windows 11 feels broken but still boots. It is great for failed updates, missing system files, broken optional features, odd crashes, and strange built-in app problems.
If your drive is dying, this will not save it. If malware is active, clean that first. If Windows cannot boot at all, you may need recovery tools.
For many everyday Windows 11 messes, though, PowerShell and DISM are the sweet spot. No reinstall. No fresh setup marathon. Just a repair pass, a restart, and hopefully fewer weird errors.




