diff --git a/windows/deploy/resolve-windows-10-upgrade-errors.md b/windows/deploy/resolve-windows-10-upgrade-errors.md index 5aef1c48e6..634137d387 100644 --- a/windows/deploy/resolve-windows-10-upgrade-errors.md +++ b/windows/deploy/resolve-windows-10-upgrade-errors.md @@ -45,15 +45,16 @@ WIM = Windows image (Microsoft) Setup will return two codes: 1. A result code, corresponding to a specific Win32 error. -2. An extend code, corresponding to the phase and the operation when a failure occurred. +2. An extend code, representing the phase when a failure occurred. + - 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** +>For example, a result code of **0xC1900101** with an extend code of **0x4000D** will be returned as: **0xC1900101 - 0x4000D**. In this case, the extend code 0x4000D can be evaluated as representing a problem during phase 4 (0x4) with data migration (000D). A list of extend codes and the associated phase and operation is provided below. -Note: If only a single code is returned, this can be because a tool is being used that does not capture the extend code, for example the [Windows 10 Upgrade Assistant](https://support.microsoft.com/en-us/kb/3159635). +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](https://support.microsoft.com/en-us/kb/3159635) then only a result code might be returned. ### Extend codes -The following tables display the phase and operation assoicated with an extend code: +The following tables provide the corresponding phase and operation for values of an extend code: @@ -114,30 +115,41 @@ The following tables display the phase and operation assoicated with an extend c
Extend code: phase
-For example: A code of 0x**4**00**0D** is a problem during **phase 4** with the **data migration** operation (**4** = SP_EXECUTION_OOBE_BOOT, **0D** = SP_EXECUTION_OP_MIGRATE_DATE). - ## Log files -Various log files are created during each phase of the upgrade process. These log files are essential for detailed troubleshooting of upgrade problems. The most useful log is **setupact.log**, which is located in a different folder depending on the phase in which a problem occurred with the upgrade process. Recall that you can determine the phase from - -See the following table. +Various log files are created during each phase of the upgrade process. These log files are essential for troubleshooting upgrade problems. The most useful log is **setupact.log**, which is located in a different folder depending on the phase in which a problem occurred with the upgrade process. 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 fileDescriptionLocationWhen to use -
setupact.logContains information about setup actions during the installation.Down-Level phase: $Windows.~BT\Sources\PantherAll down-level failures and starting point for rollback investigations. -
setuperr.logContains information about setup errors during the installation.Same location as setupact.log -
Setupmem.dmpIf OS bugchecks during upgrade, setup will attempt to extract a mini-dump.$Windows.~BT\Sources\Rollback -
miglog.xmlContains information about the user directory structure. This information includes security identifiers (SIDs).Windows\Panther -
Appraiser XML logsContains application compatibility information.$Windows.~BT\Sources\Panther -
BlueBox.logContains information communication between setup.exe and Windows Update.Windows\Logs\Mosetup
Log filePhase: LocationDescriptionWhen to use + +
setupact.logDown-Level:
$Windows.~BT\Sources\Panther		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. +
OOBE:
$Windows.~BT\Sources\Panther		Contains information about actions during the OOBE phase.Investigating rollbacks that failed during OOBE phase and operations – 0x4001C, 0x4001D, 0x4001E, 0x4001F. +
Rollback:
$Windows.~BT\Sources\Panther		Contains information about actions during rollback.Investigating generic rollbacks - 0xC1900101. +
Pre-initialization (prior to downlevel):
$Windows.~BT\Sources\Panther		Contains information about initializing setup.If setup fails to launch. +
Post-upgrade (after OOBE):
$Windows.~BT\Sources\Panther		Contains information about setup actions during the installation.Investigate post-upgrade related issues. + +
setuperr.logSame as setupact.logContains information about setup errors during the installation.Review all errors encountered during the installation phase. + +
miglog.xmlPost-upgrade (after OOBE):
Windows\Panther		Contains information about what was migrated during the installation.Identify post upgrade data migration issues. + +
BlueBox.logDown-Level:
Windows\Logs\Mosetup		Contains information communication between setup.exe and Windows Update.Use during WSUS and WU down-level failures or for 0xC1900107. + +
Supplemental rollback logs:
+Setupmem.dmp
+setupapi.dev.log
+Event logs (*.evtx) + + +		$Windows.~BT\Sources\RollbackAdditional 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. + + + + +
## Common error codes and resolution procedures