sodcalculator

10 Tech How-To

Fix DISM Error 0x800700: Find the Full Code First

Guide 10-12512 · Updated · Step by step

DISM error 0x800700 usually means a Windows system file repair failed, but the exact cause depends on the full error code that follows it. This guide shows you how to find the complete DISM error code, interpret what it means, and apply the correct fix—whether it’s a corrupted system file, a network issue, or a problem with the Windows Update service.

What You’ll Need

  • A Windows 10 or Windows 11 PC with administrative access
  • An internet connection (for most fixes, though some work offline)
  • About 15–30 minutes of time
  • Optional: a Windows installation USB or ISO if the system file source is corrupted

Step-by-Step

  1. Open Command Prompt as Administrator. Press Windows + X, select “Terminal (Admin)� or “Command Prompt (Admin)� from the menu. If prompted by User Account Control, click “Yes�.
  2. Run DISM to see the full error. Type the following and press Enter:
    DISM /Online /Cleanup-Image /RestoreHealth
    Wait for the scan to complete. It may take 10–20 minutes. When it fails, you’ll see an error like Error: 0x80070002 or 0x80070003. Write down the complete code—this is what tells you what went wrong.
  3. Decode the full code. The 0x800700 part is generic; the last two digits matter:
    • 0x80070002 – The system cannot find the file specified. This usually means DISM can’t locate the source files it needs.
    • 0x80070003 – The system cannot find the path specified. Often a network or path issue.
    • 0x80070005 – Access denied. Run Command Prompt as administrator, or check permissions.
    • 0x80070020 – The process cannot access the file because it is in use. Close other programs or restart in Safe Mode.
    • 0x8007007E – The specified module could not be found. Usually a missing system file.
  4. If the error is 0x80070002 or 0x80070003, provide a source. DISM needs a known-good copy of the Windows system files. Use the Windows Update source by running:
    DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccess
    Replace C:\RepairSource\Windows with the path to your installation media (e.g., D:\sources\install.wim). To extract the install.wim, mount your ISO or USB and copy the install.wim file to a folder on your hard drive, then run:
    dism /Get-WimInfo /WimFile:C:\RepairSource\install.wim
    Find the index number for your Windows edition, then extract it:
    dism /Mount-Wim /WimFile:C:\RepairSource\install.wim /index:1 /MountDir:C:\RepairSource\Windows
    After mounting, run the RestoreHealth command with the source path.
  5. If the error is 0x80070005, fix permissions. Right-click Command Prompt and choose “Run as administrator�. If that doesn’t help, check that the Windows Modules Installer service is running: press Win + R, type services.msc, find “Windows Modules Installer�, set its Startup type to “Manual� and start it if it’s stopped.
  6. If the error is 0x80070020, close conflicting processes. Restart your PC in Safe Mode (Settings > System > Recovery > Advanced startup, then choose Troubleshoot > Advanced options > Startup Settings > Restart, then press 4). Run DISM again in Safe Mode.
  7. Run SFC after DISM succeeds. Once DISM completes without error, run:
    sfc /scannow
    This will repair any remaining corrupted system files using the freshly restored image.
  8. Restart your computer. After SFC finishes, reboot and check if the original problem (e.g., Windows Update failure, app crash) is resolved.

Common Mistakes

  • Ignoring the full error code. 0x800700 is only the beginning—the last two digits determine the fix. Don’t stop at “0x800700�.
  • Running DISM without admin rights. DISM requires elevated privileges. If you see “Access denied�, you’re not running as administrator.
  • Using the wrong source path. If you point to a file that doesn’t exist or is not a valid Windows image, you’ll get the same 0x80070002 error.
  • Skipping the /LimitAccess flag. Without it, DISM may try to use Windows Update and fail again if the network is the issue.
  • Not waiting long enough. DISM can appear stuck at 20% for several minutes. Let it finish; interrupting it can cause more corruption.

Tips

  • Use the exact error code in a web search. Searching “DISM 0x80070005� will give you targeted solutions much faster than searching “DISM error�.
  • Create a system restore point first. Before making changes, type rstrui in the Run dialog to create a restore point. This gives you a rollback option.
  • Keep your Windows installation media handy. A USB or ISO with the same version (and ideally the same language) as your installed Windows is the most reliable source.
  • Run DISM in an elevated PowerShell if Command Prompt fails. Right-click the Start button and choose “Windows PowerShell (Admin)� or “Terminal (Admin)�.
  • Check disk space. DISM needs about 2–3 GB of free space to work. Run cleanmgr to free up space if needed.

Troubleshooting

If DISM still fails after following the steps above, try these additional approaches:

  • Run DISM with the /Cleanup-Image /StartComponentCleanup option to remove old versions of updated components:
    DISM /Online /Cleanup-Image /StartComponentCleanup
    Then retry RestoreHealth.
  • Check the CBS log. After a failed DISM run, open C:\Windows\Logs\CBS\CBS.log in Notepad. Look for lines containing “Error� or “Failed� near the end. The log often gives a more specific reason (e.g., a particular DLL missing).
  • Use the Windows Update Troubleshooter. Go to Settings > System > Troubleshoot > Other troubleshooters, run “Windows Update�. This can fix underlying update service issues that block DISM.
  • Reset Windows Update components manually. Stop the BITS and Windows Update services, rename the SoftwareDistribution and catroot2 folders, then restart the services. This is a common fix for update-related DISM errors.
  • If all else fails, perform an in-place upgrade repair. Download the Windows 10 or 11 Media Creation Tool, run it, and choose “Upgrade this PC now�. This reinstalls Windows while keeping your files and apps. It’s the most thorough fix for persistent DISM errors.

Frequently Asked Questions

Why does DISM return 0x80070002 even though I have internet?

0x80070002 means DISM can’t find the source files. Even with internet, Windows Update might be blocked by a firewall, proxy, or corrupted update cache. Using a local source (installation media) bypasses the network entirely.

Can I run DISM offline?

Yes, you can repair an offline Windows image by booting from installation media and running DISM with the /Image parameter, but it’s more complex. For most users, running it online in Safe Mode is simpler.

What’s the difference between SFC and DISM?

SFC (System File Checker) scans and repairs protected system files using the local cache. DISM repairs the underlying Windows system image itself, which is often needed before SFC can work. Run DISM first, then SFC.

Is it safe to use a Windows ISO from a different version (e.g., Windows 10 21H2 vs 22H2)?

Using a different minor version can work, but it may cause DISM to downgrade some components. It’s best to use the same version and language as your installed Windows. If you’re unsure, try the Windows Update source first.

How long does DISM /RestoreHealth take?

It typically takes 10–20 minutes, but can take up to an hour on slower machines or if the source is a USB drive. The progress bar may stay at 20% for a long time—that’s normal.

Will DISM delete my personal files?

No. DISM only repairs Windows system files. Your documents, photos, and apps are untouched. Always back up important data before major repairs, but DISM itself is non-destructive.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →