Question

Difficulty: MediumResolving System File Corruption and Driver Issues

A desktop technician is troubleshooting a Windows workstation displaying missing file errors and system instability. The technician suspects corruption within both the Windows component store and protected operating system files. In what order should the technician perform the following repair steps to ensure system integrity is fully restored?

  1. 1Open Command Prompt as an administrator.
  2. 2Execute `dism /online /cleanup-image /restorehealth` to repair the Windows component store.
  3. 3Execute `sfc /scannow` to scan and replace corrupted protected operating system files.
  4. 4Restart the computer to complete the replacement of locked system files.

Answer

The correct sequence of repair steps is: Open an elevated Command Prompt, execute DISM to repair the component store, execute SFC to repair system files, and restart the computer to complete pending replacements.
To repair corrupted operating system files effectively, administrative elevation must be established first. Executing DISM `/restorehealth` restores the health of the Windows component store image. Once the store is repaired, running `sfc /scannow` allows the System File Checker to successfully extract clean file copies from the component store and repair corrupted OS files. Finally, restarting the workstation applies file updates for core binaries that were locked in active memory during the scan.

Step-by-Step Solution

1
Open Command Prompt with administrative privileges.
Obtains necessary administrative permissions to run system-level diagnostic and repair tools.
Both DISM and SFC require elevated privilege levels to modify protected system directories.
2
Run `dism /online /cleanup-image /restorehealth`.
Scans and repairs the Windows image component store cache.
The System File Checker uses the component store as its source repository. If the component store itself is corrupt, SFC will fail to repair files until DISM fixes the store.
3
Run `sfc /scannow`.
Scans protected system files and replaces corrupted ones using the restored component store.
Once the component store is healthy, SFC can pull clean replacement files to replace damaged system binaries.
4
Reboot the operating system.
Applies changes to system files that could not be modified while actively loaded in memory.
Core operating system files in active use are queued for replacement during the next system startup.

Key Concept

Sequential repair of Windows component store using DISM prior to executing System File Checker (SFC)
Estimated Time:1m 30s
Rate this question