deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 13:27:23 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Merged PR 5493: Explained code section examples more clearly

Browse Source 
Explained code section examples more clearly
This commit is contained in:
Greg Lindsay 2018-01-26 16:22:04 +00:00
parent 1c66ac5468
commit ef80b8989a
1 changed files with 17 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
windows/deployment/upgrade/resolve-windows-10-upgrade-errors.md
View File

@ -7,7 +7,7 @@ ms.mktglfcycl: deploy
ms.sitesec: library
ms.pagetype: deploy
author: greg-lindsay
ms.date: 01/11/2018
ms.date: 01/25/2018
ms.localizationpriority: high
---
@ -105,15 +105,23 @@ Note: If only a result code is returned, this can be because a tool is being use
Result codes can be matched to the type of error encountered. To match a result code to an error:
1. Identify the error code type, either Win32 or NTSTATUS, using the first hexadecimal digit:
<br>8 = Win32 error code (ex: 0x**8**0070070)
<br>C = NTSTATUS value (ex: 0x**C**1900107)
2. Write down the last 4 digits of the error code (ex: 0x8007**0070** = 0070). These digits correspond to the last 16 bits of the [HRESULT](https://msdn.microsoft.com/en-us/library/cc231198.aspx) or the [NTSTATUS](https://msdn.microsoft.com/en-us/library/cc231200.aspx) structure.
3. 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](https://msdn.microsoft.com/en-us/library/cc231199.aspx), or an [NTSTATUS value](https://msdn.microsoft.com/en-us/library/cc704588.aspx).
1. Identify the error code type as either Win32 or NTSTATUS using the first hexadecimal digit:
<br>**8** = Win32 error code (ex: 0x**8**0070070)
<br>**C** = NTSTATUS value (ex: 0x**C**1900107)
2. Write down the last 4 digits of the error code (ex: 0x8007**0070** = 0070). These digits are the actual error code type as defined in the [HRESULT](https://msdn.microsoft.com/en-us/library/cc231198.aspx) or the [NTSTATUS](https://msdn.microsoft.com/en-us/library/cc231200.aspx) structure. Other digits in the code identify things such as the device type that produced the error.
3. Based on the type of error code determined in the first step (Win32 or NTSTATUS), match the 4 digits derived from the second step to either a Win32 error code or NTSTATUS value using the following links:
a. [Win32 error code](https://msdn.microsoft.com/en-us/library/cc231199.aspx)
b. [NTSTATUS value](https://msdn.microsoft.com/en-us/library/cc704588.aspx)
For example:
- 0x80070070 = Win32 = 0070 = 0x00000070 = ERROR_DISK_FULL
- 0xC1900107 = NTSTATUS = 0107 = 0x00000107 = STATUS_SOME_NOT_MAPPED
Examples:
- 0x80070070
- 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: ERROR_DISK_FULL
- 0xC1900107
- Based on the "C" this is an NTSTATUS error code
- The last four digits are 0107, so look up 0x00000107 in the NTSTATUS values table
- The error is: 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.