Fix it now
0xC1900130 is MOSETUP_E_INSTALL_HASH_MISSING – the install cannot continue because the instance hash was not found. 0x80190001 is an unexpected error downloading the files required for the upgrade, and Microsoft’s published mitigation for it is to download and run the media creation tool. Both mean setup never received a complete, verified payload.
net stop wuauserv
net stop bits
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
net start bits
net start wuauserv
- Check free space on the system drive first. A feature update needs the download, the expanded image and rollback headroom, so tens of gigabytes rather than a few.
- Run the commands above and restart. Renaming the folder discards the datastore and any partly downloaded payload, and Windows rebuilds both.
- Clear the peer cache in an elevated PowerShell session:
Delete-DeliveryOptimizationCache -Force. - Retry from Settings, Windows Update, and watch whether the download percentage moves at all. Nothing moving and a stall part way are different problems.
- If it fails again, stop fighting the download. Get the ISO, mount it, and run
setup.exe /auto upgrade /dynamicupdate disablefrom the mounted drive – which is Microsoft’s own escalation for 0x80190001.
Renaming SoftwareDistribution also clears update history. Nothing installed is removed, but the list in Settings starts again from empty.
If the upgrade downloads and starts, you are done. If it still will not, the next section explains what the hash codes actually distinguish and where the delivery is breaking.
Why it happens
A feature update is not one file arriving. The client is offered an update, resolves it to a payload, downloads that payload in pieces – possibly from peers as well as from Microsoft – and then hands setup something it can verify. The codes on this page mark different points in that chain, and reading which one you have saves a great deal of guessing.
The two hash codes are the most useful and the most often confused. 0xC1900130 is MOSETUP_E_INSTALL_HASH_MISSING: the install cannot continue because the instance hash was not found. 0xC1900131 is MOSETUP_E_INSTALL_HASH_MISMATCH: the instance hash does not match. Missing and mismatched are different diagnoses. A missing hash usually means the state that tied the download to the offer is gone – an interrupted or cancelled attempt, a rebuilt datastore, a client that has moved on. A mismatch means the hash is there and the content does not agree with it, which is a statement that something altered or truncated the payload in transit.
0x80190001 is the transport reporting an unexpected error while downloading the files required for the upgrade. Microsoft’s published mitigation is short and pragmatic: download and run the media creation tool. That is worth taking seriously rather than treating as a last resort – Microsoft’s own answer to this code is to stop using the delivery path that is failing.
0x8007000D is ERROR_INVALID_DATA, and Microsoft’s Windows Update description is that data that is not valid was downloaded or corruption occurred, with the mitigation to redownload the update and start the installation again. 0x80246009 is WU_E_DM_BITSTRANSFERERROR: a download manager operation failed because of an unspecified BITS transfer error – the layer beneath, saying the transfer itself went wrong.
Cached download state no longer matches the offer
You have this one if 0xC1900130, or a download that restarts from zero on every attempt after a previous run was interrupted.
- Stop the Windows Update and BITS services, rename
C:\Windows\SoftwareDistribution, and start them again. - Restart the machine so nothing holds a handle on the old folder.
- Retry and let it run without cancelling part way, which is what creates the mismatch in the first place.
- Delete the renamed folder to reclaim the space once the upgrade has succeeded.
Content is arriving altered or truncated
You have this one if 0xC1900131 or 0x8007000D: the payload completes and then fails verification.
- Suspect anything in the path that rewrites content: an inspecting proxy, a caching appliance, a filtering gateway.
- Ask for the Windows Update host names to be exempted from inspection and content rewriting, and for range requests to be allowed through.
- Prove the point by running the same update over a different connection before changing anything on the network.
- If it verifies elsewhere, the machine is fine and the path is not.
Delivery Optimization is serving damaged or unreachable peer content
You have this one if Several machines on one subnet stall at the same point, or a download sits at a percentage with no traffic to Microsoft.
- Look at the current state with
Get-DeliveryOptimizationStatusin an elevated PowerShell session. - Clear the cache with
Delete-DeliveryOptimizationCache -Force. - Take peering out of the picture temporarily through Settings, Windows Update, Advanced options, Delivery Optimization, or the matching policy on a managed fleet.
- Retry, and reintroduce peering afterwards with the cache empty.
There is no room for the download and its expansion
You have this one if 0x8007000D or a failure as the download finishes, on a machine with only a handful of gigabytes free.
- Free space with Disk Cleanup, Clean up system files, including previous installations and delivery optimisation files.
- Turn off hibernation if the machine does not need it:
powercfg /hibernate off. - Retry. If the drive is simply small, run the upgrade from mounted media so the source does not have to live on the system disk as well.
The offer is coming from somewhere that cannot deliver it
You have this one if Managed machines fail while unmanaged ones on the same network succeed.
- Check whether policy is redirecting the client: read
WUServerunderHKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate. - Confirm the server named there still exists, still synchronises that product, and has the content approved and downloaded.
- Test with mounted ISO media, which bypasses the offer path entirely and tells you whether the machine or the source is the problem.
Full reference
What the five codes distinguish
| Code | Published meaning | What it implies |
|---|---|---|
0xC1900130 |
The instance hash was not found | The link between the offer and the download is gone |
0xC1900131 |
The instance hash does not match | Content arrived and disagrees with what was expected |
0x80190001 |
Unexpected error downloading files required for upgrade | Use the media creation tool, per Microsoft |
0x8007000D |
Invalid data was downloaded or corruption occurred | Redownload and start again |
0x80246009 |
WU_E_DM_BITSTRANSFERERROR: an unspecified BITS transfer error | The transfer layer itself failed |
Reading the behaviour rather than the code
| What you see | Likely layer |
|---|---|
| Reaches a percentage then restarts at zero repeatedly | Cached partial content no longer matching the offer |
| Never starts and fails within seconds | The offer could not be resolved to a payload |
| Fails on the office network, works on a hotspot | A proxy, filter or inspecting appliance in the path |
| Fails at one site on every machine at the same point | A shared network path or a common peer source |
| Completes, then setup reports invalid data | Content arrived corrupt and failed verification |
| Works from mounted ISO media | Confirms the fault is delivery, not the machine |
The ISO route, properly
Running the upgrade from mounted installation media is a supported in-place upgrade, not a workaround, and for 0x80190001 it is Microsoft’s own published mitigation. Mount the ISO, run setup.exe /auto upgrade from the mounted drive, and add /dynamicupdate disable if you want to stop setup fetching content mid-run over the path that has been failing. An activated machine keeps its licence and reactivates by itself.
Where the space actually goes
- The compressed payload as downloaded.
- The expanded image setup applies.
- A full copy of the current installation, kept so the machine can roll back.
- The Delivery Optimization cache, which holds content for peers as well as for this machine.
- Previous Windows installations from earlier upgrades, which Disk Cleanup removes under Clean up system files.
When it still will not download
At some point the sensible move is to stop diagnosing the delivery and get the machine upgraded. Mounted media does that. Keep one failing machine in its failed state if you need to prove where the fault is to whoever runs the network, because once the datastore is rebuilt and the peer cache is cleared, the evidence is gone. Get-WindowsUpdateLog produces a static copy of the client’s log for exactly this purpose – run it before you reset anything.
When a licence is the actual fix
Nothing above requires a purchase. If the machine is already licensed for the edition you are installing, the ISO route costs nothing and the digital licence carries across an in-place upgrade without anyone typing a key. The one case where a licence genuinely enters the picture is the moment you switch to media and find the device is not entitled to the edition on it – most often a Home machine being pointed at Windows 11 Pro media because someone wanted the management features rather than because the download failed. That is a Windows 11 Pro upgrade licence, bought for the edition change and not for the download problem, and the same stalled download would have stalled on either edition. Check what the device is actually licensed for with slmgr /dli before buying anything: a machine that is already Pro needs nothing from this section.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0xC1900130 |
MOSETUP_E_INSTALL_HASH_MISSING: the install cannot continue because the instance hash was not found | Microsoft Learn |
0x80190001 |
An unexpected error was encountered while attempting to download files required for upgrade; Microsoft’s mitigation is to use the media creation tool | Microsoft Learn |
0x8007000D |
ERROR_INVALID_DATA: data that is not valid was downloaded or corruption occurred; redownload the update and start the installation again | Microsoft Learn |
0xC1900131 |
MOSETUP_E_INSTALL_HASH_MISMATCH: the install cannot continue because the instance hash does not match | Microsoft Learn |
0x80246009 |
WU_E_DM_BITSTRANSFERERROR: a download manager operation failed because of an unspecified BITS transfer error | Microsoft Learn |
Confirm the fix worked
- The download reaches completion and the machine restarts into the upgrade rather than returning to the desktop.
winverreports the new build after the upgrade finishes.C:\Windows\SoftwareDistributionhas been recreated and is being written to.- The renamed
SoftwareDistribution.oldfolder can be deleted to reclaim the space, once you are satisfied with the result. - A second machine on the same network completes the same download, which is what tells you a network change worked.
Questions people ask about this
Is the ISO route legitimate, or a workaround?
Legitimate, and for 0x80190001 it is Microsoft’s own published mitigation – download and run the media creation tool. An in-place upgrade from mounted media is the same upgrade by a different delivery route.
What is the difference between 0xC1900130 and 0xC1900131?
Missing versus mismatched. 0xC1900130 says the instance hash was not found, which usually means the state linking the offer to the download has gone. 0xC1900131 says the hash is there and the content does not match it, which points at something altering or truncating the payload.
Do I need to buy anything to fix a failed download?
No. The download is a delivery problem. A licence question only arises if you switch to media for an edition the device is not entitled to.
Should I disable Delivery Optimization permanently?
No. Clear the cache and take peering out temporarily to test, then put it back. Turning it off across an estate moves the whole download load onto your internet link, which usually creates a bigger problem than the one you were solving.
Why does /dynamicupdate disable help?
It stops setup fetching additional content mid-run. When the delivery path is the thing that is failing, removing every trip back to it is the point of running from media at all.
