DISM Command: Repair Windows Image & Component Store | Guide

The DISM command (Deployment Image Servicing and Management) is a Windows Command Prompt utility that services and repairs Windows images, including the component store that System File Checker uses for repairs. Use DISM /Online /Cleanup-Image /RestoreHealth to fix corrupted Windows Update components, repair SFC failures, and restore Windows image integrity without reinstallation.

Whether you're troubleshooting Windows Update errors that prevent security patch installation, resolving SFC failures where "corrupt files could not be repaired," or preparing system images for enterprise deployment, DISM provides low-level Windows servicing capabilities that go deeper than standard repair tools. System administrators rely on DISM to repair the Windows component store (WinSxS), which serves as the foundation for all other Windows repair operations including SFC and Windows Update.

This comprehensive guide covers DISM command syntax, all cleanup and restore options, practical repair examples for common Windows corruption scenarios, troubleshooting tips when DISM operations fail, related system recovery commands, and frequently asked questions. By the end, you'll confidently diagnose and repair Windows image corruption across workstations, servers, and deployment infrastructures.

What Is the DISM Command?

The DISM command is Microsoft's advanced servicing tool for Windows images, operating at a lower level than System File Checker by repairing the Windows component store (located in C:\Windows\WinSxS). This component store serves as the repository of all Windows files, drivers, and features—acting as the "source of truth" that SFC uses when repairing system files.

DISM runs on Windows 7 and later (with full functionality on Windows 8/10/11 and Server 2012+). The command requires administrator privileges because it modifies critical operating system components. Unlike SFC which repairs files in use by Windows, DISM repairs the component store itself—the underlying database and file cache that makes other repairs possible.

The most common usage is DISM /Online /Cleanup-Image /RestoreHealth, which scans the component store for corruption and automatically repairs it using Windows Update as a source. DISM also handles offline image servicing, driver injection, feature management, and Windows edition servicing for deployment scenarios.

Syntax

DISM /Online /Cleanup-Image [/CheckHealth | /ScanHealth | /RestoreHealth] [/Source:<path>] [/LimitAccess]

Parameters and Options

Parameter	Description
/Online	Targets the currently running Windows installation
/Cleanup-Image	Performs component store cleanup operations
/CheckHealth	Quick check for corruption markers (no scan)
/ScanHealth	Scans component store for corruption (no repair)
/RestoreHealth	Scans and repairs component store corruption
/Source:<path>	Specifies custom repair source (install.wim or mounted image)
/LimitAccess	Prevents DISM from using Windows Update as source
/StartComponentCleanup	Removes superseded components to reduce WinSxS size
/ResetBase	Removes all superseded versions (cannot uninstall updates after)
/Image:<path>	Targets offline Windows image instead of running system

Parameters Explained

/CheckHealth – Quick Corruption Check

The /CheckHealth parameter performs a fast check (completes in seconds) to see if corruption markers exist in the component store. It doesn't perform actual scanning—just checks if previous operations flagged corruption.

Example: DISM /Online /Cleanup-Image /CheckHealth

This is useful for quick health status verification before maintenance windows or as part of automated monitoring scripts.

/ScanHealth – Detailed Corruption Scan

Use /ScanHealth to thoroughly scan the component store for corruption without performing repairs. This diagnostic scan takes 10-30 minutes and identifies all corruption but doesn't modify anything.

Example: DISM /Online /Cleanup-Image /ScanHealth

Results are logged to C:\Windows\Logs\DISM\dism.log. This option is ideal when you want to assess corruption severity before committing to potentially lengthy repair operations.

/RestoreHealth – Scan and Repair

The /RestoreHealth parameter scans the component store and automatically repairs all detected corruption using Windows Update or specified sources. This is the most commonly used DISM operation for troubleshooting.

Example: DISM /Online /Cleanup-Image /RestoreHealth

The repair typically takes 20-60 minutes depending on corruption extent and internet connection speed (if using Windows Update as source).

/Source – Custom Repair Source

