DISM Not Working in Windows 11/10 [Here's How to Fix]

DISM, short for Deployment Image Servicing and Management, is a built-in Windows tool that helps repair a damaged system image. It is often used alongside the System File Checker (SFC) to fix corrupted files that cause crashes, update failures, or general instability.

However, many users report that DISM fails to run, often getting stuck at a certain percentage, freezing, or throwing an error code instead of completing the repair. This issue can be frustrating, especially since DISM itself is usually the tool people turn to when something else in Windows is already broken.

This problem almost always comes down to a small number of common causes, such as a corrupted component store, a blocked internet connection, incorrect system time, or interference from third-party software.

In this guide, you will find a complete walkthrough to resolve this issue easily!.

Table of Contents

DISM Not Working in Windows 11/10 [Complete Steps]

Most of the time, the tool fails because it cannot reach the files it needs to repair your system, either because your internet connection is blocked, the built-in repair source is damaged, or a background service required for the operation is not running properly.

Sometimes the issue is even simpler, such as not running the tool with the correct permissions. The steps below are arranged in the order you should try them, starting with the easiest checks and moving toward more advanced solutions.

Work through them one at a time, and test DISM again after each step to see if the problem has been resolved.

Step 1: Run Command Prompt as an Administrator

One of the most common reasons DISM refuses to work is that it was not launched with the correct permissions.

DISM needs full administrative access to your system in order to scan, repair, and replace protected files, and if it does not have this access, it will either fail immediately or stop partway through with an error message.

To fix this, click on the Start menu and type Command Prompt into the search bar. Instead of clicking on the result normally, right-click on it and choose Run as administrator from the menu that appears. A confirmation window called User Account Control may pop up asking if you want to allow the app to make changes to your device. Click Yes to continue.

Once the Command Prompt window opens with the title bar showing Administrator, you know you are running it correctly.

Step 2: Check Your Internet Connection

DISM often needs to download certain files from Microsoft’s servers, especially when your local repair files are damaged or missing. If your internet connection is unstable, restricted, or completely offline, the DISM command will fail or hang indefinitely.

Start by opening any web browser and visiting a website to confirm that your connection is active. If it loads normally, your internet is likely fine, but if pages are slow to load or will not load at all, try restarting your router and modem by unplugging them for about thirty seconds before plugging them back in.

If you are using a VPN or a proxy server, temporarily disable it, since these tools sometimes block the specific connections DISM needs to reach Microsoft’s update servers.

Once your connection is confirmed stable, return to your administrator Command Prompt window and try running the DISM command again.

Step 3: Verify the Windows Time and Date Settings

This step is often overlooked, but an incorrect system clock can prevent DISM from verifying secure connections to Microsoft’s servers, which causes the process to fail.

To check this, click on the date and time display in the bottom right corner of your screen, then select Adjust date and time from the menu. Make sure the toggle next to Set time automatically is turned on.

If it is already on but the time still looks wrong, turn it off, wait a few seconds, then turn it back on to force Windows to resync with the internet time server. Also confirm that your time zone is set correctly for your location.

Once your clock is accurate, close the settings window and try running DISM once more.

Step 4: Run the DISM Command With the RestoreHealth Option

If the earlier steps did not solve the problem, it is time to run the core repair command itself.

In your administrator Command Prompt window, type the following command exactly as written and press Enter: dism /online /cleanup-image /restorehealth.

This process can take anywhere from ten to thirty minutes, and it is completely normal for the progress percentage to appear frozen at certain points, particularly around 20 percent and 40 percent.

Avoid closing the window or restarting your computer during this time, even if it seems stuck, since interrupting it can cause further damage.

Once the process finishes, it will tell you whether the repair was successful or if it encountered an error, which will help guide your next step.

Step 5: Use Installation Media as a Repair Source

If DISM cannot connect to Microsoft’s online servers at all, you can point it toward a local repair source instead, such as a Windows installation USB drive or ISO file.

After inserting your installation media, note the drive letter it was assigned, then open Command Prompt as an administrator and run a command that directs DISM to use the install.wim file found on that drive as its source, rather than relying on the internet.

This method is especially useful for users with restricted or unreliable internet access, since it bypasses the online connection entirely and lets the repair process work with local files.

Step 6: Restart Essential Windows Services

DISM relies on several background services to function correctly, including the Windows Update service, the Background Intelligent Transfer Service, and the Cryptographic service.

If any of these have stopped running or become corrupted, DISM may fail without a clear explanation.

To check them, type services.msc into the Start menu search bar and press Enter. In the list that appears, locate each of these services one by one, right-click on it, and select Restart.

If a service shows as Disabled, right-click it, choose Properties, and change the Startup type to Automatic before starting it manually.

Step 7: Run SFC After DISM Completes

Once DISM finishes running successfully, it is a good idea to follow up with the System File Checker to catch any remaining issues.

In the same administrator Command Prompt window, type sfc /scannow and press Enter.

This tool scans all protected system files and automatically replaces any that are corrupted, using the healthy component store that DISM just repaired.

Running these two tools together gives Windows the best chance of fully recovering from file corruption issues.

FAQs

Why does DISM get stuck at a certain percentage?

This is usually normal behavior rather than an actual freeze. The process can pause for several minutes at points like 20 percent or 40 percent while it works through larger file sets, so it is best to leave it running for at least thirty minutes before assuming it has failed.

Can I use DISM without an internet connection?

Yes, as long as you have access to Windows installation media, you can direct DISM to use that as its repair source instead of downloading files online.

Is it safe to restart my computer if DISM freezes?

It is best to avoid restarting unless the tool has clearly failed with an error message, since interrupting the process midway can leave your system files in a worse state than before.

Do I need to run SFC before or after DISM?

Running DISM first and then SFC afterward is the recommended order, since DISM repairs the component store that SFC depends on to fix individual files.

Summary

DISM not working in Windows 11 or 10 is a common problem, but it is almost always fixable once you understand the underlying cause.

Starting with simple checks like running Command Prompt as an administrator, confirming your internet connection, and verifying your system clock resolves the issue for many users right away.

If the problem persists, running the core DISM repair command, switching to installation media as a source, or restarting essential background services will usually clear things up.

Finishing with an SFC scan ensures your system files are fully restored.