Skip to main content
To repair corrupted system files on Windows Server, open an elevated Command Prompt and run DISM.exe /Online /Cleanup-image /Restorehealth first, then sfc /scannow. DISM repairs the Windows component store; SFC then uses that store to replace damaged system files. If DISM can’t download repair files (error 0x800f081f), point it at the install.wim on a Windows Server ISO with /Source and /LimitAccess.

Before you start

  • Use an elevated prompt: search Start for Command Prompt or PowerShell, right-click it and choose Run as administrator.
  • DISM downloads repair files from Windows Update by default, so the server needs internet access.
  • If Windows doesn’t start at all, see Windows Server not booting for the offline commands.

When to use SFC and DISM

Use them when Windows Update fails with corruption errors (for example 0x80073712 or 0x800f0831), when built-in tools or roles crash or won’t install, or after an unexpected shutdown left the system unstable. They don’t fix problems in your own applications or data.

How to run DISM and SFC

1

Check the component store (optional)

A quick check that reports whether corruption was already detected:
The result is healthy, repairable or non-repairable. For a full scan, use /ScanHealth instead; it takes several minutes.
2

Repair the component store

Wait for The restore operation completed successfully. It can take several minutes; don’t close the window.
3

Repair system files

Keep the window open until Verification 100% complete.
4

Restart

Restart the server, then retry what failed before.
The PowerShell equivalent of the DISM step is:

What the SFC result means

To see which files SFC found, extract its entries from the log to your desktop:

How to fix “The source files could not be found” (0x800f081f)

DISM couldn’t download the repair files, usually because Windows Update is blocked or broken. Use the Windows Server installation ISO for the same version and edition instead.
1

Mount the ISO

On a VPS, attach the ISO with mount custom ISOs, or download it inside Windows, right-click it and choose Mount. Note the drive letter, for example D:.
2

Find the right image index

Note the ImageIndex of your edition, for example Windows Server 2022 Standard (Desktop Experience).
3

Repair from the ISO

Replace 2 with your index:
/LimitAccess stops DISM from trying Windows Update.
4

Run SFC again

Run sfc /scannow and restart.
Use an ISO of the same Windows Server version (2019, 2022 or 2025) and edition as the installed system, and the index of that edition.

How to check it worked

Run sfc /scannow once more. It should end with Windows Resource Protection did not find any integrity violations. Then retry what failed before, such as Windows Update.

Frequently asked questions

Should I run SFC or DISM first?

Microsoft’s order is DISM first, then SFC. SFC repairs files from the component store, so the store must be healthy first.

Where is the DISM log?

DISM logs to C:\Windows\Logs\DISM\dism.log. Component servicing details are in C:\Windows\Logs\CBS\CBS.log.

Can I run SFC when Windows won’t start?

Yes, from the recovery environment: SFC /Scannow /OffBootDir=C:\ /OffWinDir=C:\Windows. The drive letter can differ there. See Windows Server not booting.

DISM still fails with a repair source. What now?

Check CBS.log for the failing package, then reinstall from a backup or rebuild the VPS after saving your data.

VPS and dedicated server guides

Every guide in this section.

Windows Update stuck or failing

Reset Windows Update components.

Windows Server not booting

Startup Repair and offline fixes.

Free up disk space

Clean the component store.

Mount a custom ISO

Attach a Windows Server ISO.

Checked against Microsoft Learn: Fix Windows Update corruptions, Repair a Windows image, Configure a Windows repair source and Microsoft Support: System File Checker on 4 November 2026. Commands were not tested on a live Windows server for this page.

Need Extra Help?

If you encounter any issues, our support team is ready to assist:

Save on Your Hosting

Ready to upgrade your hosting? Use code KB20 at checkout for 20% off your first order!

Last Updated: November 2026