The /Source parameter specifies a custom location for repair files instead of downloading from Windows Update. This is essential for offline repairs, air-gapped environments, or when you want faster repairs using local installation media.

Example: DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\Sources\install.wim:1 /LimitAccess

The :1 suffix specifies the image index within the WIM file. /LimitAccess prevents fallback to Windows Update.

/StartComponentCleanup – Reduce WinSxS Size

This parameter removes superseded versions of components, freeing disk space in the WinSxS folder. Component cleanup is safe and recommended for systems with limited storage.

Example: DISM /Online /Cleanup-Image /StartComponentCleanup

This maintenance operation can recover several gigabytes of disk space by removing outdated component versions no longer needed for rollback.

Examples

Basic Component Store Repair

Scenario: Windows Update repeatedly fails with errors 0x800F0922 or 0x80070003, and SFC reports "found corrupt files but was unable to fix some of them." You need to repair the component store so SFC can subsequently fix system files.

DISM /Online /Cleanup-Image /RestoreHealth

Expected Output:

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19041.844

[==========================100.0%==========================]
The restore operation completed successfully.
The operation completed successfully.

Explanation: DISM connects to Windows Update, downloads necessary repair files, and rebuilds corrupted component store entries. This typically takes 20-60 minutes. After completion, run sfc /scannow to complete system file repairs using the now-healthy component store.

Quick Health Check

Scenario: You're performing routine system diagnostics and want to quickly verify if the component store has any known corruption without running a lengthy scan.

DISM /Online /Cleanup-Image /CheckHealth

Expected Output:

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19041.844

No component store corruption detected.
The operation completed successfully.

Explanation: This fast check (completes in seconds) reports if previous operations flagged corruption. If corruption is detected, follow up with /ScanHealth or /RestoreHealth for detailed diagnosis and repair.

Detailed Corruption Scan

Scenario: You suspect component store corruption but want to assess severity before committing to a repair operation that could take an hour. You need diagnostic information without making changes.

DISM /Online /Cleanup-Image /ScanHealth

Expected Output:

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19041.844

[==========================100.0%==========================]
Component Store corruption was detected.
The operation completed successfully.

Explanation: Detailed scan takes 10-30 minutes and reports corruption without repairing. Review C:\Windows\Logs\DISM\dism.log for specific corruption details, then run /RestoreHealth to perform actual repairs.

Offline Repair Using Installation Media

Scenario: Your internet connection is unreliable, or you're working on an air-gapped enterprise network. You have Windows installation media and want to repair the component store using local files instead of downloading from Windows Update.

DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\Sources\install.wim:1 /LimitAccess

Expected Output:

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

[==========================100.0%==========================]
The restore operation completed successfully.
The operation completed successfully.

Explanation: DISM uses the install.wim file from mounted installation media (drive D:) as the repair source. The :1 specifies Windows edition index (typically 1 for standard edition). /LimitAccess prevents fallback to Windows Update, ensuring offline operation.

Repair Before Running SFC

Scenario: SFC failed with "found corrupt files but was unable to fix some of them," indicating component store corruption. You need to repair the component store first so SFC can complete its repairs.

DISM /Online /Cleanup-Image /RestoreHealth

Wait for completion, then run SFC:

sfc /scannow

Expected Output: DISM completes successfully, then SFC successfully repairs all system files.

Explanation: This is the correct repair sequence when SFC fails. DISM repairs the "repair library" (component store), then SFC uses that healthy library to fix actual system files. Always run DISM before repeating failed SFC operations.

Component Store Cleanup for Disk Space

Scenario: Your system partition is running low on disk space. The WinSxS folder has grown to 15GB+ over time with superseded component versions. You need to safely reclaim space without breaking Windows.

DISM /Online /Cleanup-Image /StartComponentCleanup

Expected Output:

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

[==========================100.0%==========================]
The operation completed successfully.

Explanation: This removes superseded component versions no longer needed for rollback, potentially freeing 2-8GB of space. This is safe and recommended. Do not use /ResetBase unless you're certain you won't need to uninstall recent updates.

