diff --git a/windows/deploy/resolve-windows-10-upgrade-errors.md b/windows/deploy/resolve-windows-10-upgrade-errors.md index cac06aad4a..5744d2f08c 100644 --- a/windows/deploy/resolve-windows-10-upgrade-errors.md +++ b/windows/deploy/resolve-windows-10-upgrade-errors.md @@ -117,32 +117,34 @@ The following tables provide the corresponding phase and operation for values of ## Log files -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: +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 filePhase: LocationDescriptionWhen to use +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. +
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. +
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. +
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. +
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:
+
Supplemental rollback logs:
Setupmem.dmp
setupapi.dev.log
Event logs (*.evtx) -		$Windows.~BT\Sources\RollbackAdditional logs collected during rollback. - +$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. @@ -159,14 +161,14 @@ A common result code is 0xC1900101. This result code can be thrown at any stage - - - - + + - - - + + - - - + + - - - + + - - - + + + @@ -231,9 +233,9 @@ For more information, see [How to perform a clean boot in Windows](https://suppo
Error code -Cause -Mitigation +Error code +Cause +Mitigation
0xC1900101 - 0x20017A driver has caused an illegal operation and Windows was not able to migrate the driver, resulting in a rollback of the operating system.To resolve this issue:
+		0xC1900101 - 0x20017A driver has caused an illegal operation and Windows was not able to migrate the driver, resulting in a rollback of the operating system.To resolve this issue:
1. Make sure all that drivers are updated.
2. Open the Setuperr.log and Setupact.log files under the %windir%\Panther directory, and then locate the problem drivers. Refer: [Understanding Failures and Log Files](https://technet.microsoft.com/en-us/library/ee851579.aspx)
@@ -175,18 +177,18 @@ A common result code is 0xC1900101. This result code can be thrown at any stage
0xC1900101 - 0x30018A device driver has stopped responding to setup.exe during the upgrade process.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. +0xC1900101 - 0x30018A device driver has stopped responding to setup.exe during the upgrade process.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 - 0x4000DA driver configuration issue occurred during the Windows setup process and a rollback occurred.

Review the rollback log and determine the stop code. The rollback log is located in the **C:\$Windows.~BT\Sources\Panther** folder. Look for text similar to the following: -

+

0xC1900101 - 0x4000DA driver configuration issue occurred during the Windows setup process and a rollback occurred.

Review the rollback log and determine the stop code. The rollback log is located in the **C:\$Windows.~BT\Sources\Panther** folder. Look for text similar to the following: +


Info SP Crash 0x0000007E detected
Info SP Module name :
Info SP Bugcheck parameter 1 : 0xFFFFFFFFC0000005 @@ -197,7 +199,7 @@ A common result code is 0xC1900101. This result code can be thrown at any stage
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:
+

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.
@@ -207,9 +209,9 @@ A common result code is 0xC1900101. This result code can be thrown at any stage

0xC1900101 - 0x40017Windows 10 upgrade fails after the second reboot, which is most like to be caused by a faulty driver, for example antivirus filter drivers or encryption drivers.Clean boot into Windows, and then attempt the upgrade to Windows 10.
+		0xC1900101 - 0x40017Windows 10 upgrade fails after the second reboot, which is most like to be caused by a faulty driver, for example antivirus filter drivers or encryption drivers.Clean boot into Windows, and then attempt the upgrade to Windows 10.
For more information, see [How to perform a clean boot in Windows](https://support.microsoft.com/en-us/kb/929135). @@ -218,9 +220,9 @@ For more information, see [How to perform a clean boot in Windows](https://suppo
0x8007002C - 0x4000DThe user cancelled an interactive dialog.Start the upgrade process again again.0x8007002C - 0x4000DThe user cancelled an interactive dialog.Start the upgrade process again again.
-
Error code -Cause -Mitigation +Error code +Cause +Mitigation