Resolve Windows 10 upgrade errors : Technical information for IT Pros
- Windows 10
Important: This topic contains technical instructions for IT administrators. If you are not an IT administrator, see Get help with Windows 10 upgrade and installation errors for more information.
In this topic
This topic contains a brief introduction to Windows 10 installation processes, and provides resolution procedures that IT administrators can use to resolve issues with Windows 10 upgrade. The following sections and procedures are provided in this guide:
- The Windows 10 upgrade process: An explanation of phases used during the upgrade process.
- Quick fixes: Steps you can take to eliminate many Windows upgrade errors.
- Upgrade error codes: The components of an error code are explained.
- Log files: A list and description of log files useful for troubleshooting.
- Resolution procedures: Causes and mitigation procedures associated with specific error codes.
- 0xC1900101: Information about the 0xC1900101 result code.
- 0x800xxxxx: Information about result codes that start with 0x800.
- Other result codes: Additional causes and mitigation procedures are provided for some result codes.
- Other error codes: Additional causes and mitigation procedures are provided for some error codes.
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:
- Downlevel phase: The downlevel phase is run within the previous operating system. Installation components are gathered.
- Safe OS phase: A recovery partition is configured and updates are installed. An OS rollback is prepared if needed.
- Example error codes: 0x2000C, 0x20017
- First boot phase: Initial settings are applied.
- Example error codes: 0x30018, 0x3000D
- Second boot phase: Final settings are applied. This is also called the OOBE boot phase.
- Example error: 0x4000D, 0x40017
- Uninstall phase: This phase occurs if upgrade is unsuccessful.
- Example error: 0x50000
Figure 1: Phases of a successful Windows 10 upgrade (uninstall is not shown):
DU = Driver/device updates.
OOBE = Out of box experience.
WIM = Windows image (Microsoft)
The following steps can resolve many Windows upgrade problems.
- Remove nonessential external hardware, such as docks and USB devices.
- 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
- 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
- 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.
- Uninstall non-Microsoft antivirus software.
- Use Windows Defender for protection during the upgrade.
- Verify compatibility information and re-install antivirus applications after the upgrade.
- Uninstall all nonessential software.
- Update firmware and drivers.
- Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process.
- 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.
Note: If only a result code is returned, this can be because a tool is being used that was not able to capture the extend code. For example, if you are using the Windows 10 Upgrade Assistant then only a result code might be returned.
A result code of 0xC1900101 is generic and indicates that a rollback occurred. In most cases, the cause is a driver compatibility issue.
To troubleshoot a failed upgrade that has returned a result code of 0xC1900101, analyze the extend code to determine the Windows Setup phase, and see the Resolution procedures section later in this topic.
Result codes can be matched to the type of error encountered. To match a result code to an error:
- Identify the error code type, either Win32 or NTSTATUS, using the first hexidecimal digit:
8 = Win32 error code (ex: 0x80070070)
C = NTSTATUS value (ex: 0xC1900107)
- Write down the last 4 digits of the error code (ex: 0x80070070 = 0070). These digits correspond to the last 16 bits of the HRESULT or the NTSTATUS structure.
- Based on the type of error code determined in the first step, match the 4 digits derived from the second step to either a Win32 error code, or an NTSTATUS value.
- 0x80070070 = Win32 = 0070 = 0x00000070 = ERROR_DISK_FULL
- 0xC1900107 = NTSTATUS = 0107 = 0x00000107 = STATUS_SOME_NOT_MAPPED
Some result codes are self-explanatory, whereas others are more generic and require further analysis. In the examples shown above, ERROR_DISK_FULL indicates that the hard drive is full and additional room is needed to complete Windows upgrade. The message STATUS_SOME_NOT_MAPPED is more ambiguous, and means that an action is pending. In this case, the action pending is often the cleanup operation from a previous installation attempt, which can be resolved with a system reboot.
Important: Extend codes reflect the current Windows 10 upgrade process, and might change in future releases of Windows 10. The codes discussed in this section apply to Windows 10 version 1607, also known as the Anniversary Update.
Extend codes can be matched to the phase and operation when an error occurred. To match an extend code to the phase and operation:
- Use the first digit to identify the phase (ex: 0x4000D = 4).
- Use the last two digits to identify the operation (ex: 0x4000D = 0D).
- Match the phase and operation to values in the tables provided below.
The following tables provide the corresponding phase and operation for values of an extend code:
|Extend code: phase|
|Extend code: operation|
For example: An extend code of 0x4000D, represents a problem during phase 4 (0x4) with data migration (000D).
Several log files are created during each phase of the upgrade process. These log files are essential for troubleshooting upgrade problems. By default, the folders that contain these log files are hidden on the upgrade target computer. To view the log files, configure Windows Explorer to view hidden items, or use a tool to automatically gather these logs. The most useful log is setupact.log. The log files are located in a different folder depending on the Windows Setup phase. Recall that you can determine the phase from the extend code.
The following table describes some log files and how to use them for troubleshooting purposes:
|Log file||Phase: Location||Description||When to use|
|Contains information about setup actions during the downlevel phase.||All down-level failures and starting point for rollback investigations.
This is the most important log for diagnosing setup issues.
|Contains information about actions during the OOBE phase.||Investigating rollbacks that failed during OOBE phase and operations – 0x4001C, 0x4001D, 0x4001E, 0x4001F.|
|Contains information about actions during rollback.||Investigating generic rollbacks - 0xC1900101.|
|Pre-initialization (prior to downlevel):|
|Contains information about initializing setup.||If setup fails to launch.|
|Post-upgrade (after OOBE):|
|Contains information about setup actions during the installation.||Investigate post-upgrade related issues.|
|setuperr.log||Same as setupact.log||Contains information about setup errors during the installation.||Review all errors encountered during the installation phase.|
|miglog.xml||Post-upgrade (after OOBE):|
|Contains information about what was migrated during the installation.||Identify post upgrade data migration issues.|
|Contains information communication between setup.exe and Windows Update.||Use during WSUS and WU down-level failures or for 0xC1900107.|
|Supplemental rollback logs:
Event logs (*.evtx)
|$Windows.~BT\Sources\Rollback||Additional logs collected during rollback.||
Setupmem.dmp: If OS bugchecks during upgrade, setup will attempt to extract a mini-dump.
Setupapi: Device install issues - 0x30018
Event logs: Generic rollbacks (0xC1900101) or unexpected reboots.
Log entry structure
A setupact.log or setuperr.log entry includes the following elements:
- The date and time - 2016-09-08 09:20:05.
- The log level - Info, Warning, Error, Fatal Error.
- The logging component - CONX, MOUPG, PANTHR, SP, IBSLIB, MIG, DISM, CSI, CBS.
- The logging components SP (setup platform), MIG (migration engine), and CONX (compatibility information) are particularly useful for troubleshooting Windows Setup errors.
- The message - Operation completed successfully.
See the following example:
|2016-09-08 09:23:50,||Warning||MIG||Could not replace object C:\Users\name\Cookies. Target Object cannot be removed.|
Analyze log files
To analyze Windows Setup log files:
- Determine the Windows Setup error code. This code should be returned by Windows Setup if it is not successful with the upgrade process.
- Based on the extend code portion of the error code, determine the type and location of a log files to investigate.
- Open the log file in a text editor, such as notepad.
- Using the result code portion of the Windows Setup error code, search for the result code in the file and find the last occurrence of the code. Alternatively search for the "abort" and abandoning" text strings described in step 7 below.
- To find the last occurrence of the result code:
- Scroll to the bottom of the file and click after the last character.
- Click Edit.
- Click Find.
- Type the result code.
- Under Direction select Up.
- Click Find Next.
- Shell application requested abort
- Abandoning apply due to error for object
For example, assume that the error code for an error is 0x8007042B - 0x2000D. Searching for "8007042B" reveals the following content from the setuperr.log file:
Some lines in the text below are shortened to enhance readability. The date and time at the start of each line (ex: 2016-10-05 15:27:08) is shortened to minutes and seconds, and the certificate file name which is a long text string is shortened to just "CN."
27:08, Error SP Error READ, 0x00000570 while gathering/applying object: File, C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 [CN]. Will return 0[gle=0x00000570] 27:08, Error MIG Error 1392 while gathering object C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 [CN]. Shell application requested abort![gle=0x00000570] 27:08, Error Gather failed. Last error: 0x00000000 27:08, Error SP SPDoFrameworkGather: Gather operation failed. Error: 0x0000002C 27:09, Error SP CMigrateFramework: Gather framework failed. Status: 44 27:09, Error SP Operation failed: Migrate framework (Full). Error: 0x8007042B[gle=0x000000b7] 27:09, Error SP Operation execution failed: 13. hr = 0x8007042B[gle=0x000000b7] 27:09, Error SP CSetupPlatformPrivate::Execute: Execution of operations queue failed, abandoning. Error: 0x8007042B[gle=0x000000b7]
The first line indicates there was an error 0x00000570 with the file C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 [CN] (shown below):
27:08, Error SP Error READ, 0x00000570 while gathering/applying object: File, C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 [CN]. Will return 0[gle=0x00000570]
The error 0x00000570 is a Win32 error code corresponding to: ERROR_FILE_CORRUPT: The file or directory is corrupted and unreadable.
Therefore, Windows Setup failed because it was not able to migrate the corrupt file C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18[CN]. This file is a local system certificate and can be safely deleted. Searching the setupact.log file for additional details, the phrase "Shell application requested abort" is found in a location with the same timestamp as the lines in setuperr.log. This confirms our suspicion that this file is the cause of the upgrade failure:
27:00, Info Gather started at 10/5/2016 23:27:00 27:00, Info [0x080489] MIG Setting system object filter context (System) 27:00, Info [0x0803e5] MIG Not unmapping HKCU\Software\Classes; it is not mapped 27:00, Info [0x0803e5] MIG Not unmapping HKCU; it is not mapped 27:00, Info SP ExecuteProgress: Elapsed events:1 of 4, Percent: 12 27:00, Info [0x0802c6] MIG Processing GATHER for migration unit:
\UpgradeFramework (CMXEAgent) 27:08, Error SP Error READ, 0x00000570 while gathering/applying object: File, C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 [CN]. Will return 0[gle=0x00000570] 27:08, Error MIG Error 1392 while gathering object C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 [CN]. Shell application requested abort![gle=0x00000570] 27:08, Info SP ExecuteProgress: Elapsed events:2 of 4, Percent: 25 27:08, Info SP ExecuteProgress: Elapsed events:3 of 4, Percent: 37 27:08, Info [0x080489] MIG Setting system object filter context (System) 27:08, Info [0x0803e5] MIG Not unmapping HKCU\Software\Classes; it is not mapped 27:08, Info [0x0803e5] MIG Not unmapping HKCU; it is not mapped 27:08, Info MIG COutOfProcPluginFactory::FreeSurrogateHost: Shutdown in progress. 27:08, Info MIG COutOfProcPluginFactory::LaunchSurrogateHost::CommandLine: -shortened- 27:08, Info MIG COutOfProcPluginFactory::LaunchSurrogateHost: Successfully launched host and got control object. 27:08, Error Gather failed. Last error: 0x00000000 27:08, Info Gather ended at 10/5/2016 23:27:08 with result 44 27:08, Info Leaving MigGather method 27:08, Error SP SPDoFrameworkGather: Gather operation failed. Error: 0x0000002C
This analysis indicates that the Windows upgrade error can be resolved by deleting the C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18[CN] file. Note: In this example, the full, unshortened file name is C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18\be8228fb2d3cb6c6b0ccd9ad51b320b4_a43d512c-69f2-42de-aef9-7a88fabdaa3f.
A frequently observed result code is 0xC1900101. This result code can be thrown at any stage of the upgrade process, with the exception of the downlevel phase. 0xC1900101 is a generic rollback code, and usually indicates that an incompatible driver is present. The incompatible driver can cause blue screens, system hangs, and unexpected reboots. Analysis of supplemental log files is often helpful, such as:
- The minidump file: $Windows.~bt\Sources\Rollback\setupmem.dmp,
- Event logs: $Windows.~bt\Sources\Rollback*.evtx
- The device install log: $Windows.~bt\Sources\Rollback\setupapi\setupapi.dev.log
The device install log is particularly helpful if rollback occurs during the sysprep operation (extend code 0x30018). To resolve a rollback due to driver conflicts, try running setup using a minimal set of drivers and startup programs by performing a clean boot before initiating the upgrade process.
See the following general troubleshooting procedures associated with a result code of 0xC1900101:
Result codes starting with the digits 0x800 are also important to understand. These error codes indicate general operating system errors, and are not unique to the Windows upgrade process. Examples include timeouts, devices not functioning, and a process stopping unexpectedly.
See the following general troubleshooting procedures associated with a result code of 0x800xxxxx:
Other result codes
|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.
|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.||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.|
|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 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 before you enable update synchronization. However, if you have already run into this problem, do the following:
For detailed information on how to run these steps check out How to delete upgrades in WSUS.
|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.
Other error codes
|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.|
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.
Windows 10 FAQ for IT professionals
Windows 10 Enterprise system requirements
Windows 10 Specifications
Windows 10 IT pro forums
Fix Windows Update errors by using the DISM or System Update Readiness tool
Not finding content you need? Windows 10 users, tell us what you want on Feedback Hub.