Your shopping cart is empty.
Microsoft Upgrade Errors
Microsoft error codes for upgrading
Error code | Cause | Mitigation |
0xC1800118 | WSUS has downloaded content that it cannot use due to a missing decryption key. | See Steps to resolve error 0xC1800118 for information. |
0xC1900200 | Setup.exe has detected that the machine does not meet the minimum system requirements. | Ensure the system you are trying to upgrade meets the minimum system requirements. See Windows 10 specifications for information. |
0x80090011 | A device driver error occurred during user data migration. | Contact your hardware vendor and get all the device drivers updated. It is recommended to have an active internet connection during upgrade process. Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process. |
0xC7700112 | Failure to complete writing data to the system drive, possibly due to write access failure on the hard disk. | This issue is resolved in the latest version of Upgrade Assistant. Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process. |
0x80190001 | An unexpected error was encountered while attempting to download files required for upgrade. | To resolve this issue, download and run the media creation tool. See Download windows 10. |
0x80246007 | The update was not downloaded successfully. | Attempt other methods of upgrading the operating system. Download and run the media creation tool. See Download windows 10. Attempt to upgrade using .ISO or USB. Note Windows 10 Enterprise isn’t available in the media creation tool. For more information, go to the Volume Licensing Service Center. |
0x80244018 | Your machine is connected through a proxy server. | Make sure Automatically Detect Settings is selected in internet options. (Control Panel > Internet Options > Connections > LAN Settings). |
0xC1900201 | The system did not pass the minimum requirements to install the update. | Contact the hardware vendor to get the latest updates. |
0x80240017 | The upgrade is unavailable for this edition of Windows. | Administrative policies enforced by your organization might be preventing the upgrade. Contact your IT administrator. |
0x80070020 | The existing process cannot access the file because it is being used by another process. | Use the MSCONFIG tool to perform a clean boot on the machine and then try to perform the update again. For more information, see How to perform a clean boot in Windows. |
0x80070522 | The user doesn’t have required privilege or credentials to upgrade. | Ensure that you have signed in as a local administrator or have local administrator privileges. |
0xC1900107 | A cleanup operation from a previous installation attempt is still pending and a system reboot is required in order to continue the upgrade. | Restart the device and run setup again. If restarting the device does not resolve the issue, then use the Disk Cleanup utility and clean up the temporary files as well as the System files. For more information, see Disk cleanup in Windows 10. |
0xC1900209 | The user has chosen to cancel because the system does not pass the compatibility scan to install the update. Setup.exe will report this error when it can upgrade the machine with user data but cannot migrate installed applications. | Incompatible software is blocking the upgrade process. Uninstall the application and try the upgrade again. See Windows 10 Pre-Upgrade Validation using SETUP.EXE for more information. You can also download the Windows Assessment and Deployment Kit (ADK) for Windows 10 and install Application Compatibility Tools. |
0x8007002 | This error is specific to upgrades using System Center 2012 Configuration Manager R2 SP1 CU3 (5.00.8238.1403) | Analyze the SMSTS.log and verify that the upgrade is failing on "Apply Operating system" Phase: Error 80072efe DownloadFileWithRanges() failed. 80072efe. ApplyOperatingSystem (0x0760) The error 80072efe means that the connection with the server was terminated abnormally. To resolve this issue, try the OS Deployment test on a client in same VLAN as the Configuration Manager server. Check the network configuration for random client-server connection issues happening on the remote VLAN. |
0x80240FFF | Occurs when update synchronization fails. It can occur when you are using Windows Server Update Services on its own or when it is integrated with Microsoft Endpoint Configuration Manager. If you enable update synchronization before you install hotfix 3095113, WSUS doesn't recognize the Upgrades classification and instead treats the upgrade like a regular update. | You can prevent this by installing hotfix 3095113 before you enable update synchronization. However, if you have already run into this problem, do the following:
|
0x8007007E | Occurs when update synchronization fails because you do not have hotfix 3095113 installed before you enable update synchronization. Specifically, the CopyToCache operation fails on clients that have already downloaded the upgrade because Windows Server Update Services has bad metadata related to the upgrade. It can occur when you are using standalone Windows Server Update Services or when WSUS is integrated with Microsoft Endpoint Configuration Manager. | Use the following steps to repair Windows Server Update Services. You must run these steps on each WSUS server that synched metadata before you installed the hotfix.
|
Other error codes
Error Codes | Cause | Mitigation |
0x80070003- 0x20007 | This is a failure during SafeOS phase driver installation. | Verify device drivers on the computer, and analyze log files to determine the problem driver. |
0x8007025D - 0x2000C | This error occurs if the ISO file's metadata is corrupt. | "Re-download the ISO/Media and re-attempt the upgrade.
Alternatively, re-create installation media the Media Creation Tool. |
0x80070490 - 0x20007 | An incompatible device driver is present. | Verify device drivers on the computer, and analyze log files to determine the problem driver. |
0xC1900101 - 0x2000c | An unspecified error occurred in the SafeOS phase during WIM apply. This can be caused by an outdated driver or disk corruption. | Run checkdisk to repair the file system. For more information, see the quick fixes section in this guide. Update drivers on the computer, and select "Download and install updates (recommended)" during the upgrade process. Disconnect devices other than the mouse, keyboard and display. |
0xC1900200 - 0x20008 | The computer doesn’t meet the minimum requirements to download or upgrade to Windows 10.
See Windows 10 Specifications and verify the computer meets minimum requirements. Review logs for compatibility information. |
|
0x80070004 - 0x3000D | This is a problem with data migration during the first boot phase. There are multiple possible causes. | Analyze log files to determine the issue. |
0xC1900101 - 0x4001E | Installation failed in the SECOND_BOOT phase with an error during PRE_OOBE operation. | This is a generic error that occurs during the OOBE phase of setup. See the 0xC1900101 section of this guide and review general troubleshooting procedures described in that section. |
0x80070005 - 0x4000D | The installation failed in the SECOND_BOOT phase with an error in during MIGRATE_DATA operation. This error indicates that access was denied while attempting to migrate data. | Analyze log files to determine the data point that is reporting access denied. |
0x80070004 - 0x50012 | Windows Setup failed to open a file. | Analyze log files to determine the data point that is reporting access problems. |
0xC190020e 0x80070070 - 0x50011 0x80070070 - 0x50012 0x80070070 - 0x60000 |
These errors indicate the computer does not have enough free space available to install the upgrade. | To upgrade a computer to Windows 10, it requires 16 GB of free hard drive space for a 32-bit OS, and 20 GB for a 64-bit OS. If there is not enough space, attempt to free up drive space before proceeding with the upgrade.
Note If your device allows it, you can use an external USB drive for the upgrade process. Windows setup will back up the previous version of Windows to a USB external drive. The external drive must be at least 8GB (16GB is recommended). The external drive should be formatted using NTFS. Drives that are formatted in FAT32 may run into errors due to FAT32 file size limitations. USB drives are preferred over SD cards because drivers for SD cards are not migrated if the device does not support Connected Standby. |