How to Run DISM command in Windows 11

Open Command Prompt as administrator to run the DISM command in Windows 11, now you need to run this specific command.

Step 1: Open Terminal or Command Prompt as Administrator

• Press Start button and select Terminal (Admin) or Command Prompt (Run as Admin).
• Click Yes if a prompt comes asking for permission.

Step 2: Run the DISM Commands

Run commands one by one and press Enter to check each:

• Check Health (Fast check for corruption flags):

cmd

DISM /Online /Cleanup-Image /CheckHealth

• Scan Health (In depth scan of the component store):

cmd

DISM /Online /Cleanup-Image /ScanHealth

• Restore Health (Downloads and repairs corrupt files through Windows Update):

cmd

DISM /Online /Cleanup-Image /RestoreHealth

Here is a visual guide on using DISM and SFC for repairing Windows 11

How to Fix Windows 11 Errors with DISM & SFC

Step 3: Running System File Checker (SFC)

Run SFC command for repairing protected system files as DISM finishes:

cmd

sfc /scannow

Understanding DISM in Windows 11

The Deployment Image Servicing and Management (DISM) command-line tool is a powerful utility for tackling component store problems and missing system files on Windows 11. However, it is important to know its boundaries.

What DISM Cannot Fix

While DISM is effective for many operating system issues, it has strict limitations:

• Hardware failures: It cannot diagnose or repair physical hardware problems, such as a failing solid-state drive (SSD) or faulty RAM modules.
• Third-party software corruption: It does not repair broken applications or registry errors that are completely separate from core Windows system files.
• Specific app breakdowns: If an app like the Adobe Creative Suite crashes or a custom line-of-business (LOB) software fails to launch, running DISM will not resolve the issue.

When Should You Use DISM?

DISM shines in specific administrative and troubleshooting scenarios. The most common use cases include:

• Repairing system images: Using the /RestoreHealth parameter to automatically detect and replace corrupted system files.
• Fixing Windows Update blocks: Resolving stubborn update failures that stem from damaged underlying system components.
• Servicing offline images: Modifying .wim or .vhd installation files before deployment.
• Managing Windows features: Enabling or disabling specific operating system features remotely.
• Cleaning up storage: Shrinking the WinSxS component store to reclaim valuable hard drive space.

Prerequisites and System Requirements

Before running DISM commands, make sure you meet the necessary conditions depending on whether you are working on a live operating system (online) or an offline image.

Here is what you will need:

• Administrative Privileges: You must open Command Prompt or PowerShell with Administrator rights (elevated mode) to execute DISM commands successfully.
• Online Status: The operating system must be running and connected if you are performing an online repair, such as using DISM /Online /Cleanup-Image /RestoreHealth.
• Active Internet Connection: Network access is required if you plan to use Windows Update as your repair source to fetch missing files.
• Alternative Repair Source: If Windows Update is blocked, offline, or unavailable, you will need a valid installation media source (like a USB drive) or a local install.wim file.
• Available Storage: Ensure you have enough breathing room on your drive—it is generally recommended to have at least 2 to 4 GB of free space.

Managing Production Risks with DISM

Executing DISM on active production systems isn’t a task to take lightly. Because the utility directly manipulates the core OS image store (WinSxS) and essential system files, improper handling can lead to unexpected hiccups.

Here are the main risks to keep on your radar:

• User Disruption: Running DISM can tie up vital system resources. On shared servers or multi-user terminal environments, this can slow things down or interrupt active sessions for multiple people at once.
• Corrupted States: If a repair command (like /RestoreHealth) gets cut short mid-way, or if you point it to a mismatched repair source, it might overwrite files incorrectly and leave your OS in an unstable limbo.
• Peak-Hour Sluggishness: Firing off DISM during busy hours—especially when combined with SFC or Windows Update tasks—can cause noticeable lag or unexpected prompts to reboot. End-users certainly won’t enjoy sudden performance drops or restart alerts.
• Security & Monitoring Blind Spots: If local security software interferes with the process, or if you fail to check the logs afterward, you might miss a crucial error and leave a machine vulnerable.

Best Practices to Play It Safe

To keep things running smoothly, follow these precautions:

• Timing is Everything: Always run DISM during scheduled maintenance blocks rather than in the middle of the workday.
• Match Your Sources: If you’re using a local repair image (install.wim), make sure its build version matches the OS you are fixing.
• Check the Logs: Dive into DISM.log and CBS.log after completion to verify everything finished cleanly.
• Watch Out for AV Interference: If security tools aggressively block core file replacements, temporarily whitelist or pause them during the run.
• Test First: Run through the procedure on a test machine or non-production VM before touching anything mission-critical.
• Have a Safety Net: Always take a backup or create a fresh system restore point before initiating deep repairs on a live production box.

