- Get help with Windows 10 upgrade and installation errors
- General fixes
- 0xC1900101 Errors
- Other Common Errors
- Windows Update troubleshooting
- Why am I offered an older update?
- My device is frozen at scan. Why?
- Feature updates are not being offered while other updates are
- Issues related to HTTP/Proxy
- The update is not applicable to your computer
- Issues related to firewall configuration
- Issues arising from configuration of conflicting policies
- Device cannot access update files
- Updates aren’t downloading from the intranet endpoint (WSUS or Configuration Manager)
- You have a bad setup in the environment
- High bandwidth usage on Windows 10 by Windows Update
Get help with Windows 10 upgrade and installation errors
There are many reasons why you might receive an error message when upgrading or installing Windows 10, but common errors can be fixed with a few steps that you can do on your own. Note: An upgrade takes your device from an older version of Windows, such as Windows 7 or Windows 8.1, to Windows 10.
Before searching for a specific error code, try the tips listed in General fixes. If those don’t fix your upgrade or installation problem, check the table of error codes at the bottom of this article.
General fixes
Here are some things you can try to fix upgrade and installation errors:
Unplug any nonessential hardware devices. These could include headphones, printers, scanners speakers, USB flash drives, and external hard drives.
If you’re using a laptop and it’s plugged in to a docking station, undock it.
It’s a good idea to make sure that all important updates are installed before trying to upgrade Windows. This includes updates to hardware drivers on your device.
For information and to make sure you’re up-to-date, see Windows Update: FAQ.
Use Windows Defender to protect your device during the upgrade—non-Microsoft antivirus software can sometimes cause upgrade problems. As long as you have installation media and all required activation information, you can always reinstall the software after you upgrade.
To remove an antivirus application, go to Control Panel\Programs\Programs and Features. Select the program, and then select Uninstall. Select Yes to confirm.
Outdated software can cause problems with a Windows upgrade, so removing old or nonessential applications can help.
If you plan to reinstall the application later, make sure you have the installation media and all required activation information before removing it.
To uninstall software, go to Control Panel\Programs\Programs and Features. Select the program, and then select Uninstall. Select Yes to confirm.
To upgrade to Windows 10, you need enough space on your hard drive for the installation to take place.
To view how much hard drive space is available on your computer, select the Start button, then in the search box on the taskbar, type File Explorer (known as Windows Explorer in Windows 7).
Then select Computer or This PC and look under Hard Disk Drives or under Devices and drives. If there are multiple drives listed, the system drive is the drive that includes a Microsoft Windows logo above the drive icon. You’ll see the amount of available space under the drive.
If it looks like your drive is running low on space, see Tips to free up drive space on your PC.
0xC1900101 Errors
An error that begins with 0xC1900101 is usually a driver error. If you see any of these error codes, try the following steps first to fix the problem. If these steps don’t work, see Resolve Windows 10 upgrade errors for more detailed technical info.
Make sure that your device has enough space. Your device requires at least 16 GB of free space to upgrade a 32-bit OS, or 20 GB for a 64-bit OS. For more info, see Free up drive space in Windows 10.
Run Windows Update a few times. Download and install any available updates in Windows Update, including software updates, hardware updates, and some third-party drivers. Use the troubleshooter for Windows 10 to fix Windows Update errors.
Check third-party drivers and download any updates. You can find third-party drivers and installation instructions for any hardware you’ve added to your device on the manufacturer’s website.
Unplug extra hardware. Remove all external storage devices and drives, docks, and other hardware you might have plugged into your device that isn’t needed for basic functionality.
Check Device Manager for errors. Select the Start button, then in the search box on the taskbar, type device manager. Choose Device Manager from the results. In the window that pops up, look for any device with a yellow exclamation mark beside it (you may have to select each category to switch to the list of devices). Press and hold (or right-click) the device name and select either Update Driver Software or Uninstall to correct the errors.
Remove third-party security software. Make sure you know how to reinstall your programs and that any necessary product keys are on hand. Windows Defender will help protect your device in the meantime.
Repair hard-drive errors. Select the Start button, then in the search box on the taskbar, type command prompt. Choose Command Prompt from the list of results. In the window that pops up, type chkdsk/f C: and press the Enter key. Repairs automatically start on your hard drive, and you’ll be asked to restart your device.
Note: You must have administrator permissions on your device to do this.
Do a clean restart into Windows. Learn how.
Restore and repair system files. Select the Start button, then in the search box on the taskbar, type command prompt. Choose Command Prompt from the list of results. In the window that pops up, type DISM.exe /Online /Cleanup-image /Restorehealth and press the Enter key. (Learn to repair a Windows image)
Note: You must have administrator permissions on your device to do this.
Other Common Errors
The following table lists the most common upgrade and installation errors and some things you can try to fix them. If you continue having problems upgrading or installing Windows 10, contact Microsoft support.
What it means and how to fix it
This indicates that there was a problem downloading and installing the selected update. Windows Update will try again later and there is nothing you need to do at this time.
This could indicate that an incompatible app installed on your PC is blocking the upgrade process from completing. Check to make sure that any incompatible apps are uninstalled and then try upgrading again.
A cleanup operation from a previous installation attempt is still pending, and a system restart is required to continue the upgrade. Restart the device and run setup again. If restarting device does not resolve the issue, then use the Disk Cleanup utility and clean up the temporary files and the System files. For more information, see Disk cleanup in Windows 10.
A file needed by Windows Update is likely damaged or missing. Try repairing your system files: Select the Start button and type command prompt in the search box on the taskbar. Choose Command Prompt from the list of results. In the window that appears, type DISM.exe /Online /Cleanup-image /Restorehealth and press the Enter key.
This may signify that your PC doesn’t meet the minimum requirements to download or install the upgrade to Windows 10. Learn more about the minimum requirements for Windows 10
This might indicate that a driver or other software on your PC isn’t compatible with the upgrade to Windows 10. For info about how to fix this problem, contact Microsoft support.
This could mean that the upgrade process was interrupted because you accidentally restarted your PC or signed out of your PC. Try upgrading again and make sure your PC is plugged in and stays turned on.
This error might mean that your PC couldn’t connect to the Windows Update servers. If you’re using a VPN connection to connect to a work network, disconnect from the network and turn off the VPN software (if applicable) and try upgrading again.
The error could also mean there isn’t enough free space in the System Reserved partition. You might be able to fix this problem by using third-party software to increase the size of the System Reserved partition.
Error: We couldn’t complete the updates. Undoing changes. Don’t turn off your computer.
Error: Failure configuring Windows Updates. Reverting changes.
These are generic errors that might appear any time a Windows update fails. You’ll need to determine the specific error code to investigate how to best resolve this problem.
You can find the error code for the failed update by viewing your update history. Look for the update that wasn’t installed, note the error code, and then contact Microsoft support.
To view your update history in Windows 8.1:
Open Windows Update by swiping in from the right edge of the screen (or, if you’re using a mouse, pointing to the lower-right corner of the screen and moving the mouse pointer up), select Settings > Change PC settings > Update and recovery > View your update history.
To view your update history in Windows 7:
Select the Start button. In the search box, type Update, and then, in the list of results, Select Windows Update > View update history.
Error: The update isn’t applicable to your computer.
This error might mean that your PC doesn’t have the required updates installed.
Check to make sure that all important updates are installed on your PC before you try upgrading.
This likely indicates that your PC doesn’t have enough space available to install the upgrade.
Free some space on the drive and try again. Get tips for freeing up drive space
The specified disk operation is not supported by the target disk, partition, or volume.
Make sure your machine meets the minimum requirements to install Windows 10.
The system cannot find the file specified.
If you have a disk or disks where you are not installing Windows 10 on, remove those disks.
A driver has caused a problem.
Disable or remove all 3rd party antivirus or antispyware from your system. Disconnect all peripheral devices that are connected to the system, except for the mouse, keyboard and display.
Contact your hardware vendor to obtain updated device drivers.
Windows Setup terminated unexpectedly due to another process running in the background.
When you start Windows by using a normal startup, several applications and services start automatically, and then run in the background. These programs include basic system processes, antivirus software, system utility applications, and other software that has been previously installed. These applications and services can cause interference when you attempt to upgrade to the latest version of Windows 10.
To help you determine whether a background program is interfering with the upgrade, a «clean boot» may be needed. See How to perform a clean boot in Windows.
Windows Setup terminated unexpectedly due to another process running in the background.
Uninstall any antivirus or antispyware software and update again.
Windows Update troubleshooting
If you run into problems when using Windows Update, start with the following steps:
Run the built-in Windows Update troubleshooter to fix common issues. Navigate to Settings > Update & Security > Troubleshoot > Windows Update.
Install the most recent Servicing Stack Update (SSU) that matches your version of Windows from the Microsoft Update Catalog. See Servicing stack updates for more details on servicing stack updates.
Make sure that you install the latest Windows updates, cumulative updates, and rollup updates. To verify the update status, refer to the appropriate update history for your system:
Advanced users can also refer to the log generated by Windows Update for further investigation.
You might encounter the following scenarios when using Windows Update.
Why am I offered an older update?
The update that is offered to a device depends on several factors. The following are some of the most common attributes:
- OS Build
- OS Branch
- OS Locale
- OS Architecture
- Device update management configuration
If the update you’re offered isn’t the most current available, it might be because your device is being managed by a WSUS server, and you’re being offered the updates available on that server. It’s also possible, if your device is part of a deployment group, that your admin is intentionally slowing the rollout of updates. Since the deployment is slow and measured to begin with, all devices will not receive the update on the same day.
My device is frozen at scan. Why?
The Settings UI communicates with the Update Orchestrator service that in turn communicates with to Windows Update service. If these services stop unexpectedly, then you might see this behavior. In such cases, follow these steps:
Close the Settings app and reopen it.
Start Services.msc and check if the following services are running:
- Update State Orchestrator
- Windows Update
Feature updates are not being offered while other updates are
Devices running Windows 10, version 1709 through Windows 10, version 1803 that are configured to update from Windows Update (including Windows Update for Business) are able to install servicing and definition updates but are never offered feature updates.
Checking the WindowsUpdate.log reveals the following error:
The 0x80070426 error code translates to:
Microsoft Account Sign In Assistant (MSA or wlidsvc) is the service in question. The DCAT Flighting service (ServiceId: 855E8A7C-ECB4-4CA3-B045-1DFA50104289) relies on MSA to get the global device ID for the device. Without the MSA service running, the global device ID won’t be generated and sent by the client and the search for feature updates never completes successfully.
To resolve this issue, reset the MSA service to the default StartType of «manual.»
Issues related to HTTP/Proxy
Windows Update uses WinHttp with Partial Range requests (RFC 7233) to download updates and applications from Windows Update servers or on-premises WSUS servers. Therefore proxy servers on the network must support HTTP RANGE requests. If a proxy was configured in Internet Explorer (User level) but not in WinHTTP (System level), connections to Windows Update will fail.
To fix this issue, configure a proxy in WinHTTP by using the following netsh command:
You can also import the proxy settings from Internet Explorer by using the following command: netsh winhttp import proxy source=ie
If downloads through a proxy server fail with a 0x80d05001 DO_E_HTTP_BLOCKSIZE_MISMATCH error, or if you notice high CPU usage while updates are downloading, check the proxy configuration to permit HTTP RANGE requests to run.
You might choose to apply a rule to permit HTTP RANGE requests for the following URLs:
*.download.windowsupdate.com
*.dl.delivery.mp.microsoft.com *.delivery.mp.microsoft.com
If you can’t allow RANGE requests, you’ll be downloading more content than needed in updates (as delta patching will not work).
The update is not applicable to your computer
The most common reasons for this error are described in the following table:
Cause | Explanation | Resolution |
---|---|---|
Update is superseded | As updates for a component are released, the updated component will supersede an older component that is already on the system. When this occurs, the previous update is marked as superseded. If the update that you’re trying to install already has a newer version of the payload on your system, you might receive this error message. | Check that the package that you are installing contains newer versions of the binaries. Or, check that the package is superseded by another new package. |
Update is already installed | If the update that you’re trying to install was previously installed, for example, by another update that carried the same payload, you may encounter this error message. | Verify that the package that you are trying to install was not previously installed. |
Wrong update for architecture | Updates are published by CPU architecture. If the update that you’re trying to install does not match the architecture for your CPU, you may encounter this error message. | Verify that the package that you’re trying to install matches the Windows version that you are using. The Windows version information can be found in the «Applies To» section of the article for each update. For example, Windows Server 2012-only updates cannot be installed on Windows Server 2012 R2-based computers. Also, verify that the package that you are installing matches the processor architecture of the Windows version that you are using. For example, an x86-based update cannot be installed on x64-based installations of Windows. |
Missing prerequisite update | Some updates require a prerequisite update before they can be applied to a system. If you are missing a prerequisite update, you may encounter this error message. For example, KB 2919355 must be installed on Windows 8.1 and Windows Server 2012 R2 computers before many of the updates that were released after April 2014 can be installed. | Check the related articles about the package in the Microsoft Knowledge Base (KB) to make sure that you have the prerequisite updates installed. For example, if you encounter the error message on Windows 8.1 or Windows Server 2012 R2, you may have to install the April 2014 update 2919355 as a prerequisite and one or more pre-requisite servicing updates (KB 2919442 and KB 3173424). To determine if these prerequisite updates are installed, run the following PowerShell command: get-hotfix KB3173424,KB2919355, KB2919442 . If the updates are installed, the command will return the installed date in the InstalledOn section of the output. |
Issues related to firewall configuration
Error that you might see in Windows Update logs:
Go to Services.msc and ensure that Windows Firewall Service is enabled. Stopping the service associated with Windows Firewall with Advanced Security is not supported by Microsoft. For more information, see I need to disable Windows Firewall.
Issues arising from configuration of conflicting policies
Windows Update provides a wide range configuration policy to control the behavior of the Windows Update service in a managed environment. While these policies let you configure the settings at a granular level, misconfiguration or setting conflicting policies may lead to unexpected behaviors.
Device cannot access update files
Ensure that devices can reach necessary Windows Update endpoints through the firewall. For example, for Windows 10, version 2004, the following protocols must be able to reach these respective endpoints:
Protocol | Endpoint URL |
---|---|
TLS 1.2 | *.prod.do.dsp.mp.microsoft.com |
HTTP | emdl.ws.microsoft.com |
HTTP | *.dl.delivery.mp.microsoft.com |
HTTP | *.windowsupdate.com |
HTTPS | *.delivery.mp.microsoft.com |
TLS 1.2 | *.update.microsoft.com |
TLS 1.2 | tsfe.trafficshaping.dsp.mp.microsoft.com |
Be sure not to use HTTPS for those endpoints that specify HTTP, and vice versa. The connection will fail.
The specific endpoints can vary between Windows 10 versions. See, for example, Windows 10 2004 Enterprise connection endpoints. Similar articles for other Windows 10 versions are available in the table of contents nearby.
Updates aren’t downloading from the intranet endpoint (WSUS or Configuration Manager)
Windows 10 devices can receive updates from a variety of sources, including Windows Update online, a Windows Server Update Services server, and others. To determine the source of Windows Updates currently being used on a device, follow these steps:
- Start Windows PowerShell as an administrator.
- Run $MUSM = New-Object -ComObject «Microsoft.Update.ServiceManager».
- Run $MUSM.Services.
Check the output for the Name and OffersWindowsUPdates parameters, which you can interpret according to this table.
Output | Meaning |
---|---|
— Name: Microsoft Update -OffersWindowsUpdates: True | — The update source is Microsoft Update, which means that updates for other Microsoft products besides the operating system could also be delivered. — Indicates that the client is configured to receive updates for all Microsoft Products (Office, etc.) |
— Name: DCat Flighting Prod — OffersWindowsUpdates: True | — Starting with Windows 10 1709, feature updates are always delivered through the DCAT service. — Indicates that the client is configured to receive feature updates from Windows Update. |
— Name: Windows Store (DCat Prod) — OffersWindowsUpdates: False | -The update source is Insider Updates for Store Apps. — Indicates that the client will not receive or is not configured to receive these updates. |
— Name: Windows Server Update Service — OffersWindowsUpdates: True | — The source is a Windows Server Updates Services server. — The client is configured to receive updates from WSUS. |
— Name: Windows Update — OffersWindowsUpdates: True | — The source is Windows Update. — The client is configured to receive updates from Windows Update Online. |
You have a bad setup in the environment
In this example, per the Group Policy set through registry, the system is configured to use WSUS to download updates (note the second line):
From Windows Update logs:
In the above log snippet, we see that the Criteria = «IsHidden = 0 AND DeploymentAction=*» . «*» means there is nothing specified from the server. So, the scan happens but there is no direction to download or install to the agent. So it just scans the update and provides the results.
As shown in the following logs, automatic update runs the scan and finds no update approved for it. So it reports there are no updates to install or download. This is due to an incorrect configuration. The WSUS side should approve the updates for Windows Update so that it fetches the updates and installs them at the specified time according to the policy. Since this scenario doesn’t include Configuration Manager, there’s no way to install unapproved updates. You’re expecting the operational insight agent to do the scan and automatically trigger the download and installation but that won’t happen with this configuration.
High bandwidth usage on Windows 10 by Windows Update
Users might see that Windows 10 is consuming all the bandwidth in the different offices under the system context. This behavior is by design. Components that might consume bandwidth expand beyond Windows Update components.
The following group policies can help mitigate this situation:
Other components that connect to the internet: