Resolve Windows 10 upgrade errors: Quick fixes, Upgrade error codes, Resolution procedures

The Windows 10 upgrade process

The Windows Setup application is used to upgrade a computer to Windows 10, or to perform a clean installation. Windows Setup starts and restarts the computer, gathers information, copies files, and creates or adjusts configuration settings. When performing an operating system upgrade, Windows Setup uses the following phases:

1. Downlevel phase: The downlevel phase is run within the previous operating system. Installation components are gathered.
2. Safe OS phase: A recovery partition is configured and updates are installed. An OS rollback is prepared if needed. Example error codes: 0x2000C, 0x20017
3. First boot phase: Initial settings are applied. Example error codes: 0x30018, 0x3000D
4. Second boot phase: Final settings are applied. This is also called the OOBE boot phase. Example error: 0x4000D, 0x40017
5. Uninstall phase: This phase occurs if upgrade is unsuccessful.
Example error: 0x50000


Quick fixes

The following steps can resolve many Windows upgrade problems.
1. Remove nonessential external hardware, such as docks and USB devices.
2. Check all hard drives for errors and attempt repairs. To automatically repair hard drives, open an elevated command prompt, switch to the drive you wish to repair, and type the following command. You will be required to reboot the computer if the hard drive being repaired is also the system drive. chkdsk /F
3. Attept to restore and repair system files by typing the following commands at an elevated command prompt. It may take several minutes for the command operations to be completed. For more information, see Repair a Windows Image. DISM.exe /Online /Cleanup-image /Restorehealth, sfc /scannow
4. Update Windows so that all available recommended updates are installed, and ensure the computer is rebooted if this is necessary to complete installation of an update.
5. Uninstall non-Microsoft antivirus software. Use Windows Defender for protection during the upgrade; Verify compatibility information and re-install antivirus applications after the upgrade.
6. Uninstall all nonessential software.
7. Update firmware and drivers.
8. Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process.
9. Verify at least 16 GB of free space is available to upgrade a 32-bit OS, or 20 GB for a 64-bit OS.


Upgrade error codes

If the upgrade process is not successful, Windows Setup will return two codes:
A result code: The result code corresponds to a specific Win32 error.
An extend code: The extend code contains information about both the phase in which an error occurred, and the operation that was being performed when the error occurred.
For example, a result code of 0xC1900101 with an extend code of 0x4000D will be returned as: 0xC1900101 - 0x4000D.


Resolution procedures

0xC1900101 - 0x20004
Windows Setup encountered an error during the SAFE_OS with the INSTALL_RECOVERY_ENVIRONMENT operation. This is generally caused by out-of-date drivers.
Mitigation
Uninstall antivirus applications.
Remove all unused SATA devices.
Remove all unused devices and drivers.
Update drivers and BIOS.

0xC1900101 - 0x2000c
Windows Setup encountered an unspecified error during Wim apply in the WinPE phase. This is generally caused by out-of-date drivers.
Mitigation
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.
Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process.

0xC1900101 - 0x20017
A driver has caused an illegal operation. Windows was not able to migrate the driver, resulting in a rollback of the operating system. This is a safeOS boot failure, typically caused by drivers or non-Microsoft disk encryption software.
Mitigation
Ensure that all that drivers are updated.
Open the Setuperr.log and Setupact.log files in the %windir%\Panther directory, and then locate the problem drivers.
For more information, see Understanding Failures and Log Files.
Update or uninstall the problem drivers.

0xC1900101 - 0x30018
A device driver has stopped responding to setup.exe during the upgrade process.
Mitigation
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.
Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process.

0xC1900101 - 0x3000D
Installation failed during the FIRST_BOOT phase while attempting the MIGRATE_DATA operation. This can occur due to a problem with a display driver.
Mitigation
Disconnect all peripheral devices that are connected to the system, except for the mouse, keyboard and display.
Update or uninstall the display driver.

