Analyze Component Store
Runs DISM /Online /Cleanup-Image /AnalyzeComponentStore /NoRestart to analyze the Windows component store and report its servicing/cleanup state.
Windows Repair Utility
Repair Tool is a focused Windows PowerShell utility that runs Microsoft DISM component-store analysis, cleanup, health checks, and repair commands, then runs System File Checker to verify and repair protected Windows system files.
Repair Sequence
The script runs the servicing commands in a fixed order so the Windows component store is analyzed and repaired before System File Checker performs its final protected-file scan.
DISM
Runs DISM /Online /Cleanup-Image /AnalyzeComponentStore /NoRestart to analyze the Windows component store and report its servicing/cleanup state.
Runs DISM /Online /Cleanup-Image /StartComponentCleanup to clean superseded component-store content through Microsoft's servicing stack.
Runs DISM /Online /Cleanup-Image /CheckHealth for a quick check of whether Windows has already marked the component image as corrupted.
Runs DISM /Online /Cleanup-Image /ScanHealth to perform a deeper component-store corruption scan.
Runs DISM /Online /Cleanup-Image /RestoreHealth to repair component-store corruption when Windows detects it.
The current PowerShell script does not issue a restart command after DISM or SFC completes.
System File Checker
After all DISM commands finish, Repair Tool runs sfc /scannow. System File Checker verifies protected Windows system files and attempts to replace corrupted copies using the Windows servicing infrastructure.
Saved Results
Before the repair commands start, Repair Tool creates a results folder and starts a PowerShell transcript so the console output is saved for later review.
If %USERPROFILE%\Desktop exists, the output folder is created as Desktop\Repair Tool Results.
If that Desktop path is not found, the script uses %USERPROFILE%\OneDrive\Desktop\Repair Tool Results.
The full PowerShell transcript is written to DISM_SFC.txt inside the Repair Tool Results folder.
After SFC finishes, the script prints its completion message and stops the PowerShell transcript before waiting for Enter.
How To Run
Transparency
DISM StartComponentCleanup and RestoreHealth can change the Windows component store as part of Microsoft's built-in servicing process.
SFC can replace corrupted protected Windows system files when valid repair copies are available.
The current script relies on built-in Microsoft Windows DISM and SFC executables rather than downloading a third-party repair application.
The current PowerShell script contains no upload/API command for sending the saved DISM/SFC transcript to Melding Software or another service.
FAQ
DISM AnalyzeComponentStore, StartComponentCleanup, CheckHealth, ScanHealth, RestoreHealth, and finally sfc /scannow.
Yes. The batch launcher requests an elevated PowerShell window through UAC.
Normally under Desktop\Repair Tool Results\DISM_SFC.txt, with a OneDrive Desktop fallback when the regular Desktop path is not present.
No. The current script does not contain an automatic reboot command.
No. The repair operations use Microsoft's built-in DISM and System File Checker tools.
The script itself does not issue a direct web download, but DISM RestoreHealth may need access to a Windows repair source when replacement components are required.