A Windows 11 workstation experienced an improper shutdown during a power outage and now frequently crashes with Stop errors referencing system file corruption. A technician opens an elevated Command Prompt and executes `sfc /scannow`, but the process halts with the error: "Windows Resource Protection found corrupt files but was unable to fix some of them." The technician suspects that the local Windows Component Store (WinSxS) used for file repair is itself corrupted. Which of the following command-line procedures should the technician execute NEXT to successfully restore system file integrity?
- Execute `dism /online /cleanup-image /restorehealth` to repair the local Component Store, and then re-run `sfc /scannow`.Answer
- BRe-run `sfc /scannow` repeatedly in Safe Mode prior to running DISM, as Safe Mode bypasses Component Store corruption checks.
- CExecute `dism /online /cleanup-image /sfcfix` to automatically repair system file binaries directly from Windows Update.
- DOpen Device Manager in Computer Management and select 'Scan for hardware changes' under System Devices to refresh system binaries.
Answer
The technician should execute `dism /online /cleanup-image /restorehealth` to repair the Windows Component Store, followed by re-running `sfc /scannow`.
When System File Checker (`sfc /scannow`) reports that it found corrupt files but could not repair them, it means the local source repository (the WinSxS folder) lacks healthy replacement copies. Running `dism /online /cleanup-image /restorehealth` repairs the Windows Component Store image using Windows Update. Once DISM finishes repairing the store, running `sfc /scannow` again will successfully restore damaged protected operating system files.
Step-by-Step Solution
Key Concept
DISM and SFC Repair Workflow Sequence