0xC1900101 - 0x4000D
A rollback occurred due to a driver configuration issue. Installation failed during the second boot phase while attempting the MIGRATE_DATA operation. This can occur due to incompatible drivers.
Mitigation
Check supplemental rollback logs for a setupmem.dmp file, or event logs for any unexpected reboots or errors.
Review the rollback log and determine the stop code.
The rollback log is located in the C:$Windows.~BT\Sources\Panther folder. An example analysis is shown below. This example is not representative of all cases:
Info SP Crash 0x0000007E detected
Info SP Module name :
Info SP Bugcheck parameter 1 : 0xFFFFFFFFC0000005
Info SP Bugcheck parameter 2 : 0xFFFFF8015BC0036A
Info SP Bugcheck parameter 3 : 0xFFFFD000E5D23728
Info SP Bugcheck parameter 4 : 0xFFFFD000E5D22F40
Info SP Cannot recover the system.
Info SP Rollback: Showing splash window with restoring text: Restoring your previous version of Windows.
Typically there is a a dump file for the crash to analyze. If you are not equipped to debug the dump, then attempt the following basic troubleshooting procedures:
1. Make sure you have enough disk space.
2. If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.
3. Try changing video adapters.
4. Check with your hardware vendor for any BIOS updates.
5. Disable BIOS memory options such as caching or shadowing.

0xC1900101 - 0x40017
Windows 10 upgrade failed after the second reboot. This is usually caused by a faulty driver. For example: antivirus filter drivers or encryption drivers.
Mitigation
Clean boot into Windows, and then attempt the upgrade to Windows 10.
For more information, see How to perform a clean boot in Windows.
Ensure you select the option to "Download and install updates (recommended)."

800040005 - 0x20007
An unspecified error occurred with a driver during the SafeOS phase.
Mitigation
This error has more than one possible cause. Attempt quick fixes, and if not successful, analyze log files in order to determine the problem and solution.

800704B8 - 0x3001A
An extended error has occurred during the first boot phase.
Mitigation
Disable or uninstall non-Microsoft antivirus applications, disconnect all unnecessary devices, and perform a clean boot.

8007042B - 0x4000D
The installation failed during the second boot phase while attempting the MIGRATE_DATA operation. This issue can occur due to file system, application, or driver issues.
Mitigation
Analyze log files in order to determine the file, application, or driver that is not able to be migrated. Disconnect, update, remove, or replace the device or object.

8007001F - 0x3000D
The installation failed in the FIRST_BOOT phase with an error during MIGRATE_DATA operation.
Mitigation
Analyze log files in order to determine the files or registry entires that are blocking data migration. This error can be due to a problem with user profiles. It can occur due to corrupt registry entries under HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList or invalid files in the \Users directory. Note: If a previous upgrade did not complete, invalid profiles might exist in the Windows.old\Users directory. To repair this error, ensure that deleted accounts are not still present in the Windows registry and that files under the \Users directory are valid. Delete the invalid files or user profiles that are causing this error. The specific files and profiles that are causing the error will be recorded in the Windows setup log files.

8007001F - 0x4000D
General failure, a device attached to the system is not functioning.
Mitigation
Analyze log files in order to determine the device that is not functioning properly. Disconnect, update, or replace the device.

8007042B - 0x4001E
The installation failed during the second boot phase while attempting the PRE_OOBE operation.
Mitigation
This error has more than one possible cause. Attempt quick fixes, and if not successful, analyze log files in order to determine the problem and solution.

