Check Disk, System File Checker & Deployment Image Servicing and Management

Execute these tools in the following order: CHKDSK → DISM → SFC.

time /T
chkdsk
time /T 
DISM /Online /Cleanup-Image /RestoreHealth
time /T
sfc /scannow
time /T 

Do I have to run it regularly?

No!

chkdsk

• for SSDs: never run chkdsk routinely
• after unexpected shutdowns: always run chkdsk after a sudden power loss, crash, or forced reset.
• running chkdsk on a schedule (e.g., every 3-6 months) won't cause harm, it is mostly considered unnecessary maintenance

dism

• You do not need to run a DISM (Deployment Image Servicing and Management) scan on a regular schedule
• Never run DISM alone if you suspect deep corruption; pair it with the SFC (System File Checker) tool.

sfc

• some users proactively run it once a month as part of their update routine
• run sfc if you experience any of the following symtoms:
  • Frequent Windows crashes (Blue Screen of Death).
  • Windows features or system apps stop opening properly.
  • Update errors or failures during Windows Update.
  • Noticeable system sluggishness that you suspect is tied to the operating system.

Duration

device	date	command	start time	end time	duration
ARTEMIS22	08/06/2026	sfc /scannow	16:04	16:07	3 min.
ARTEMIS22	08/06/2026	DISM /Online /Cleanup-Image /RestoreHealth	15:36	16:04	28 min.
ARTEMIS22	08/06/2026	chkdsk	15:35	15:36	1 min.

device	date	command	start time	end time	duration
PERGOLESI	01/11/2020	sfc /scannow	18:34	18:39	5 min.
PERGOLESI	01/11/2020	DISM /Online /Cleanup-Image /RestoreHealth	18:39	18:43	4 min.

Issues

dism hangs at 62.3 percent

Solution 1: see https://answers.microsoft.com/en-us/windows/forum/all/dism-restorehealth-stuck-at-623/c3275aa3-0588-4e17-a0e8-eefb6ce1d512?page=3

► I had to enable the Background Intelligent Transfer Service, then it worked fine!

Solution 2: it's a false positive, because, in reality, Windows is doing a lot to restore the health of your Windows system

► Issue the following command in an elevated PowerShell window to follow the progress:

Get-Content C:\Windows\Logs\CBS\CBS.log -tail 10 -wait

source: https://learn.microsoft.com/en-us/answers/questions/3897970/dism-restorehealth-stuck-at-62-3-(info-resolved)

Error: 0x800f0915 - The repair content could not be found anywhere.

Ik kreeg op 06/06/2026 twee keer een blue screen op de HP (Lemmens), en voerde dus chkdsk, sfc en dism uit en kreeg bovenstaande foutmelding.

Geen oplossing gevonden, teruggegaan naar vorige AOMEI-image, zijnde SysBup 260418 (NewVPN and NanaZip), en opnieuw chkdsk, sfc en dism uitgevoerd, met succes dan:

E:\Tools>DISM /Online /Cleanup-Image /RestoreHealth
Deployment Image Servicing and Management tool
Version: 10.0.26100.5074
Image Version: 10.0.26200.8246
[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

Onderstaande geeft mijn pogingen min of meer weer, maar hebben dus niet tot een oplossing geleid:

DISM geeft na 100% het volgende weer:

Error: 0x800f0915

The repair content could not be found anywhere.
Check the internet connectivity or use the "Source" option to specify the location of the files that are required to restore the image. For more information on specifying a source location, see https://go.microsoft.com/fwlink/?LinkId=243077.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log 

Normaal haalt hij zijn info online, maar ook als ik een lokale source opgeef, komt dezelfde melding:

Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:"I:\Sources\Install.esd":6 /limitaccess

• limitaccess: voorkomt dat je PC Windows Update of WSUS contacteert om herstelbestanden te downloaden

Index-nr. (6 voor Pro) weet je als volgt:

Get-WindowsImage -ImagePath "I:\sources\install.esd"

Van de dism.log word je ook niet wijzer

2026-06-06 11:49:49, Info DISM DISM Package Manager: PID=7132 TID=16484 Error in operation: The repair content could not be found anywhere. (CBS HRESULT=0x800f0915) - CCbsConUIHandler::Error
2026-06-06 11:49:49, Error DISM DISM Package Manager: PID=7132 TID=17824 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f0915)
2026-06-06 11:49:49, Error DISM DISM Package Manager: PID=7132 TID=17824 The repair content could not be found anywhere. The image may be corrupted. Check the internet connection or try to restore the image using the /source option. - GetCbsErrorMsg
2026-06-06 11:49:49, Error DISM DISM Package Manager: PID=7132 TID=17824 Failed processing package changes with session options - CDISMPackageManager::Internal_ProcessChangesWithOptions(hr:0x800f0915)
2026-06-06 11:49:49, Error DISM DISM Package Manager: PID=7132 TID=17824 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f0915)
2026-06-06 11:51:37, Error DISM DISM Package Manager: PID=7132 TID=17824 The repair content could not be found anywhere. The image may be corrupted. Check the internet connection or try to restore the image using the /source option. - GetCbsErrorMsg
2026-06-06 11:51:37, Error DISM DISM Package Manager: PID=7132 TID=17824 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x800f0915)
2026-06-06 11:51:37, Error DISM DISM Package Manager: PID=7132 TID=17824 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f0915)
2026-06-06 11:51:37, Info DISM DISM Package Manager: PID=7132 TID=17824 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2026-06-06 11:51:37, Info DISM DISM Package Manager: PID=7132 TID=9884 Finalizing CBS core. - CDISMPackageManager::Finalize
2026-06-06 11:51:37, Info DISM DISM Manager: PID=9252 TID=7008 Closing session event handle 0x270 - CDISMManager::CleanupImageSessionEntry
2026-06-06 11:51:37, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.
2026-06-06 11:51:37, Info DISM DISM.EXE: 
2026-06-06 11:51:37, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->
2026-06-06 11:51:37, Info DISM DISM.EXE:

En van die cbs.log word je ook niet wijzer:

2026-06-06 19:16:43, Error CBS Session: 31258071_2171460150 failed to perform store corruption detect and repair operation. [HRESULT = 0x800f0915 - CBS_E_REPAIR_CONTENT_MISSING]

sfd

time /T DISM /Online /Cleanup-Image /RestoreHealth > C:\Temp\dism.log