For managed service providers (MSPs) handling multiple client environments, standardizing and documenting your DISM workflows goes a long way. Having a clear, repeatable process minimizes human error and makes troubleshooting much faster when things go sideways.

Easiest ways to use DISM in Windows 11

DISM does not work along, rather it is a part of the layered recovery strategy with SFC, WSUS and Windows Update. Understanding how these tools work together is critical to troubleshoot effectively.

Here’s the key concept:

DISM part is to repair the Windows image (the WinSxS), and then SFC uses this image file to fix the system files. So process will fail if the image is corrupted and not rectified by using DISM, which is why DISM comes first.

Here’s what to do:

First, validate image health before repair

You should not directly jump to /RestoreHealth before checking if you actually need it. By running unnecessary scans you just waste system resources and time. You can instead run a quick scan by following these simple steps to identify corruption:

1. Run Command Prompt as administrator

2. Execute this command: DISM /Online /Cleanup-Image /CheckHealth

Here are the results you might get:

• “No component store corruption detected”: Your image is fine. Repairs not needed.
• “The component store is repairable”:  Run a repair. Proceed to Step 3.
• Error codes or corruption messages: Now check the logs (see below).

3. If required, run a deep scan by executing this command: DISM /Online /Cleanup-Image /ScanHealth

This command performs a indepth scan of the component store, which takes longer but catches issues related to IT that a simple scan might have missed.

4. Now you can find the diagnostic logs by pressing Windows + E and then searching “%windir%\Logs\CBS\CBS.log” and “%windir%\Logs\DISM\DISM.log” in the directory path and the hit Enter

These logs will show you in depth diagnosis about the issues DISM found and if the image can be repaired.

Perform the complete system image repair

Once you confirmed your system needs repair, the standard /RestoreHealth command is core tool for fixing corrupted component stores.

This command uses Windows Update as the repair source. DISM will download clean component files and replace them with your system image corrupted ones. The process is about 10 to 30 minutes depending on your internet connection and the extent of corruption.

Follow these steps:

1. Open Command Prompt as administrator

2. Execute repair command: DISM /Online /Cleanup-Image /RestoreHealth

3. Now let the process gets finished until the message pops up: “The restore operation completed successfully.”

4. Now run this command to fix any remaining issues: sfc /scannow

Across Windows 11 Home, Server edition and Enterprise /RestoreHealth process works identically. Although Enterprise and Server environment instead of Windows update use WSUS, which might require /Source parameter for specifying network repair or local source.

Controlling repair sources

The /Source and /LimitAccess parameters give you precise control over where DISM retrieves repair files, which is critical for offline repairs, air-gapped systems, or when Windows Update is unreliable.

/Source and /LimitAccess parameters provide you with precise control over

Here’s the command as an example: DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\Sources\install.wim

The /Source parameter informs DISM exactly where to find clean component files. To prevent tool from utilizing Windows update access, you can use \LimitAccess command, if the current Windows Update event is causing the problem:

Repairing offline systems

When you are servicing your system for recovery environment or if Windows will not boot, DISM offline repair capabilities are best in this specific case scenario. Successfully repairing an offline system following of these will be required.

• Windows 11 installation media or ISO file.
• Extracted or mounted ISO for accessing \Sources folder.
• Now install.esd or install.win from the folder.
• Now Matching Windows architecture or version between the target system and the source.

Then, follow these steps:

1. If your system is not booting normally then you need to access WinRE by keeping the SHIFT pressed while clicking restart and then select Troubleshoot > Advanced Options > Command Prompt.

2. Run “diskpart” and then “list volume” for identifying which volume contains your Windows installation.

Most of the times it is in the drive D:\ than in C:\.

3. You can run this offline repair command: DISM /Image:D:\ /Cleanup-Image /RestoreHealth /Source:D:\Sources\install.wim

Replace “D:\” with your actual Windows drive letter.

Automating DISM across multiple endpoints

For MSPs and IT teams which are managing hundreds or dozens of Windows 11 devices, manual DISM repairs is a nightmare and limit their scale. Basic PowerShell scripts along with RMM platform transform DISM to occasional one time fix to a continuous maintenance strategy

Get Your IT Managed Without Hassle Today: Sign Up Now