Question

Difficulty: MediumResolving System File Corruption and Driver Issues

A technician is troubleshooting a Windows workstation that displays frequent system error dialogs after an unclean shutdown. The technician ran the System File Checker (`sfc /scannow`), but the utility reported that it found corrupt files and was unable to fix some of them because the local component store itself is damaged. In what sequence should the technician execute the following procedures to properly repair the component store image, fix the corrupted system files, and complete the repair process?

  1. 1Open an elevated Command Prompt with administrative privileges.
  2. 2Run `dism /online /cleanup-image /restorehealth` to repair the Windows Component Store image.
  3. 3Run `sfc /scannow` to scan protected system files and replace corrupted files using the repaired component store.
  4. 4Reboot the workstation to complete pending file replacements and verify system stability.

Answer

The correct troubleshooting sequence is: First, open an elevated Command Prompt. Next, execute `dism /online /cleanup-image /restorehealth` to repair the component store. Then, execute `sfc /scannow` to fix corrupt system files. Finally, restart the system to complete file replacement operations.
The correct sequence begins with opening an elevated Command Prompt to gain administrative access. The Deployment Image Servicing and Management tool (`dism /online /cleanup-image /restorehealth`) must be run next to repair the corrupted Windows component store image. Once the component store is healthy, running System File Checker (`sfc /scannow`) allows the utility to successfully replace damaged system files with clean copies from the store. Finally, restarting the computer applies any pending file operations that require a reboot.

Step-by-Step Solution

1
Launch Command Prompt with elevated (administrator) rights.
System grants necessary administrative privileges to run low-level repair utilities.
Both DISM and SFC require full administrative rights to inspect and modify Windows system files and component store manifests.
2
Execute `dism /online /cleanup-image /restorehealth`.
The Windows Component Store image is scanned, repaired, and restored to a healthy state.
SFC relies on the local component store (WinSxS) to retrieve clean copies of corrupted system files. If the component store itself is corrupted, DISM must repair it first.
3
Execute `sfc /scannow`.
Protected Windows system files are checked and any corrupted files are successfully replaced with healthy versions from the repaired component store.
With a healthy component store restored, System File Checker can successfully repair corrupted OS binaries.
4
Restart the workstation.
Pending file swaps are finalized at system boot, ensuring complete system file integrity.
Certain locked system files can only be replaced during the boot cycle prior to OS initialization.

Key Concept

DISM vs. SFC Repair Dependency Sequence
Rate this question