Windows command guide
How to Use DISM /StartComponentCleanup in Windows
The Windows component store keeps the files and versions needed for servicing, updates, repairs, and optional features. Over time, older replaced components can accumulate. That does not always mean something is broken, but it can waste space and leave more update history behind than necessary. StartComponentCleanup tells DISM to remove superseded components that Windows no longer needs for normal servicing.
This guide is written around the specific symptom-command match for clean up the component store, not as a generic dump of terminal lines. That makes the page more useful for real troubleshooting and reduces the chance of running the wrong repair step.
DISM /Online /Cleanup-Image /StartComponentCleanup
Best place to run it
Elevated Command Prompt is the right execution context for this page. Because this repair touches protected Windows state, a normal unelevated shell can return misleading access errors or partial results.
Fast repair workflow
- Start from the exact symptom on this page: The WinSxS area has grown large over time
- Run the primary repair line exactly as shown: DISM /Online /Cleanup-Image /StartComponentCleanup.
- This workflow is tuned for this repair, so avoid mixing it with unrelated repair commands too early.
- Reboot if the servicing stack or protected files were changed, then retry the original Windows action.
- Escalate only after reading the output, usually toward CBS.log, DISM source repair, or Windows Update-specific repair.
Copyable wrapper script
Use this wrapper when you want the page command inside a clearer script block with start and finish prompts.
@echo off
echo Run this CMD sequence in an elevated Command Prompt.
echo Starting targeted repair sequence...
DISM /Online /Cleanup-Image /StartComponentCleanup
echo.
echo Review the output before closing this window.
pause
Verification commands after the repair
These follow-up commands help you check whether the repair actually changed the Windows state that matters, instead of assuming success from a single line.
DISM /Online /Cleanup-Image /CheckHealth
sfc /verifyonly
What problem this command is trying to solve
This command targets unnecessary old component-store data left behind after Windows updates and servicing operations.
- The WinSxS area has grown large over time.
- You want to reduce servicing leftovers after many updates.
- System cleanup is part of ongoing maintenance rather than emergency repair.
How the command works
DISM reviews the component store and removes superseded components that have already been replaced by newer versions and are no longer needed in the same way.
When it makes sense to run it
Use it as a maintenance and cleanup command, especially on systems that have seen many cumulative updates over time.
Before you run this command
- Open an elevated Command Prompt or PowerShell window before running DISM /Online /Cleanup-Image /StartComponentCleanup.
- Confirm that the symptom really matches this guide, especially if you are seeing signs such as: the winsxs area has grown large over time.
- Keep any exact DISM, SFC, CBS, or Windows Update error output because those details matter in the next step.
What result to expect
After running DISM /Online /Cleanup-Image /StartComponentCleanup, compare the result against the symptom that brought you here. The most useful checkpoint is whether the winsxs area has grown large over time becomes less frequent, changes form, or produces a clearer error message. A command page is stronger when it helps you verify a real change instead of just assuming the line must have worked.
How to verify that it worked
The best verification step after DISM /Online /Cleanup-Image /StartComponentCleanup is to repeat the action that previously triggered the problem. If you want to reduce servicing leftovers after many updates still appears in exactly the same way, the command probably was not the whole answer and you should move to the next targeted check instead of assuming the page is finished.
Why administrator rights matter here
This command changes system integrity and component corruption. Run it in an elevated shell so Windows can apply the repair instead of only returning an access or privilege error.
Before you run it
This is more about maintenance and space efficiency than solving every update problem. Run it as administrator and expect it to take some time on older systems.
When this is probably the wrong fix
This is not the right first fix for a single third-party app bug, a browser-only issue, or obvious hardware failure. Use it when the symptom points to Windows image health, recurring update corruption, or protected system files.
What to do if it does not help
If DISM /Online /Cleanup-Image /StartComponentCleanup does not improve the winsxs area has grown large over time, move to the next repair step that matches the same symptom family instead of piling on random commands. The best follow-up depends on whether the failure is mainly about system integrity and component corruption.
Frequently asked questions
Should I use DISM /Online /Cleanup-Image /StartComponentCleanup for this exact Windows symptom?
Use it when the behavior on your PC lines up with the repair target on this page: This command targets unnecessary old component-store data left behind after Windows updates and servicing operations.
What should I check right after DISM /Online /Cleanup-Image /StartComponentCleanup?
Check whether the original trigger still reproduces the same failure. For this page, a useful checkpoint is whether the winsxs area has grown large over time becomes less frequent, changes form, or points you toward a more specific next step.
When should I not rely on DISM /Online /Cleanup-Image /StartComponentCleanup alone?
This is not the right first fix for a single third-party app bug, a browser-only issue, or obvious hardware failure. Use it when the symptom points to Windows image health, recurring update corruption, or protected system files.