Upgrade error codes
Applies to: Windows 10
This is a 400 level topic (advanced).
See Resolve Windows 10 upgrade errors for a full list of topics in this article.
If the upgrade process isn't successful, Windows Setup will return two codes:
- A result code: The result code corresponds to a specific Win32 or NTSTATUS 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.
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.
If you are unable to locate the result and extend error codes, you can attempt to find these codes using Event Viewer. For more information, see Windows Error Reporting.
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 article.
The following set of result codes is associated with Windows Setup compatibility warnings:
|0xC1900210||MOSETUP_E_COMPAT_SCANONLY||Setup didn't find any compat issue|
|0xC1900208||MOSETUP_E_COMPAT_INSTALLREQ_BLOCK||Setup found an actionable compat issue, such as an incompatible app|
|0xC1900204||MOSETUP_E_COMPAT_MIGCHOICE_BLOCK||The migration choice selected isn't available (ex: Enterprise to Home)|
|0xC1900200||MOSETUP_E_COMPAT_SYSREQ_BLOCK||The computer isn't eligible for Windows 10|
|0xC190020E||MOSETUP_E_INSTALLDISKSPACE_BLOCK||The computer doesn't have enough free space to install|
A list of modern setup (mosetup) errors with descriptions in the range is available in the Resolution procedures section in this article.
Other result codes can be matched to the specific type of error encountered. To match a result code to an error:
Identify the error code type as either Win32 or NTSTATUS using the first hexadecimal digit:
8 = Win32 error code (ex: 0x80070070)
C = NTSTATUS value (ex: 0xC1900107)
Write down the last four digits of the error code (ex: 0x80070070 = 0070). These digits are the actual error code type as defined in the HRESULT or the NTSTATUS structure. Other digits in the code identify things such as the device type that produced the error.
Based on the type of error code determined in the first step (Win32 or NTSTATUS), match the four digits derived from the second step to either a Win32 error code or NTSTATUS value using the following links:
- Based on the "8", this is a Win32 error code.
- The last four digits are 0070, so look up 0x00000070 in the Win32 error code table.
- The error is:
- Based on the "C", this is an NTSTATUS error code.
- The last four digits are 0107, so look up 0x00000107 in the NTSTATUS value table.
- The error is:
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 extra 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.
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).