From 109e826c2ab2ec34346c69e193043377ed268203 Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Thu, 29 Sep 2016 15:58:57 -0700 Subject: [PATCH] updates --- .../resolve-windows-10-upgrade-errors.md | 77 ++++++++++++++----- 1 file changed, 56 insertions(+), 21 deletions(-) diff --git a/windows/deploy/resolve-windows-10-upgrade-errors.md b/windows/deploy/resolve-windows-10-upgrade-errors.md index df5023588a..797d592ae0 100644 --- a/windows/deploy/resolve-windows-10-upgrade-errors.md +++ b/windows/deploy/resolve-windows-10-upgrade-errors.md @@ -153,21 +153,27 @@ Event logs: Generic rollbacks (0xC1900101) or unexpected reboots. -## Common errors +## Common error codes -A common result code is 0xC1900101. This result code can be thrown at any stage of the upgrade process, with the exception of the SafeOS phase. 0xC1900101 usually indicates that an incompatible driver is present, which can cause blue screens, system hangs, and unexpected reboots. +A common result code is 0xC1900101. This result code can be thrown at any stage of the upgrade process, with the exception of the SafeOS phase. 0xC1900101 usually indicates that an incompatible driver is present, which can cause blue screens, system hangs, and unexpected reboots. Analysis of all available supplemental log files is typically helpful in indentifying the incompatible driver. You can also attempt to run setup in the absence of drivers by performing a [clean boot](https://support.microsoft.com/en-us/kb/929135) before initiating the upgrade process. -Analysis of all available supplemental log files is typically helpful in indentifying the incompatible driver. You can also attempt to run setup in the absence of drivers by performing a [clean boot](https://support.microsoft.com/en-us/kb/929135) before initiating the upgrade process. The following general procedures can be used to diagnose a result code of 0xC1900101 during different phases of Windows Setup: +

The following general procedures can be used to diagnose a result code of 0xC1900101 during different phases of Windows Setup: - - + +
0xC1900101 - 0x20017
+ + +
+
Code +
0xC1900101 - 0x20017 +
+ +

Cause
A driver has caused an illegal operation. -
Windows was not able to migrate the driver, resulting in a rollback of the operating system. +
Windows was not able to migrate the driver, resulting in a rollback of the operating system.

Mitigation @@ -179,16 +185,18 @@ Analysis of all available supplemental log files is typically helpful in indenti
+
Code +
0xC1900101 - 0x30018
-

- - + + +
0xC1900101 - 0x30018
- +

Cause -
A device driver has stopped responding to setup.exe during the upgrade process. +
A device driver has stopped responding to setup.exe during the upgrade process.
Mitigation @@ -199,16 +207,18 @@ Disconnect all peripheral devices that are connected to the system, except for t
+
Code +
0xC1900101 - 0x4000D
-

- - + + + +
0xC1900101 - 0x4000D
- +

Cause -
A rollback occurred due to a driver configuration issue. +
A rollback occurred due to a driver configuration issue.
Mitigation @@ -235,17 +245,20 @@ Disconnect all peripheral devices that are connected to the system, except for t
+
Code +
0xC1900101 - 0x40017
-

- - + +
0xC1900101 - 0x40017
- +

Cause
Windows 10 upgrade failed after the second reboot. -
This is usually caused by a faulty driver. For example: antivirus filter drivers or encryption drivers. +
This is usually caused by a faulty driver. For example: antivirus filter drivers or encryption drivers.
Mitigation @@ -257,10 +270,32 @@ For more information, see [How to perform a clean boot in Windows](https://suppo
+ + + + + + + + + + + + + + + + + + + + + ## Common errors I've edited but don't know how to classify