0xC1800118
WSUS has downloaded content that it cannot use due to a missing decryption key.
Mitigation
See Steps to resolve error 0xC1800118 for information (https://blogs.technet.microsoft.com/wsus/2016/09/21/resolving-error-0xc1800118/).

0xC1900200
Setup.exe has detected that the machine does not meet the minimum system requirements.
Mitigation
Ensure the system you are trying to upgrade meets the minimum system requirements. See Windows 10 specifications for information (https://www.microsoft.com/en-us/windows/windows-10-specifications).

0x80090011
A device driver error occurred during user data migration.
Mitigation: 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.
Mitigation: 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.
Mitigation: To resolve this issue, download and run the media creation tool. See Download windows 10 (https://www.microsoft.com/en-us/software-download/windows10).

0x80246007
The update was not downloaded successfully.
Mitigation: Attempt other methods of upgrading the operating system. Attempt to upgrade using .ISO or USB. Note: Windows 10 Enterprise isn’t available in the media creation tool.

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 (https://support.microsoft.com/en-us/kb/929135).

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.
Reboot the device and run setup again. If restarting device does not resolve the issue, then use the Disk Cleanup utility and cleanup the temporary as well as the System files. For more information, see Disk cleanup in Windows 10 (https://support.microsoft.com/en-us/instantanswers/8fef4121-711b-4be1-996f-99e02c7301c2/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 (https://blogs.technet.microsoft.com/mniehaus/2015/08/23/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 (http://go.microsoft.com/fwlink/p/?LinkId=526740) and install Application Compatibility Tools.

0x8007002
This error is specific to upgrades using System Center Configuration Manager 2012 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 System Center 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 (http://blogs.technet.com/b/wsus/archive/2015/12/04/important-update-for-wsus-4-0-kb-3095113.aspx) before you enable update synchronization. However, if you have already run into this problem, do the following:
1. Disable the Upgrades classification.
2. Install hotfix 3095113.
3. Delete previously synched updates.
4. Enable the Upgrades classification.
5. Perform a full synch.
For detailed information on how to run these steps check out How to delete upgrades in WSUS (http://blogs.technet.com/b/wsus/archive/2016/01/30/quot-help-i-synched-upgrades-too-soon-quot.aspx).

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 downlaoded 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 System Center Configuration Manager.
Use the following steps to repair Windows Server Update Services. You must run these steps on each WSUS server that synched metadate before you installed the hotfix:
1. Stop the Windows Update service. Sign in as a user with administrative privileges, and then do the following:
a) Open Administrative Tools from the Control Panel.
b) Double-click Services.
c) Find the Windows Update service, right-click it, and then click Stop. If prompted, enter your credentials.
2. Delete all files and folders under c:\Windows\SoftwareDistribution\DataStore.
3. Restart the Windows Update service.

0x80070003- 0x20007
This is a failure during SafeOS phase driver installation.
Verify device drivers (https://msdn.microsoft.com/windows/hardware/drivers/install/troubleshooting-device-and-driver-installations) on the computer, and analyze log (https://docs.microsoft.com/pt-pt/windows/deployment/upgrade/resolve-windows-10-upgrade-errors#analyze-log-files) 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 (https://www.microsoft.com/en-us/software-download/windows10).

0x80070490 - 0x20007
An incompatible device driver is present.
Verify device drivers (https://msdn.microsoft.com/windows/hardware/drivers/install/troubleshooting-device-and-driver-installations) on the computer, and analyze log (https://docs.microsoft.com/pt-pt/windows/deployment/upgrade/resolve-windows-10-upgrade-errors#analyze-log-files) 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 (https://docs.microsoft.com/pt-pt/windows/deployment/upgrade/resolve-windows-10-upgrade-errors#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 (https://www.microsoft.com/en-us/windows/windows-10-specifications) and verify the computer meets minimum requirements. Review logs for compatibility information (https://blogs.technet.microsoft.com/askcore/2016/01/21/using-the-windows-10-compatibility-reports-to-understand-upgrade-issues/).

0x80070004 - 0x3000D
This is a problem with data migration during the first boot phase. There are multiple possible causes.
Analyze log files (https://docs.microsoft.com/pt-pt/windows/deployment/upgrade/resolve-windows-10-upgrade-errors#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 (https://docs.microsoft.com/pt-pt/windows/deployment/upgrade/resolve-windows-10-upgrade-errors#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 (https://docs.microsoft.com/pt-pt/windows/deployment/upgrade/resolve-windows-10-upgrade-errors#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 (https://support.microsoft.com/en-us/help/17421/windows-free-up-drive-space) before proceeding with the upgrade. 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.

Source: https://docs.microsoft.com/