Aggressive Cleanup with ResetBase

Scenario: You're preparing a system for long-term deployment and will not need to uninstall any currently installed updates. You want maximum disk space recovery from the WinSxS folder.

DISM /Online /Cleanup-Image /StartComponentCleanup /ResetBase

Expected Output:

The operation completed successfully.

Explanation: /ResetBase removes all superseded versions, preventing future update uninstallation for currently installed updates. Use this only when absolutely certain rollback won't be needed, such as in golden images for deployment.

Repair Using Mounted Image Source

Scenario: You're an enterprise administrator with a mounted reference image on a network share. You need to repair multiple workstations using this controlled source instead of Windows Update for consistency.

DISM /Online /Cleanup-Image /RestoreHealth /Source:wim:\\Server\Images\Windows10.wim:1 /LimitAccess

Expected Output: Successful repair using network-based WIM file.

Explanation: Network paths are supported for /Source parameter, enabling centralized enterprise repair sources. This ensures all workstations repair using the same validated component source, improving consistency across the fleet.

Pre-Upgrade Component Store Verification

Scenario: Before performing a major Windows feature update (e.g., Windows 10 to 11 upgrade), you want to ensure the component store is healthy to prevent upgrade failures.

DISM /Online /Cleanup-Image /ScanHealth

If corruption found:

DISM /Online /Cleanup-Image /RestoreHealth

Expected Output: Scan identifies any issues; repair operation fixes them before upgrade attempt.

Explanation: Major Windows upgrades fail if the component store has corruption. Running DISM before upgrades is a best practice that dramatically reduces upgrade-related failures and post-upgrade instability.

Offline Windows Image Repair

Scenario: You're servicing an offline Windows image mounted at C:\Mount for deployment preparation. You need to repair the mounted image's component store before capturing it for distribution.

DISM /Image:C:\Mount /Cleanup-Image /RestoreHealth /Source:D:\Sources\install.wim:1

Expected Output: Mounted image repairs successfully.

Explanation: /Image targets offline mounted images instead of the running system. This is critical for IT professionals preparing master deployment images, ensuring deployed systems start with healthy component stores.

Common Use Cases

1. SFC Failure Resolution: Run DISM /RestoreHealth when SFC reports "found corrupt files but was unable to fix some of them," repairing the component store so SFC can subsequently complete system file repairs successfully.

2. Windows Update Error Recovery: Fix persistent Windows Update errors (0x800F0922, 0x80070003, 0x800F081F) caused by component store corruption that prevents proper update installation and security patch application.

3. Pre-Upgrade System Preparation: Verify and repair component store health before major Windows feature upgrades to prevent installation failures and ensure smooth upgrade completion without corruption-related issues.

4. Enterprise Image Servicing: Repair and optimize offline Windows deployment images by servicing mounted WIM files, ensuring master images deployed across organizations start with healthy component stores.

5. Component Store Cleanup: Reclaim disk space on systems with limited storage by running /StartComponentCleanup to remove superseded component versions, potentially recovering 2-8GB from the WinSxS folder.

6. Air-Gapped System Repair: Use /Source with local installation media to repair systems without internet connectivity, essential for secure networks, classified environments, and offline workstations.

7. Post-Malware Recovery Verification: After malware removal and SFC repairs, run DISM to verify component store integrity and ensure malware didn't compromise the underlying Windows servicing infrastructure.

8. Server Maintenance and Compliance: Include DISM health checks in regular server maintenance schedules to proactively detect corruption before it causes service outages, update failures, or compliance audit issues.

9. Driver Integration for Deployment: Use DISM to inject hardware drivers into offline Windows images, enabling single-image deployment across diverse hardware while maintaining proper component store structure.

10. Feature Enable/Disable Operations: Manage optional Windows features using DISM /Enable-Feature and /Disable-Feature commands, properly updating component store records and feature manifests for clean feature state management.

11. Windows Edition Upgrades: Service Windows images to change editions (Home to Pro, Pro to Enterprise) using DISM /Set-Edition, properly updating licensing and feature availability in the component store.

12. Pre-Deployment Image Validation: Scan captured deployment images with DISM /CheckHealth and /ScanHealth before distribution to prevent deploying corrupted images that would require individual workstation repairs post-deployment.

Tips and Best Practices

1. Always Run DISM Before Repeating Failed SFC: When SFC cannot repair files, the component store is corrupted. Run DISM /Online /Cleanup-Image /RestoreHealth first, then re-run SFC. This is the correct repair sequence that resolves 90%+ of stubborn SFC failures.

2. Expect Long Execution Times: DISM /RestoreHealth typically takes 20-60 minutes, sometimes longer with slow internet or extensive corruption. Don't interrupt the process even if progress appears stuck—let it complete naturally for reliable results.

3. Use /Source with Local Media for Speed: If you have Windows installation media, use /Source:D:\Sources\install.wim:1 /LimitAccess for much faster repairs than downloading from Windows Update. This is especially important on metered connections.

4. Review dism.log for Detailed Errors: The DISM log at C:\Windows\Logs\DISM\dism.log contains detailed operation information. When DISM fails, review this log to identify specific files or packages causing issues before escalating to reinstallation.

5. Run /CheckHealth in Monitoring Scripts: Include DISM /Online /Cleanup-Image /CheckHealth in automated system health monitoring. This fast check (completes in seconds) detects corruption flags without resource-intensive scanning.

6. Start with /ScanHealth for Diagnostics: When troubleshooting, run /ScanHealth first to assess corruption severity and estimate repair time before committing to /RestoreHealth on production systems during maintenance windows.

7. Combine with Disk Cleanup: After running /StartComponentCleanup, also run Disk Cleanup (cleanmgr.exe) and select "Windows Update Cleanup" for maximum space recovery from superseded files and update caches.

8. Verify Internet Connectivity First: DISM /RestoreHealth requires Windows Update access unless /Source is specified. Test connectivity to update.microsoft.com before running DISM to avoid operation failures due to network issues.

9. Use /ResetBase Cautiously: Only use /StartComponentCleanup /ResetBase when certain you won't need to uninstall updates. This permanently removes rollback capability for installed updates—ideal for golden images but risky for production systems.

10. Run as Administrator Always: DISM requires full administrator privileges. Right-click Command Prompt and select "Run as administrator" before executing DISM commands to avoid access denied errors and operation failures.

11. Schedule During Low-Activity Periods: DISM is resource-intensive, consuming significant CPU, disk I/O, and potentially bandwidth. Schedule DISM operations during maintenance windows on production servers to minimize user impact and performance degradation.

12. Document Component Store Health: In enterprise environments, log DISM results to central documentation systems for audit trails, compliance reporting, and change management records—especially before and after major system changes or deployments.

Troubleshooting Common Issues

DISM Error 0x800f081f – Source Files Not Found

Problem: Running DISM /Online /Cleanup-Image /RestoreHealth fails with error 0x800f081f stating "The source files could not be found."

Cause: DISM cannot reach Windows Update servers due to internet connectivity issues, firewall restrictions, or proxy configurations blocking access to Microsoft update services.

Solution: Use local installation media as repair source:

1. Mount Windows installation ISO or insert installation USB
2. Run: DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\Sources\install.wim:1 /LimitAccess

(Replace D: with your installation media drive letter)

Prevention: Test connectivity to update.microsoft.com before running DISM, or always use /Source parameter with local media in enterprise environments with restricted internet access.

DISM Stuck at Specific Percentage

Problem: DISM /RestoreHealth appears frozen at 20%, 40%, or 62.3% for over 30 minutes with no apparent progress or disk activity.

Cause: DISM may be downloading large repair files from Windows Update (appears frozen but is actually network-bound), or encountering severe corruption requiring extensive processing. The operation is often not truly stuck—just extremely slow.

