Use the online tools when Windows starts and the evidence points to protected-file or component-store damage. The retained reports include Windows Update failures, CoreMessaging.dll crashes and a fingerprint-reader symptom. Those symptoms or codes alone do not prove corruption.
- Save work and open Command Prompt as administrator. Keep the exact error and servicing logs from the failed operation.
- Run the supported component-store repair and wait for its final result:
DISM.exe /Online /Cleanup-Image /RestoreHealth
- After DISM succeeds, run the protected-file scan and allow verification to finish:
sfc /scannow
- Restart and repeat the operation that actually failed.
- If DISM fails or asks for a repair source, record that specific error and obtain a matching supported source. Do not point it at an arbitrary image or repeat commands indefinitely.
Record both tools’ final messages and whether the original failure returns. One source reported an SFC-first sequence after DISM failed; that outcome does not establish a general correction for other DISM errors. Successful file repair is not proof that every update, DLL or device problem shares one cause.