How to Fix DISM Error 0x800f0906 (Source Files Could Not Be Downloaded)

By ErrorFix · Updated October 19, 2026 · 7 min read

What error 0x800f0906 means

DISM (Deployment Image Servicing and Management) is the tool that repairs Windows itself: when you run DISM.exe /Online /Cleanup-image /Restorehealth, it compares your system files against known-good copies and replaces anything damaged. By default, it pulls those good copies from Windows Update over the internet. Error 0x800f0906 means that download step failed — DISM never got the source files, so the repair aborted before fixing anything.

The important thing to understand is that this error says nothing about your actual system damage. Your Windows files might be perfectly repairable; the tool simply cannot reach the spare parts. The same failure mode also hits anyone installing .NET Framework 3.5 from Control Panel or from a DISM command, because that install pulls feature files through the same download path. Work through the steps below in order — most people fix this without touching their files or reinstalling Windows.

Common causes

• No usable internet for the download: a metered connection setting, an unstable signal, or a captive network means DISM's file fetch never completes, even if the browser seems to work.
• VPN or proxy interference: tunnels and proxies can redirect or throttle Windows Update traffic, so DISM's download quietly fails behind them.
• Stalled Windows Update download cache: a frozen session inside the SoftwareDistribution folder makes every retry hit the same broken download instead of starting fresh.
• Corporate policy or WSUS redirection: on work PCs, group policy can point Windows Update at an internal server that has no repair files, leaving DISM with nothing valid to download from.
• Component store too damaged for online repair: when the local repair metadata itself is wrecked, DISM cannot even figure out what to download, and the fetch fails with 0x800f0906.

How to fix error 0x800f0906 — step by step

Work through these fixes in order. Most people get a working DISM repair by step 4.

1. Confirm the PC has a working internet connection. DISM's default repair pulls fresh files from Windows Update online, so a metered, blocked, or unstable connection is the most common reason the source files could not be downloaded. Open Settings, go to Network & internet, select your connection, and switch off Metered connection. Open a browser and load a page to prove real internet access, not just a Wi-Fi icon. If you use a VPN or proxy, disconnect it and retry the DISM command.
2. Run the System File Checker first, then retry DISM. Right-click Start and choose Terminal (Admin), then run sfc /scannow and let it finish. SFC repairs files from the local component store without downloading anything, and it often fixes enough damage that a second DISM attempt succeeds where the first one failed. When SFC finishes, restart the PC and run DISM.exe /Online /Cleanup-image /Restorehealth again.
3. Reset the Windows Update components. DISM fetches its source files through the Windows Update pipeline, so a broken pipeline means a broken download. In an admin terminal, stop the services: net stop wuauserv, net stop cryptSvc, net stop bits, net stop msiserver. Then rename the caches: ren C:\Windows\SoftwareDistribution SoftwareDistribution.old and ren C:\Windows\System32\catroot2 catroot2.old. Restart the services: net start wuauserv, net start cryptSvc, net start bits, net start msiserver. A stalled download session in these caches is a classic reason the source files fail to download, and this rebuilds the whole pipeline.
4. Point DISM at a Windows install media source. Download the Windows Media Creation Tool from Microsoft, create an ISO for your version of Windows, and double-click the ISO to mount it (note the drive letter, for example E:). Then in an admin terminal run DISM.exe /Online /Cleanup-image /Restorehealth /Source:WIM:E:\sources\install.wim:1 /LimitAccess. The /Source switch hands DISM a local copy of the repair files, and /LimitAccess stops it from trying the internet at all — which bypasses whatever was blocking the download.
5. Use an ESD source if your media has install.esd instead of install.wim. Some official ISOs ship with sources\install.esd rather than install.wim, and DISM will fail if you point it at the wrong file. Open the mounted ISO's sources folder and check the actual filename, then adjust the command: DISM.exe /Online /Cleanup-image /Restorehealth /Source:ESD:E:\sources\install.esd:1 /LimitAccess. Keep the index number 1 unless you know your edition needs a different index.
6. Perform an in-place upgrade repair if DISM still cannot repair. Keep the Windows ISO mounted, open it, and run setup.exe from inside Windows (not by booting from the media). Choose to keep personal files and apps when prompted, and let the installer refresh Windows. This reinstalls every system component from the local media and resolves 0x800f0906 situations where the component store is too damaged for DISM to fix, with your files and programs intact.

Did this fix it? Quick checklist

• DISM /Restorehealth completes and reports that the restore operation completed successfully
• A follow-up sfc /scannow reports no integrity violations
• The original symptom (failed update, broken feature, or crash) no longer appears
• DISM no longer throws 0x800f0906 on a plain retry

If the error persists after all six steps, double-check the ISO matches your Windows version and edition — a Windows 10 ISO cannot repair a Windows 11 install, and the repair will silently fail. Also confirm you are running the terminal as administrator (the title bar should say Administrator), since DISM without elevation produces misleading errors. If a work PC is involved, ask the IT admin whether group policy redirects Windows Update to an internal server; that policy is a frequent hidden cause of 0x800f0906, and only the admin can exempt the machine or provide the approved repair source.