⌚ About 2 min read
Control and repair Windows components and then system files protected.
Avant de commencer : adaptez toujours les commandes et manipulations à votre environnement. Sur un système de production, prévoyez une backup ou un retour arrière lorsque l’action peut modifier la configuration.
Étapes à suivre
-
1
Open an admin terminal
Open Windows Terminal as an administrator.
-
2
Control the Windows image
Run DISM /Online / cleanup-Image /Scan-2005.
-
3
Repair the image if necessary
Run DISM /Online / cleanup-Image /Re Store-2005.
-
4
Control System Files
Run sfc /scannow.
-
5
Restart and then control
Restart the position and check if the problem is resolved.
Commands utiles
DISM /Online / cleanup-Image /Scan-2005
DISM /Online / cleanup-Image /Re Store-2005
sfc /scannow
À retenir
- L, operation may seem blocked for several minutes.
- Do a backup before any major intervention on a position with physical symptoms.
DISM and SFC: know what each tool repairs
Technical checkpoints
- DISM /RestoreHealth repairs the Windows component store; SFC then validates system files against that source.
- SFC may fail to repair files when the WinSxS component store is damaged, which is why DISM usually precedes SFC.
- CBS.log and DISM.log contain evidence about unrepaired components; rebooting without reading them can lose useful context.
Typical sequence
Run checks from an elevated console and verify the exit result before moving on.
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannowTopic-specific pitfalls
- Using a /Source from the wrong Windows version/build can cause further failures.
- DISM/SFC do not fix disk or RAM hardware faults.
How to validate
- DISM finishes without remaining repairable corruption and SFC reports no integrity violations or successful repairs.
- The original Windows Update or application failure is retested after reboot if required.