A help desk technician is troubleshooting a Windows 11 workstation that experiences erratic system crashes. Running `sfc /scannow` from an elevated command prompt returns the following message: "Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.log." Repeated attempts to execute SFC fail to repair the files because the local side-by-side component store (WinSxS) is corrupted. Which of the following procedures should the technician perform NEXT to resolve this issue?
- Execute `dism /online /cleanup-image /restorehealth` to repair the component store, and then re-run `sfc /scannow`.Answer
- BExecute `sfc /scannow /offbootdir=c:\ /offwindir=c:\windows` directly within the active Windows desktop environment.
- COpen Device Manager, expand System Devices, and select Roll Back Driver on the Windows System File abstraction driver.
- DOpen System Properties in Control Panel and select Startup and Recovery to run an automated system file rebuilding wizard.
Answer
Execute DISM with the restorehealth parameter while online to fix the component store, followed by re-running SFC scannow.
When System File Checker (SFC) encounters corruption in the local component store, it cannot retrieve known-good copies of system files. Running Deployment Image Servicing and Management (DISM) with the `/online /cleanup-image /restorehealth` parameters repairs the local component store by fetching replacement files from Windows Update. Once DISM finishes repairing the component store, running `sfc /scannow` again successfully replaces corrupt system files.
Step-by-Step Solution
Key Concept
DISM and SFC repair sequence for corrupted Windows component store