sodcalculator

10 Tech How-To

Fix DISM Error 0x800f0906 on Windows 10 v1703

Guide 10-57675 · Updated · Step by step

DISM error 0x800f0906 on Windows 10 version 1703 (the Creators Update) means the Deployment Imaging Service and Management tool cannot download the files it needs from Windows Update to repair your system image. The fix usually involves pointing DISM to a local source, repairing the Windows Update component, or clearing the download cache — and this article walks through each method in order of likelihood.

Why This Error Happens on Version 1703

DISM (Deployment Image Servicing and Management) is a command-line tool that repairs the Windows system image and the component store that Windows Update relies on. When you run DISM /Online /Cleanup-Image /RestoreHealth, it tries to pull missing or corrupted files from Windows Update. Error 0x800f0906 specifically means “the source files could not be downloaded.”

On Windows 10 version 1703, this error became common for two reasons:

  • Windows Update client corruption: The very component that DISM uses to download files is broken, so the download fails.
  • Network or proxy interference: A firewall, VPN, or corporate proxy can block the connection to Microsoft’s update servers.
  • Outdated servicing stack: Version 1703 is an older release, and its servicing stack may not handle newer update metadata correctly.

Importantly, this error is not a sign that your hard drive is failing or that your files are at risk. It only means the repair tool couldn’t fetch its source files.

Before You Start: Check Your Internet and Run as Admin

DISM requires administrative privileges, and a stable internet connection is essential for the default repair path. Open Command Prompt as administrator by right-clicking the Start button and selecting “Command Prompt (Admin)” or “Windows PowerShell (Admin).” If you see a User Account Control prompt, click Yes.

Also verify that Windows Update itself can check for updates. Go to Settings → Update & Security → Windows Update and click “Check for updates.” If that fails with a different error, fix that first — DISM depends on the same underlying service.

Method 1: Use a Local Source Instead of Windows Update

The most reliable fix for 0x800f0906 is to bypass Windows Update entirely and give DISM a local copy of the system files. You need a Windows 10 installation media (USB or ISO) that matches your system’s build — for version 1703, that’s build 15063. If you have a different build, the repair may not work correctly.

  1. Mount the ISO or insert the USB drive and note its drive letter (e.g., D:).
  2. Open Command Prompt as administrator.
  3. Run the following command, replacing D: with your media’s drive letter:
    DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\sources\install.wim /LimitAccess
  4. If the install.wim file is not found, your media may use install.esd instead. In that case, you need to extract the index first — see the next section.

The /LimitAccess flag tells DISM to only use the specified source and not contact Windows Update. This avoids the exact failure point that caused the error.

Method 2: Extract install.esd to a WIM File

Many Windows 10 ISOs use a compressed install.esd file instead of install.wim. DISM cannot read .esd directly as a source in this context, so you must convert it. Here’s how:

  1. Create a folder on your C: drive, e.g., C:\mount.
  2. Run this command to see which index corresponds to your edition (usually index 1 for Home, 2 for Pro):
    DISM /Get-WimInfo /WimFile:D:\sources\install.esd
  3. Export the desired index to a WIM file:
    DISM /Export-Image /SourceImageFile:D:\sources\install.esd /SourceIndex:1 /DestinationImageFile:C:\mount\install.wim /Compress:max
  4. Now use that WIM as the source:
    DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\mount\install.wim /LimitAccess

This conversion can take 10–20 minutes and requires about 10 GB of free space. After the repair, you can delete the C:\mount folder.

Method 3: Repair Windows Update Components First

If you don’t have installation media, you can try to fix the Windows Update client itself. The Windows Update Troubleshooter (Settings → Update & Security → Troubleshoot → Additional troubleshooters → Windows Update) can reset the update cache and repair corrupted files automatically. Run it and restart your PC, then try DISM again.

If the troubleshooter doesn’t help, manually reset the Windows Update components:

  1. Open Command Prompt as administrator.
  2. Stop the relevant services:
    net stop wuauserv
    net stop cryptSvc
    net stop bits
    net stop msiserver
  3. Rename the SoftwareDistribution folder (this is safe — it will be recreated):
    ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
  4. Rename the Catroot2 folder:
    ren C:\Windows\System32\catroot2 catroot2.old
  5. Restart the services:
    net start wuauserv
    net start cryptSvc
    net start bits
    net start msiserver
  6. Restart your PC and try the DISM restore again.

This clears corrupted update metadata that may be causing the download failure.

Method 4: Clear the DISM Scratch Folder

DISM uses a temporary folder (default: C:\Windows\Temp) for its own operations. If that folder is full, corrupted, or has permission issues, the download can fail with 0x800f0906. You can specify a different scratch directory:

  1. Create a folder, e.g., C:\scratch.
  2. Run:
    DISM /Online /Cleanup-Image /RestoreHealth /ScratchDir:C:\scratch

Make sure the folder has at least 2 GB of free space. This is a quick test that often resolves the error if the default temp location is the culprit.

What to Do If DISM Still Fails

If none of the above works, the system image may be too damaged for DISM to repair in place. Your next options are:

  • Run System File Checker (SFC): sfc /scannow after DISM. Sometimes SFC can fix files that DISM couldn’t, though the reverse order is more common.
  • Perform an in-place upgrade repair: Run the Windows 10 setup.exe from your installation media while keeping your files and apps. This reinstalls the OS without wiping your data and often fixes deep corruption. Choose “Keep personal files and apps” when prompted.
  • Reset this PC: Settings → Update & Security → Recovery → Reset this PC. Choose “Keep my files” to preserve your personal data, but note that installed apps will be removed.

An in-place upgrade is less drastic than a reset and usually resolves persistent DISM errors on version 1703.

Frequently Asked Questions

Does this error mean my PC is infected with malware?

No. Error 0x800f0906 is a servicing failure, not a security alert. It indicates that DISM couldn’t download repair files, which can happen due to network issues, corrupted update components, or a mismatched local source. If you suspect malware, run a separate antivirus scan — but this error alone doesn’t indicate an infection.

Can I use a Windows 10 ISO from a different version (e.g., 21H2) as the source?

It’s not recommended. DISM expects source files from the same build (or a newer build in some cases, but mixing versions can cause other errors). For version 1703, use a 1703 ISO. If you can’t find one, the in-place upgrade with a newer ISO is a better path — it will upgrade your system while repairing it.

How long does the DISM repair take?

With a local source, it typically takes 10–30 minutes depending on your disk speed and CPU. If it uses Windows Update, it can take longer, especially on a slow connection. If it appears stuck at 20% for over an hour, it may have hung — press Ctrl+C to cancel and try a different method.

Will I lose my files if I run DISM?

No. DISM only repairs system files and the component store. Your personal files, settings, and installed applications remain untouched. The same is true for SFC. Only the in-place upgrade or reset options have the potential to affect apps, and even then you can choose to keep your files.

Why does the error mention “source files could not be downloaded” when I’m online?

This message means DISM’s connection to Windows Update failed, not that your internet is down. It could be a proxy, a firewall rule, or a corrupted Windows Update service. That’s why using a local source with /LimitAccess is the most reliable fix — it removes the network dependency entirely.

Is it safe to delete the SoftwareDistribution.old folder after resetting?

Yes, once you’ve confirmed Windows Update works and DISM completes successfully, you can delete C:\Windows\SoftwareDistribution.old to free up space. It’s only a backup of the old update cache. The same applies to catroot2.old.

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 →