Fix it now
0x800F0906 is CBS_E_DOWNLOAD_FAILURE: content download failed for a Feature on Demand or for inbox corruption repair. The machine either has no route to Windows Update, or policy sends it somewhere that carries no repair payload. Supplying a source of the same build finishes the job offline.
DISM /Get-WimInfo /WimFile:D:\sources\install.wim
DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:D:\sources\install.wim:1 /LimitAccess
DISM /Online /Cleanup-Image /ScanHealth
- Check the installed build with
winverand note the edition, then mount an ISO patched to at least that level. - Read the WimInfo output and pick the index whose edition matches the machine. The first index is not always the right one.
- To enable the older .NET Framework instead of repairing the store, point at the side-by-side folder:
DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /Source:D:\sources\sxs /LimitAccess. - If the machine is centrally managed, check Computer Configuration – Administrative Templates – System – ‘Specify settings for optional component installation and component repair’ before blaming the network.
/LimitAccess prevents DISM contacting Windows Update for repair of online images. Keep it on while diagnosing: it turns a silent fallback into an honest failure, so you know whether your source was actually used.
If ScanHealth comes back clean, or the feature now appears as installed, you are done. If your source is being rejected, the next section explains the rule it is failing.
Why it happens
Windows does not carry the files for everything it can install. Optional features and some repair components are represented in the store by metadata with no payload behind them, and the payload is fetched when it is needed. By default that fetch goes to Windows Update, regardless of how the machine gets its ordinary updates. 0x800F0906 is that fetch failing.
The default is what breaks on managed machines. A client pointed at an internal update server is redirected for payload as well, and internal update servers do not host feature and repair payload unless somebody deliberately arranged it. The machine is online, the update server is reachable, and DISM still comes back empty-handed. There is a policy that lets repair content and optional features come straight from Windows Update while everything else stays managed, and switching it on is often the whole fix.
Supplying a source on the command line sidesteps all of that, provided the source is acceptable. Microsoft publishes the rule that catches most people: make sure the source is patched to the latest cumulative update, because if the target is patched to a higher level than the source, adding features or repairing the operating system may fail. The source needs the files the target expects, and older media does not have them.
The companion codes describe the neighbouring failures. 0x80070490 is ERROR_NOT_FOUND, decimal 1168, which the Windows Update tables render as ‘Windows could not search for new updates’. 0x800F0900 is CBS_E_XML_PARSER_FAILURE, a generic XML parsing failure inside servicing rather than an internal error of unknown kind. 0x8024002C is WU_E_BIN_SOURCE_ABSENT: a delta-compressed update that could not be installed because it required the source.
The machine has no usable route to Windows Update
You have this one if An isolated network, an inspecting proxy, or a server that is deliberately offline. Other Windows Update traffic fails too.
- Mount media patched to at least the machine’s level and supply it as the source with
/LimitAccess. - For .NET Framework, point at the
sources\sxsfolder on the media rather than at install.wim. - Where a proxy is in the way and has to stay, ask for the update endpoints to bypass inspection.
- Rerun the operation and read the result rather than assuming it worked.
Policy redirects payload to an internal update server
You have this one if Managed machines fail while an unmanaged machine on the same network succeeds.
- Open Computer Configuration – Administrative Templates – System and find ‘Specify settings for optional component installation and component repair’.
- Either set an alternate source file path pointing at a share holding the media, or enable the option to download repair content directly from Windows Update.
- Force a policy refresh and confirm the setting reached the machine.
- Keep supplying the source on the command line for one-off repairs rather than changing policy for a single machine.
The source is at a lower patch level than the target
You have this one if You supplied media and the operation still fails, sometimes reporting that the source files could not be found.
- Check the build with
winverand compare it against the media. Newer media repairing an older machine is usually fine; older media repairing a newer machine usually is not. - Run
DISM /Get-WimInfo /WimFile:D:\sources\install.wimand choose the index matching the installed edition. - If the media ships install.esd, export the correct index to a WIM first and point at that.
- Rerun with the corrected source path and index.
The feature needs separate on-demand media
You have this one if Store repair works with the installation ISO, but one specific optional feature still fails.
- Check whether the feature is distributed as a Feature on Demand rather than as part of the installation media.
- Obtain the matching on-demand media for the same build through your volume licensing or admin portal.
- Point the source at that media instead.
- Enable the feature again and confirm it appears as installed afterwards.
The store is damaged rather than merely missing payload
You have this one if Repairs with a good source still fail, and other servicing operations report inconsistency.
- Run
DISM /Online /Cleanup-Image /ScanHealthand read what it reports. - Repair with the matching source, then run
sfc /scannow. - Read
%windir%\Logs\DISM\dism.logfor the component that could not be restored and which source was used. - If it cannot be repaired at all, plan an in-place upgrade with media patched at least as far as the machine.
Full reference
The source formats DISM accepts
| Form | What to pass |
|---|---|
| A mounted Windows image | The path to the Windows directory inside it, such as c:\mount\Windows |
| A running Windows installation shared on the network | A share pointing at that installation’s Windows folder |
| The side-by-side folder from media | z:\sources\SxS, which is what optional features such as NetFx3 need |
| A WIM holding several editions | WIM:D:\sources\install.wim:1, where the number is the index |
| Windows Update | The default, used when no source is supplied and /LimitAccess is absent |
A network share works as well as a local drive letter, provided the account running DISM can read it. That is the usual arrangement for fleets that cannot reach Windows Update: one share holding an extracted sources folder, referenced by policy or on the command line.
Repairing versus enabling a feature
rem repair the component store from a WIM index
DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:D:\sources\install.wim:1 /LimitAccess
rem enable .NET Framework 3.5 from the side-by-side folder
DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /Source:D:\sources\sxs /LimitAccess
rem list the editions and indexes inside an image
DISM /Get-WimInfo /WimFile:D:\sources\install.wim
Those two operations take different sources and people mix them up. Store repair wants an image; a feature such as NetFx3 wants the side-by-side folder. Pointing the feature at install.wim, or the repair at the sxs folder, produces the same download failure you started with.
The codes in this article
| Code | Published name | Reading |
|---|---|---|
| 0x800F0906 | CBS_E_DOWNLOAD_FAILURE | Content download failed for a Feature on Demand or for inbox corruption repair |
| 0x80070490 | ERROR_NOT_FOUND | Decimal 1168, element not found. Rendered in the Windows Update tables as ‘Windows could not search for new updates’ |
| 0x800F0900 | CBS_E_XML_PARSER_FAILURE | A generic XML parsing failure in servicing |
| 0x8024002C | WU_E_BIN_SOURCE_ABSENT | A delta-compressed update could not be installed because it required the source |
The policy that decides where payload comes from
‘Specify settings for optional component installation and component repair’ lives under Computer Configuration – Administrative Templates – System. It carries an alternate source file path and an option to download repair content directly from Windows Update. On a managed estate this is usually the setting that matters, because it applies to every machine rather than to the one you happen to be repairing. Set it once, confirm it has landed on a test machine, and the command-line source becomes a diagnostic tool rather than a routine step.
When the source is right and it still fails
- Read
%windir%\Logs\DISM\dism.log. It records the source DISM used, which is how you prove whether/Sourcewas honoured. - Read
%windir%\Logs\CBS\CBS.logfor the component that could not be restored. - Check the account. A network share source needs the account running DISM to be able to read it, and the system account is not always that account.
- Check whether the machine has had a component cleanup with a reset base run against it. After that, a source is mandatory on every repair.
- If several unrelated components fail, treat the disk as a suspect before the store.
An in-place upgrade rewrites the operating system. Take a full backup first, check you hold any disk encryption recovery keys, and allow for a long reboot cycle.
When a licence is the actual fix
Installation media is free to download and using it as a DISM source consumes no licence, so most readers finish this article without spending anything. A licence matters in two situations: when the machine has to change edition, for example from Home to Windows 11 Pro so it can be domain-joined and managed, and when the installed build is old enough that current media will not repair it and an upgrade is the realistic route. Arco can supply a Windows 11 Pro upgrade licence and confirm which edition the machine currently holds before you commit to that path.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0x800F0906 |
CBS_E_DOWNLOAD_FAILURE: content download failed for a Feature on Demand or for inbox corruption repair | Microsoft Learn |
0x80070490 |
ERROR_NOT_FOUND, decimal 1168: element not found. Rendered by the Windows Update tables as ‘Windows could not search for new updates’ | Microsoft Learn |
0x800F0900 |
CBS_E_XML_PARSER_FAILURE: a generic XML parsing failure inside servicing | Microsoft Learn |
0x8024002C |
WU_E_BIN_SOURCE_ABSENT: a delta-compressed update could not be installed because it required the source | Microsoft Learn |
Confirm the fix worked
- Run
DISM /Online /Cleanup-Image /ScanHealthand confirm no component store corruption is reported. - If you were enabling a feature, confirm it now shows as installed in Optional features.
- Run
sfc /scannowand confirm no integrity violations remain. - Read the tail of
%windir%\Logs\DISM\dism.logand confirm the source you supplied was the one used. - Reinstall the update that originally failed and confirm it completes.
Questions people ask about this
Do I have to pay for the ISO?
No. Microsoft publishes installation media for current Windows versions at no charge, and using it as a repair source neither consumes an activation nor requires a key. What matters is that the media matches your edition and is patched at least as far as the machine.
What does /LimitAccess actually change?
It prevents DISM contacting Windows Update for repair of online images. During troubleshooting that is exactly what you want, because a silent fallback makes it impossible to tell whether your source was used or ignored.
Can I use a network share as the source?
Yes, provided the account running DISM can read it. A share holding an extracted sources folder or a mounted image behaves like a local drive letter, and it is the usual approach for fleets that cannot reach Windows Update.
Why does .NET Framework 3.5 need this at all?
Its payload is not shipped in the installed image. Windows carries the metadata for the feature and fetches the files when you enable it, which is why enabling it on an isolated machine always needs a source. Point it at the sources\sxs folder, not at install.wim.
My media is newer than the machine. Is that a problem?
Usually not. The documented rule runs the other way: a target patched to a higher level than the source can fail because it needs files the source does not carry. Newer media is the safer mistake.
