Examkin

Question

Difficulty: HardResolving System File Corruption and Driver Issues

An IT support specialist is servicing a Windows 11 desktop computer that fails to boot following a failed storage controller driver update. The workstation is stuck in an Automatic Repair loop due to corrupted driver files and pending system updates preventing normal startup. The technician needs to access the Windows Recovery Environment (WinRE) Command Prompt and use an attached USB drive containing Windows installation media (mounted as drive D:) to perform offline repair operations. In what sequential order should the technician execute the command-line procedures to cancel pending operations, repair the component store, and replace corrupted system files?

  1. 1Boot the computer into the Windows Recovery Environment (WinRE) Command Prompt.
  2. 2Execute DISM with the `/revertpendingactions` switch targeting the offline system drive.
  3. 3Execute DISM with `/restorehealth` pointing to the offline Windows volume and the external `install.wim` image source.
  4. 4Execute System File Checker (`sfc /scannow`) with `/offbootdir` and `/offwindir` parameters.
  5. 5Restart the workstation to initiate normal operating system startup.

Answer

The correct troubleshooting sequence requires accessing WinRE Command Prompt, executing DISM with /revertpendingactions to clear pending driver installations, running DISM /restorehealth with an external source to repair the offline component store, running SFC with /offbootdir and /offwindir to repair corrupted protected files, and finally restarting the workstation.
The proper sequence begins by entering WinRE Command Prompt to perform offline servicing. Next, pending driver updates and operations must be reverted using `/revertpendingactions` to unlock system file operations. DISM `/restorehealth` must then be executed using an external WIM source to restore the integrity of the offline component store (WinSxS). Once the component store is healthy, SFC (`sfc /scannow`) with `/offbootdir` and `/offwindir` can effectively repair corrupted system files. Finally, restarting the system verifies operating system functionality.

Step-by-Step Solution

1
Boot into Windows Recovery Environment (WinRE) Command Prompt.
Establishes an offline repair environment where locked OS files can be serviced.
System repair tools cannot modify active OS driver dependencies while Windows is running or failing to boot normally.
2
Run `dism /image:C:\ /cleanup-image /revertpendingactions`.
Cancels stuck driver updates and pending servicing tasks.
Pending update locks prevent DISM and SFC from successfully modifying system files.
3
Run `dism /image:C:\ /cleanup-image /restorehealth /source:wim:D:\sources\install.wim:1`.
Repairs corrupted component store files in C:\Windows\WinSxS using clean source payloads from the installation media.
SFC relies on the component store payload repository; repairing the component store first ensures SFC has valid replacement files.
4
Run `sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows`.
Scans protected offline system files and replaces corrupted binaries using the healthy component store.
SFC requires explicit offline boot and Windows directory parameters when executed from WinRE.
5
Reboot the system.
Verifies system recovery and allows normal driver initialization.
Final validation confirms the operating system boots cleanly after corruption resolution.

Key Concept

Offline DISM and SFC Repair Sequencing
Rate this question

Topics

Resolving System File Corruption and Driver Issues

More questions from this topic