Solution: Allow at least 2-3 hours before considering it genuinely stuck. If using Windows Update as source, check network activity—downloads may be in progress. If truly frozen, close Command Prompt and retry with local source:

DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\Sources\install.wim:1 /LimitAccess

Prevention: Use local installation media with /Source and /LimitAccess for predictable execution times independent of internet speed or Windows Update server load.

"Error 87: The Parameter is Incorrect"

Problem: DISM command fails immediately with "Error 87: The parameter is incorrect" without performing any operations.

Cause: Syntax error in the command, typically incorrect /Source format, missing colons, incorrect image index specification, or unsupported parameter combinations.

Solution: Verify command syntax carefully:

• Ensure /Source format: wim:D:\Sources\install.wim:1 or D:\Sources\install.wim:1
• Check image index (:1 for standard editions)
• Verify paths use backslashes (\) not forward slashes (/)
• Use quotes around paths with spaces: "/Source:D:\Windows Images\install.wim:1"

Prevention: Copy-paste verified working syntax from documentation, use tab completion for paths, and test on non-production systems before production deployment.

DISM Reports Success But SFC Still Fails

Problem: DISM /RestoreHealth completes successfully with "The operation completed successfully," but subsequent SFC scans still report "found corrupt files but was unable to fix some of them."

Cause: The corruption exists in system files outside the component store's scope, or disk hardware issues are causing new corruption faster than repairs complete, or file system corruption prevents proper file access.

Solution: Run comprehensive diagnostics:

1. Check disk health: chkdsk C: /f /r (requires reboot)
2. Test memory: mdsched.exe (Windows Memory Diagnostic)
3. Re-run DISM with verification: DISM /Online /Cleanup-Image /RestoreHealth
4. Re-run SFC: sfc /scannow
5. If still failing, consider System Restore or in-place upgrade

Prevention: Regularly run disk diagnostics, monitor SMART data, and address hardware issues promptly. File corruption often indicates failing storage hardware.

"Error 50: The Request is Not Supported"

Problem: DISM fails with "Error 50: The request is not supported" when attempting component store operations.

Cause: You're running DISM from Windows PE or recovery environment, or attempting unsupported operations on Windows 7 (which has limited DISM functionality compared to Windows 8+).

Solution: Boot into full Windows installation for online operations. For Windows 7, upgrade to Windows 8/10/11 for full DISM functionality, or use system-specific repair tools appropriate for that Windows version.

Prevention: Verify Windows version supports intended DISM operations. Use /Online only from fully booted Windows installations, not from Windows PE or recovery environments unless specifically using /Image for offline servicing.

DISM Logs Show "Ngen Worker" Timeouts

Problem: DISM completes but dism.log contains numerous "Ngen worker timed out" entries, and .NET applications subsequently fail or perform poorly.

Cause: .NET Framework native image generation failed during DISM operations, preventing proper .NET assembly optimization. This commonly occurs after component store repairs.

Solution: Manually regenerate .NET native images:

cd %windir%\Microsoft.NET\Framework\v4.0.30319
ngen update
cd %windir%\Microsoft.NET\Framework64\v4.0.30319
ngen update

Wait for completion (may take 10-30 minutes), then restart system.

Prevention: Allow adequate time for DISM to complete all post-repair tasks. Slow systems may need extended time for native image generation. Don't interrupt DISM operations prematurely.

Related Commands

sfc – System File Checker

Repairs actual Windows system files using the component store as its source. Always run DISM before SFC when SFC fails to repair files, ensuring the component store is healthy before attempting system file repairs.

When to use SFC: After successful DISM repair, run sfc /scannow to complete the repair process by fixing actual system files using the now-healthy component store.

chkdsk – Check Disk

Scans and repairs file system errors and bad sectors that can prevent DISM from operating correctly. File system corruption often causes DISM to fail or report false corruption.

When to use chkdsk: Before running DISM if you suspect disk issues. Run chkdsk C: /f /r to fix filesystem errors and recover bad sectors, then run DISM for component store repair.

