Windows Server / Services, IIS & Secure Operations
Inspect Windows Server component-store health before repair
A failed feature installation can involve servicing corruption or a missing source. Collect the exact error before running repair operations.
Environment and inputs: Windows Server 2022 / 2025 baseline · Windows PowerShell with the specified role or RSAT modules; native utilities are identified in the text. Use delegated administration and elevation only where required.
Start with this check
Confirm the host, shell and access role. Replace sample names, paths, domains and interfaces with approved targets. These are diagnostic commands; assess policy and workload impact before making changes.
DISM.exe /Online /Cleanup-Image /ScanHealthRead the result
In an elevated terminal, this scans the component store and writes diagnostics; it is not the same as RestoreHealth repair. It can take time and create I/O load.
Resolve and verify
Read the result and relevant servicing logs, then choose a supported repair source matching the installed release and patch level. Verify the original feature operation afterward.
Before changing production
Do not use an arbitrary installation image or interrupt servicing because the progress display pauses.