From 0a5c0805b5ede5d9c30dbdec4bfebdef5e30cc6d Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Thu, 29 Sep 2016 16:59:39 -0700 Subject: [PATCH] updates --- .../resolve-windows-10-upgrade-errors.md | 45 ++++++++++++++++--- 1 file changed, 39 insertions(+), 6 deletions(-) diff --git a/windows/deploy/resolve-windows-10-upgrade-errors.md b/windows/deploy/resolve-windows-10-upgrade-errors.md index c8a8cf8627..9d8626d2f0 100644 --- a/windows/deploy/resolve-windows-10-upgrade-errors.md +++ b/windows/deploy/resolve-windows-10-upgrade-errors.md @@ -155,7 +155,7 @@ Event logs: Generic rollbacks (0xC1900101) or unexpected reboots. ## 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. Analysis of supplemental log files is often 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. +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 is a generic rollback code, and usually indicates that an incompatible driver is present. The incompatible driver can cause blue screens, system hangs, and unexpected reboots. Analysis of supplemental log files is often helpful, such as the minidump file (($Windows.~bt\Sources\Rollback\setupmem.dmp), event logs (($Windows.~bt\Sources\Rollback\*.evtx), and the device install log ($Windows.~bt\Sources\Rollback\setupapi\setupapi.dev.log). The device install log is particularly helpful if rollback occurs during the sysprep operation (extend code 0x30018). To resolve a rollback due to driver conflicts, 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 some of the most common error codes that contain a result code of 0xC1900101: @@ -165,13 +165,15 @@ A common result code is 0xC1900101. This result code can be thrown at any stage
Code -
0xC1900101 - 0x20017 +
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. +
@@ -293,7 +295,7 @@ Other common codes and mitigation procedures: Code -Here is a code +8007042B - 0x4000D @@ -324,7 +326,7 @@ Here is a mitigation procedure. Code -Here is a code +8007001F - 0x4000D @@ -355,7 +357,7 @@ Here is a mitigation procedure. Code -Here is a code +8007042B - 0x4001E @@ -387,7 +389,38 @@ Here is a mitigation procedure. Code -Here is a code +800704B8 - 0x3001A + + + +

+
Cause +
+ +Here is a cause. + +
+ + + + + +
Mitigation +
+ +Here is a mitigation procedure. + +
+ + + + + + +
Code +
+ +8000405 - 0x20007