Windows Update Troubleshooter

Built-in troubleshooting tool that resets Windows Update components and services. Simpler than DISM but less comprehensive—use when DISM seems excessive for minor update issues.

When to use: For basic Windows Update problems before escalating to DISM. Access via Settings > Update & Security > Troubleshoot > Windows Update.

System Restore

Creates and restores complete system snapshots including registry, drivers, and system files. More comprehensive than DISM but requires existing restore points.

When to use: When DISM and SFC together cannot resolve corruption, or when corruption timing coincides with known restore point. Access via rstrui.exe.

In-Place Upgrade (Repair Install)

Reinstalls Windows while preserving applications, settings, and files. Most comprehensive repair option when DISM, SFC, and System Restore all fail.

When to use: As last resort before clean installation when component store corruption is too severe for DISM to repair. Run Windows 10/11 installation media and choose "Upgrade this PC now."

PowerShell DISM Module

PowerShell cmdlets providing equivalent functionality to DISM command-line tool with object-oriented output and pipeline integration.

When to use: In PowerShell scripts for automation. Use Repair-WindowsImage -Online -RestoreHealth as PowerShell equivalent to DISM /Online /Cleanup-Image /RestoreHealth.

Frequently Asked Questions

What does DISM RestoreHealth do?

DISM /Online /Cleanup-Image /RestoreHealth scans the Windows component store (WinSxS) for corruption and automatically repairs it using Windows Update or specified sources. The component store acts as the "repair library" for all Windows servicing operations. Restoring component store health enables SFC to subsequently repair system files that were previously unrepairable due to component store corruption.

How long does DISM take to complete?

DISM /RestoreHealth typically takes 20-60 minutes on systems with SSD storage and fast internet connections. Traditional hard drives may require 45-90 minutes. Extensive corruption, slow internet, or using Windows Update as source can extend operation time to 2-3 hours. Using local installation media with /Source parameter significantly reduces execution time to 15-30 minutes.

What is the difference between DISM and SFC?

DISM repairs the Windows component store (WinSxS)—the underlying repository of Windows files. SFC repairs actual system files in use by Windows, using the component store as its source. When SFC fails to repair files, it means the component store is corrupted. Correct repair sequence: run DISM first to fix the "repair library," then run SFC to fix system files using that healthy library.

Can I use DISM without internet connection?

Yes, use local Windows installation media with /Source parameter: DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\Sources\install.wim:1 /LimitAccess. The /LimitAccess switch prevents DISM from attempting Windows Update access, ensuring completely offline operation. This is essential for air-gapped networks, classified systems, and environments with restricted internet access.

Why does DISM fail with error 0x800f081f?

Error 0x800f081f ("The source files could not be found") indicates DISM cannot access Windows Update servers due to network issues, firewall blocks, or proxy restrictions. Solution: use local installation media as source with /Source parameter, or resolve network connectivity issues preventing access to update.microsoft.com.

Should I run DISM or SFC first?

Run SFC first. If SFC reports "found corrupt files but was unable to fix some of them," then run DISM to repair the component store, followed by another SFC scan to complete repairs. If SFC succeeds on first attempt, DISM is unnecessary. DISM is the escalation when SFC fails due to component store corruption.

Can DISM fix Windows Update errors?

Yes, DISM repairs component store corruption that causes Windows Update failures with error codes 0x800F0922, 0x80070003, 0x800F081F, and similar. After running DISM /Online /Cleanup-Image /RestoreHealth, retry the failed Windows Update. DISM resolves the underlying corruption preventing update installation.

Does DISM work in Safe Mode?

Yes, DISM works in Safe Mode and sometimes performs better because fewer services and processes are running, reducing file locking conflicts. However, Safe Mode with Networking is required if using Windows Update as source. For local media source, standard Safe Mode is sufficient.

How do I check if DISM fixed the problem?

