A desktop technician is servicing a Windows workstation that exhibits severe system corruption after an improper shutdown. The System File Checker utility (`sfc /scannow`) fails immediately, stating that the Windows Component Store is corrupted. What is the correct sequence of command-line operations the technician should perform to repair the Component Store and successfully fix the corrupted system files using an online repair source?
- 1Run `dism /online /cleanup-image /checkhealth` to verify whether the image has been flagged as corrupt by a previous process.
- 2Run `dism /online /cleanup-image /scanhealth` to perform an advanced scan of the Component Store for hidden corruption.
- 3Run `dism /online /cleanup-image /restorehealth` to repair the corrupted Component Store using Windows Update as the payload source.
- 4Run `sfc /scannow` to scan protected system files and replace corrupted files using the newly repaired Component Store.
Cevap
The technician should first verify corruption status (`dism /checkhealth`), perform a thorough health scan (`dism /scanhealth`), repair the Component Store payload (`dism /restorehealth`), and finally execute the System File Checker scan (`sfc /scannow`).
The correct troubleshooting sequence requires inspecting and repairing the underlying servicing store before attempting to fix system binaries. `dism /checkhealth` quickly verifies existing flags, `dism /scanhealth` performs a full scan of the Component Store, `dism /restorehealth` fixes the corrupted payload store via Windows Update, and `sfc /scannow` uses the repaired store to replace corrupted protected system files.
Adım Adım Çözüm
Anahtar Kavram
DISM and SFC Repair Workflow Sequencing