After DISM completes, run sfc /scannow to verify system files can now be repaired. If SFC completes without errors or successfully repairs all files, DISM was successful. Also check C:\Windows\Logs\DISM\dism.log for detailed operation results and confirmation of repairs performed.

Can DISM delete my files or programs?

No, DISM only repairs Windows system components and does not affect user documents, photos, installed applications, or personal files. DISM operates exclusively on the Windows component store and system files, ignoring all user data and third-party applications.

What does /StartComponentCleanup do?

/StartComponentCleanup removes superseded versions of Windows components from the WinSxS folder, freeing disk space while maintaining system rollback capability for recent updates. This is safe and recommended for space recovery. Adding /ResetBase removes all superseded versions but prevents future update uninstallation.

Can I run DISM on Windows 7?

Yes, but Windows 7 has limited DISM functionality compared to Windows 8/10/11. Basic /RestoreHealth operations work, but advanced features like /StartComponentCleanup, /ResetBase, and some servicing operations require Windows 8 or later. Consider using System Update Readiness Tool for Windows 7 component store repairs.

Quick Reference Card

Command	Purpose	Typical Use Case
DISM /Online /Cleanup-Image /CheckHealth	Quick corruption check (seconds)	Automated monitoring scripts
DISM /Online /Cleanup-Image /ScanHealth	Detailed corruption scan (10-30 min)	Pre-repair diagnostics
DISM /Online /Cleanup-Image /RestoreHealth	Full scan and repair (20-60 min)	Fix SFC failures, Windows Update errors
DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\Sources\install.wim:1 /LimitAccess	Offline repair with local media	Air-gapped systems, fast repairs
DISM /Online /Cleanup-Image /StartComponentCleanup	Reclaim WinSxS disk space	Low disk space scenarios
DISM /Online /Cleanup-Image /StartComponentCleanup /ResetBase	Aggressive space recovery	Golden image preparation

Try DISM in Our Simulator

Ready to practice DISM and other advanced system repair commands in a risk-free environment? Use our interactive Windows Command Simulator to experiment with component store maintenance commands without affecting your actual system. Perfect for learning command syntax and understanding output before running on production machines.

Explore our complete Windows Commands Reference for detailed documentation on 200+ CMD commands, including SFC, chkdsk, and other system diagnostic tools essential for Windows administration and troubleshooting.

Summary

The DISM command (Deployment Image Servicing and Management) operates at a fundamental level of Windows servicing, repairing the component store that underpins all other Windows repair mechanisms including System File Checker and Windows Update. Whether running DISM /Online /Cleanup-Image /RestoreHealth to fix persistent SFC failures, using /Source with local installation media for air-gapped environments, or performing /StartComponentCleanup for disk space recovery, DISM provides essential capabilities for maintaining Windows system integrity.

Understanding the DISM-SFC relationship is critical for effective troubleshooting: SFC repairs system files using the component store as its source, while DISM repairs the component store itself. When SFC reports "found corrupt files but was unable to fix some of them," the correct resolution is always DISM first to repair the component store, then SFC to complete system file repairs using the restored component store.

Key operational principles include expecting long execution times (20-60+ minutes), using local installation media with /Source for faster and more reliable repairs, reviewing dism.log for detailed diagnostics when operations fail, and running DISM before repeating failed SFC operations. For production environments, combining quick /CheckHealth monitoring with scheduled /RestoreHealth operations during maintenance windows provides proactive corruption detection and repair before service outages occur.

Most importantly, DISM excels as both reactive troubleshooting and preventive maintenance. Regular component store health checks on servers and workstations detect corruption early, prevent Windows Update failures, reduce emergency repair scenarios, and maintain system stability across enterprise infrastructures. Master DISM operation, understand its integration with SFC and deployment workflows, and incorporate it into comprehensive Windows health strategies for robust, maintainable system environments.

Practice DISM commands in safe test environments first, maintain local installation media for offline repairs, document all DISM operations for compliance and audit trails, and establish clear escalation paths when DISM cannot resolve corruption—typically indicating hardware failure or requiring in-place upgrade/reinstallation.