diff --git a/windows/deploy/images/upgrade-process.png b/windows/deploy/images/upgrade-process.png new file mode 100644 index 0000000000..b2b77708fc Binary files /dev/null and b/windows/deploy/images/upgrade-process.png differ diff --git a/windows/deploy/resolve-windows-10-upgrade-errors.md b/windows/deploy/resolve-windows-10-upgrade-errors.md index 3002f1a5b2..5765d2849c 100644 --- a/windows/deploy/resolve-windows-10-upgrade-errors.md +++ b/windows/deploy/resolve-windows-10-upgrade-errors.md @@ -16,96 +16,169 @@ localizationpriority: high **Applies to** - Windows 10 -Some information about this topic +This topic provides a brief introduction to Windows 10 installation processes and provides resolution procedures you can use to resolve common problems. -## An intro topic +## The Windows 10 upgrade process -Maybe an image here +The Windows Setup application is used to upgrade a computer to Windows 10, or to perform a clean installation. Windows Setup starts and restarts the computer, gathers information, copies files, and creates or adjusts configuration settings. When performing an operating system upgrade, Windows Setup uses the following phases: -- image - +1. Downlevel phase: The downlevel phase is run within the previous operating system. Installation components are gathered. +2. Safe OS phase: A recovery partition is configured and updates are installed. An OS rollback is prepared if needed. + - Example error codes during this phase: 0x2000C, 0x20017 +3. First boot phase: Initial settings are applied. + - Example error codes during this phase: 0x30018, 0x3000D +4. Second boot phase: Final settings are applied. This is also called the OOBE boot phase. + - Example error codes during this phase: 0x4000D, 0x40017 -## Some troubleshooting information +>The computer can also enter a fifth, rollback (uninstall) phase if the upgrade is unsuccessful. -Some text here +Four phases of a Windows 10 upgrade: - +![Upgrade process](images/upgrade-process.png) - - - - - +DU = Driver/device updates.
+OOBE = Out of box experience.
+WIM = Windows image (Microsoft) + +## Upgrade error codes + +Setup will typically 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. + +For example, a result code of 0xC1900101 with an extend code of 0x4000D will be returned as: **0xC1900101 - 0x4000D** + +>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). + +### Extend codes + +The phase and operation of an extend code maps to the following tables. + +
Error codeCauseMitigation
+ + + + + +
+
HexPhase +
0SP_EXECUTION_UNKNOWN +
1SP_EXECUTION_DOWNLEVEL +
2SP_EXECUTION_SAFE_OS +
3SP_EXECUTION_FIRST_BOOT +
4SP_EXECUTION_OOBE_BOOT +
5SP_EXECUTION_UNINSTALL +
+
+
HexOperation +
0SP_EXECUTION_OP_UNKNOWN +
1SP_EXECUTION_OP_COPY_PAYLOAD +
2SP_EXECUTION_OP_DOWNLOAD_UPDATES +
3SP_EXECUTION_OP_INSTALL_UPDATES +
4SP_EXECUTION_OP_INSTALL_RECOVERY_ENVIRONMENT +
5SP_EXECUTION_OP_INSTALL_RECOVERY_IMAGE +
6SP_EXECUTION_OP_REPLICATE_OC +
7SP_EXECUTION_OP_INSTALL_DRVIERS +
8SP_EXECUTION_OP_PREPARE_SAFE_OS +
9SP_EXECUTION_OP_PREPARE_ROLLBACK +
ASP_EXECUTION_OP_PREPARE_FIRST_BOOT +
BSP_EXECUTION_OP_PREPARE_OOBE_BOOT +
CSP_EXECUTION_OP_APPLY_IMAGE +
DSP_EXECUTION_OP_MIGRATE_DATA +
ESP_EXECUTION_OP_SET_PRODUCT_KEY +
FSP_EXECUTION_OP_ADD_UNATTEND +
+
+
HexOperation +
10SP_EXECUTION_OP_ADD_DRIVER +
11SP_EXECUTION_OP_ENABLE_FEATURE +
12SP_EXECUTION_OP_DISABLE_FEATURE +
13SP_EXECUTION_OP_REGISTER_ASYNC_PROCESS +
14SP_EXECUTION_OP_REGISTER_SYNC_PROCESS +
15SP_EXECUTION_OP_CREATE_FILE +
16SP_EXECUTION_OP_CREATE_REGISTRY +
17SP_EXECUTION_OP_BOOT +
18SP_EXECUTION_OP_SYSPREP +
19SP_EXECUTION_OP_OOBE +
1ASP_EXECUTION_OP_BEGIN_FIRST_BOOT +
1BSP_EXECUTION_OP_END_FIRST_BOOT +
1CSP_EXECUTION_OP_BEGIN_OOBE_BOOT +
1DSP_EXECUTION_OP_END_OOBE_BOOT +
1ESP_EXECUTION_OP_PRE_OOBE +
1FSP_EXECUTION_OP_POST_OOBE +
20SP_EXECUTION_OP_ADD_PROVISIONING_PACKAGE +
+
+ +For example, you can use these tables to interpret extend code of 0x**4**00**0D** as a problem during phase 4 with data migration (**4** = SP_EXECUTION_OOBE_BOOT, **0D** = SP_EXECUTION_OP_MIGRATE_DATE). + +## Log files + +During each phase of the upgrade process, setup log files are created in various locations. These log files can be very useful in troubleshooting upgrade problems. + + + + + + + + + + + + + + + + +
Log fileDescriptionLocation
setupact.logContains information about setup actions during the installation. +

This is the most important log for diagnosing setup issues.

+Down-Level phase: $Windows.~BT\Sources\Panther
+Rollback phase: $Windows.~BT\Sources\Rollback
+First & second boot phase: $Windows.~BT\Sources\Panther\UnattendGC
+Pre-initialization: Windows
+Post-upgrade: Windows\Panther +
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
+ +## Common error codes and resolution procedures + + + + - - + + + + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + - - - - + + + + + + - - - - - - - - - + + + - - - - - - - - - - - - - + + + - - - - -
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:
-
0xC1900200Setup.exe has detected that the machine does not meet the minimum system requirements.Ensure the system you are trying to upgrade meets the minimum system requirements.

See [Windows 10 specifications](https://www.microsoft.com/en-us/windows/windows-10-specifications) for information.

0x8007002C - 0x4000DThe user cancelled an interactive dialog.Start the upgrade process again again.
0x80090011A device driver error occurred during user data migration.Contact your hardware vendor and get all the device drivers updated. It is recommended to have an active internet connection during upgrade process. -

Ensure that “Download and install updates (recommended)” is accepted at the start of the upgrade process.

0xC7700112Failure to complete writing data to the system drive, possibly due to write access failure on the hard disk.This issue is resolved in the latest version of Upgrade Assistant. -

Ensure that “Download and install updates (recommended)” is accepted at the start of the upgrade process.

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. -

0x80190001An unexpected error was encountered while attempting to download files required for upgrade.To resolve this issue, download and run the media creation tool. See [Download windows 10](https://www.microsoft.com/en-us/software-download/windows10). -
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)
3. Update or uninstall the problem drivers.
0x80246007The update was not downloaded successfully.Attempt other methods of upgrading the operatign system.
-Download and run the media creation tool. See [Download windows 10](https://www.microsoft.com/en-us/software-download/windows10). -
Attempt to upgrade using .ISO or USB.
-**Note**: Windows 10 Enterprise isn’t available in the media creation tool. For more information, go to the [Volume Licensing Service Center](https://www.microsoft.com/licensing/servicecenter/default.aspx). + +
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.

0xC1900201The system did not pass the minimum requirements to install the update.Contact the hardware vendor to get the latest updates.
0x8007002C - 0x4000DThe user cancelled an interactive dialog.Start the upgrade process again again.
0x80240017The upgrade is unavailable for this edition of Windows.Administrative policies enforced by your organization might be preventing the upgrade. Contact your IT administrator.
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 : @@ -118,818 +191,312 @@ Download and run the media creation tool. See [Download windows 10](https://www.

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:
- - Make sure you have enough disk space.
- - If a driver is identified in the bug check message, disable the driver, or check with the manufacturer for driver updates.
- - Try changing video adapters.
- - Check with your hardware vendor for any BIOS updates.
- - Disable BIOS memory options such as caching or shadowing. + +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.
+3. Try changing video adapters.
+4. Check with your hardware vendor for any BIOS updates.
+5. Disable BIOS memory options such as caching or shadowing.

0x80070020The existing process cannot access the file because it is being used by another process.Use the MSCONFIG tool to perform a clean boot on the machine and then try to perform the update again. For more information, see [How to perform a clean boot in Windows](https://support.microsoft.com/en-us/kb/929135).
0x80070522The user doesn’t have required privilege or credentials to upgrade.Ensure that you have signed in as a local administrator or have local administrator privileges.
0xC1900107A cleanup operation from a previous installation attempt is still pending and a system reboot is required in order to continue the upgrade. +
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). + +

Ensure you select the option to "Download and install updates (recommended)."

Reboot the device and run setup again. If restarting device does not resolve the issue, then use the Disk Cleanup utility and cleanup the temporary as well as the System files. For more information, see [Disk cleanup in Windows 10](https://support.microsoft.com/en-us/instantanswers/8fef4121-711b-4be1-996f-99e02c7301c2/disk-cleanup-in-windows-10).
0xC1900209The user has chosen to cancel because the system does not pass the compatibility scan to install the update. Setup.exe will report this error when it can upgrade the machine with user data but cannot migrate installed applications.Incompatible software is blocking the upgrade process. Uninstall the application and try the upgrade again. See [Windows 10 Pre-Upgrade Validation using SETUP.EXE](https://blogs.technet.microsoft.com/mniehaus/2015/08/23/windows-10-pre-upgrade-validation-using-setup-exe/) for more information. +
+ +## Common errors I've edited but don't know how to classify + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - - - + + + - - - - - - - - - + + + - - - - + + + -
Error code +Cause +Mitigation +
0xC1900200Setup.exe has detected that the machine does not meet the minimum system requirements.Ensure the system you are trying to upgrade meets the minimum system requirements.

See [Windows 10 specifications](https://www.microsoft.com/en-us/windows/windows-10-specifications) for information.

0x80090011A device driver error occurred during user data migration.Contact your hardware vendor and get all the device drivers updated. It is recommended to have an active internet connection during upgrade process. +

Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process.

0xC7700112Failure to complete writing data to the system drive, possibly due to write access failure on the hard disk.This issue is resolved in the latest version of Upgrade Assistant. +

Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process.

0x80190001An unexpected error was encountered while attempting to download files required for upgrade.To resolve this issue, download and run the media creation tool. See [Download windows 10](https://www.microsoft.com/en-us/software-download/windows10). +
0x80246007The update was not downloaded successfully.Attempt other methods of upgrading the operatign system.
+Download and run the media creation tool. See [Download windows 10](https://www.microsoft.com/en-us/software-download/windows10). +
Attempt to upgrade using .ISO or USB.
+**Note**: Windows 10 Enterprise isn’t available in the media creation tool. For more information, go to the [Volume Licensing Service Center](https://www.microsoft.com/licensing/servicecenter/default.aspx). +
0xC1900201The system did not pass the minimum requirements to install the update.Contact the hardware vendor to get the latest updates.
0x80240017The upgrade is unavailable for this edition of Windows.Administrative policies enforced by your organization might be preventing the upgrade. Contact your IT administrator.
0x80070020The existing process cannot access the file because it is being used by another process.Use the MSCONFIG tool to perform a clean boot on the machine and then try to perform the update again. For more information, see [How to perform a clean boot in Windows](https://support.microsoft.com/en-us/kb/929135).
0x80070522The user doesn’t have required privilege or credentials to upgrade.Ensure that you have signed in as a local administrator or have local administrator privileges.
0xC1900107A cleanup operation from a previous installation attempt is still pending and a system reboot is required in order to continue the upgrade. +Reboot the device and run setup again. If restarting device does not resolve the issue, then use the Disk Cleanup utility and cleanup the temporary as well as the System files. For more information, see [Disk cleanup in Windows 10](https://support.microsoft.com/en-us/instantanswers/8fef4121-711b-4be1-996f-99e02c7301c2/disk-cleanup-in-windows-10).
0xC1900209The user has chosen to cancel because the system does not pass the compatibility scan to install the update. Setup.exe will report this error when it can upgrade the machine with user data but cannot migrate installed applications.Incompatible software is blocking the upgrade process. Uninstall the application and try the upgrade again. See [Windows 10 Pre-Upgrade Validation using SETUP.EXE](https://blogs.technet.microsoft.com/mniehaus/2015/08/23/windows-10-pre-upgrade-validation-using-setup-exe/) for more information.

You can also download the [Windows Assessment and Deployment Kit (ADK) for Windows 10](http://go.microsoft.com/fwlink/p/?LinkId=526740) and install Application Compatibility Tools.

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. See [How to perform a clean boot in Windows](https://support.microsoft.com/en-us/kb/929135) for more information. -

Ensure you select the option to “Download and install updates (recommended).” +

display is not compatibleThe display card installed is not compatible with Windows 10.Uninstall the display adapter and start the upgrade again. When setup completes successfully, install the latest display adapter driver using Windows Update or by downloading from the computer manufacturers website. Use compatibility mode if necessary.
display is not compatibleThe display card installed is not compatible with Windows 10.Uninstall the display adapter and start the upgrade again. When setup completes successfully, install the latest display adapter driver using Windows Update or by downloading from the computer manufacturers website. Use compatibility mode if necessary. -
0x8007002 This error is specific to upgrades using System Center Configuration Manager 2012 R2 SP1 CU3 (5.00.8238.1403)Analyze the SMSTS.log and verify that the upgrade is failing on "Apply Operating system" Phase: Error 80072efe DownloadFileWithRanges() failed. 80072efe. ApplyOperatingSystem (0x0760) +
0x8007002 This error is specific to upgrades using System Center Configuration Manager 2012 R2 SP1 CU3 (5.00.8238.1403)Analyze the SMSTS.log and verify that the upgrade is failing on "Apply Operating system" Phase: Error 80072efe DownloadFileWithRanges() failed. 80072efe. ApplyOperatingSystem (0x0760)

The error 80072efe means that the connection with the server was terminated abnormally.

To resolve this issue, try the OS Deployment test on a client in same VLAN as the Configuration Manager server. Check the network configuration for random client-server connection issues happening on the remote VLAN.

Error 800705B4: This operation returned because the timeout period expired.A time out issue set by the task sequence limitation to 180 mins of run time. This can also occur if the System Center client is corrupted.Review the SMSTS.log file and verify the following error is displayed:
+
Error 800705B4: This operation returned because the timeout period expired.A time out issue set by the task sequence limitation to 180 mins of run time. This can also occur if the System Center client is corrupted.Review the SMSTS.log file and verify the following error is displayed:
Command line execution failed (800705B4) TSManager 3/30/2016 10:11:29 PM 8920 (0x22D8)
Failed to run the action: Upgrade Windows.

To resolve this issue, increase the default task sequence run time and change the task sequence to have the content downloaded locally prior to installation.

+## Appendix A: Less common errors I haven't edited yet -## Appendix A: Less common errors + -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-

Error Codes

-
-

Cause

-
-

Mitigation

-
-

Contact - your system administrator to upgrade Windows Server or Enterprise Editions

-
-

This - issue occurs if you run the updater tool. The tool works only with the - Windows 10 Home, Pro, and Education editions.

-
-

To - resolve this issue, use a different method to upgrade to Windows 10 version - 1607. For example, download the ISO, and then run Setup from it.

-
-

When - doing an upgrade to Windows Version 1607 is it supported to use a custom - install.wim (sysprepped) instead of the default install.wim that comes with - Windows Version 1607

-
-

Unsupported

-
-

It - is not supported to replace the install.wim with custom wim (sysprepped or - not). It is supported to do some minor changes to the default install.wim - such as injecting latest cumulative update or remove inbox apps.

-
-

0xC1420127

-
-

The - typical conversion of the error means that the specified image in the - specified wim is already mounted for read/write access.
- When we launch the setup.exe, it checks the registry key 
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WIMMount\Mounted Images to check for - any previously mounted WIM files on the system and if the image is mounted we - will get this error.

-
-

This - error would be very rare on Upgrades of WIN10 specially when upgrading to the - Anniversary 1607 Build. This issue has been fixed with the Cumulative updates - released in June 2016 for Windows 10. When we perform an Upgrade, it is recommended - to Perform a Windows Update first and apply all important updates on the - current OS and then start the Upgrade process for Windows 10.

-
-

0x8004100E

-
-

This - error code indicates that there is a problem with an Application that has an - Invalid WMI Namespace

-
-

In - order to fix this problem, we need to open Application Event log and Check - for Errors for various applications that could be causing this - error. You can use WMIDIAG tool and make sure that the WMI is working - well. The step by step instructions are available at: - https://technet.microsoft.com/en-us/library/ff404265.aspx

-
-

0x80070003- - 0x20007

-
-

This - error occurs when there is problem with the Internet connection during the - Windows 10 upgrade.

-
-

Since - this error indicates that the internet connection ran into a problem, you may - attempt to fix the connectivity issues and reattempt the download of the - files.
- Alternatively, you may re-create installation media using "Media - Creation Tool" from a different connected system. Refer: - https://www.microsoft.com/en-us/software-download/windows10
-
- You can either create a USB drive or an ISO.

-
-

0x80070004 - - 0x3000D

-
-

SYSTEM, - LOCAL, SELF, System, and Network are reserved names that can’t be used for - Computer Name.

-
-

Ensure - that you do not use the reserved names as the Computer names. Rename the - system to a valid Computer name.
- See KB 3086101 for more details.

-
-

0x80070004 - - 0x50012

-
-

The - Computer account for the system has an invalid name.

-
-

Please - ensure that the machine name does not have any invalid characters (See - https://technet.microsoft.com/en-us/library/cc749460(v=ws.10).aspx). - Additionally, the names should not be any of the reserved names for systems. - Rename the system to a valid computer name and try the Setup again. See KB - 3086101 for more details.

-
-

0x80070005 - - 0x4000D

-
-

This - error code means The installation failed in the SECOND_BOOT phase with an - error in during MIGRATE_DATA operation.

-
-

This - issue may occur if we have any application / driver that is causing an issue - while the upgrade to Windows 10 is going on.  Preform a clean boot on - the system. Refer https://support.microsoft.com/en-us/kb/929135 for steps to - perform a Clean boot.

-
-

0x80070057

-
-

This - error means that One or more arguments are invalid

-
-

This - is a very generic error, and it could be due to any of the issues that we - would have on the machine. This error may not be related to Upgrade only. It - could be due to any programs; device drivers etc. There is no specific - resolution for this error

-
-

0x8007007e

-
-

The - error indicates one of the modules required to upgrade to Windows 10 was not - found, some of these modules could be manifest files, COM Classes, DLL or any - app packages that may be missing.

-
-

When - we start the upgrade of the OS, the Setup engine is responsible to check and - confirm that all OS components / modules are running in good health, so that - the upgrade succeeds. When we have any issues being reported - with manifest files, COM Classes, DLL or any app packages, the setup - engine would give this error. In order to fix this error, we would suggest to - follow the solutions as below and then start the upgrade again.
-
- Solution 1: System File Checker
- Follow the detailed steps as in: - https://support.microsoft.com/en-us/kb/929833
-
- Solution 2: Integrated CHKSUR
- Run DISM Command to verify the health of the system:
- 1. Go to Start
- 2. Search for ""Command Prompt""
- 3. Right Click and select ""Run as Administrator""
- 4. On the prompt type command: Dism /Online /Cleanup-Image /CheckHealth
- 5. Hit Enter.
- 6. When you use the /CheckHealth argument, the DISM tool will report whether - the image is healthy, repairable, or non-repairable. If the image is - non-repairable, you should discard the image and start again.
- 7. If the image is repairable, you can use the /RestoreHealth argument to - repair the image. Dism /Online /Cleanup-Image /RestoreHealth.

-
-

0x8007025D - - 0x2000C

-
-

This - error occurs if the ISO file's metadata is corrupt.

-
-

Re-download - the ISO/Media and re-attempt the upgrade.
-
- You may alternatively, re-create installation media using "Media - Creation Tool" Refer: https://www.microsoft.com/en-us/software-download/windows10
-
- You can either create a USB drive or an ISO using the Media Creation Tool.

-
-

0x8007045d

-
-

This - error indicates that we ran into an I/O device error.

-
-

Please - ensure that all I/O devices are working correctly. Please review the Device - Manager for any errors and troubleshoot accordingly.
- Refer: - https://msdn.microsoft.com/windows/hardware/drivers/install/troubleshooting-device-and-driver-installations
-
- Additionally, you can review the following logs to verify which I/O device is - causing the problem.
-  "%systemroot%\$Windows.~BT\Sources\Panther\setupact.log"
-
- If unable to review the logs, post on Windows 10 TechNet Forum - (https://social.technet.microsoft.com/Forums/en-us/home?forum=win10itprogeneral&filter=alltypes&sort=lastpostdesc)

-
-

0x80070490 - - 0x20007

-
-

The - error comes up during driver installation phase and it means that some - of the device driver is incompatible.

-
-

Please - ensure that all the devices are working correctly. Please review the Device - Manager for any errors and troubleshoot accordingly.
- Refer: - https://msdn.microsoft.com/windows/hardware/drivers/install/troubleshooting-device-and-driver-installations
-
- Additionally, you can review the following logs to verify which I/O device is - causing the problem.
-  "%systemroot%\$Windows.~BT\Sources\Panther\setupact.log"
-
- If unable to review the logs, post on Windows 10 TechNet Forum - (https://social.technet.microsoft.com/Forums/en-us/home?forum=win10itprogeneral&filter=alltypes&sort=lastpostdesc)

-
-

0x80070542

-
-

The - user executing the Setup.exe does not have all permissions required to - complete the upgrade. 

-
-

Please - ensure the user performing the upgrade is part of Local Administrators group - or is a Local Admin.
-
- Additionally, to troubleshoot further you may need to identify which process - is preventing access to certain resources required for upgrade process. That - can be identify by using Process Monitor - (https://technet.microsoft.com/en-us/sysinternals/processmonitor).
- Use this (https://support.microsoft.com/en-us/kb/939896) to understand how to - use Process Monitor and then post the results to Windows 10 TechNet - Forum - (https://social.technet.microsoft.com/Forums/en-us/home?forum=win10itprogeneral&filter=alltypes&sort=lastpostdesc)

-
-

0x80070652 -

-
-

This - error occurs when another program is being installed at the same time as the - upgrade.

-
-

Ensure - that the are no other installation currently in progress. If there is, wait - for the installation to complete. Restart the computer and do the upgrade to - Windows 10.

-
-

0x800F0923

-
-

This - error code indicates that the user entered Safe Mode during the upgrade - process.

-
-

In - order to complete the upgrade successfully, we recommend that you reboot the - system in normal mode. If a roll-back occurs, re-initiate the upgrade.

-
-

0x80200056

-
-

This - error indicates when the upgrade attempts to use a security token for some of - the operations, but the token is not currently available.

-
-

You - can attempt to re-login to the machine with a local administrator privileges - and attempt to re-run the upgrade. Ensure that you do not logoff until the - upgrade is complete.

-
-

0xC0000005

-
-

The - error indicates that the setup process lead to an access violation

-
-

Please - ensure the user performing the upgrade is part of Local Administrators group - or is a Local Admin.
-
- Additionally, to troubleshoot further you may need to identify which process - is preventing access to certain resources required for upgrade process. That - can be identify by using Process Monitor - (https://technet.microsoft.com/en-us/sysinternals/processmonitor).
- Use this (https://support.microsoft.com/en-us/kb/939896) to understand how to - use Process Monitor and then post the results to Windows 10 TechNet - Forum - (https://social.technet.microsoft.com/Forums/en-us/home?forum=win10itprogeneral&filter=alltypes&sort=lastpostdesc)

-
-

0XC0000428

-
-

This - error occurs when the digital signatures for one of the Boot Critical Drivers - has not been verified.
-
- In most cases, we will see an error on Bootup which will be similar to as - below:
- File: \Windows\system32\boot\winload.exe
- Status:0xc0000428
- Info: Windows cannot verify the digital signature for this file.

-
-

In - order to fix this error, we need to look for the file that is causing the - issue. The file listed in the cause section may vary as well. When this - error occurs, the machine / device will show a bluescreen and will not be in - a useable state. At this point, we would need to perform Automatic - Repair using Windows 10 installation media. The Drivers, conflicts with other - programs, malware, and memory can all cause startup problems.
- Automatic repair can detect and fix problems that prevent your PC from - starting. Refer to the steps:
-
- a. Insert the installation USB media and boot Windows Technical Preview from - it.
- b. In the ‘Windows setup’ page select the ‘language to install’, ‘Time and - currency format’ and the ‘keyboard or input method’ and click on ‘next’.
- c. Click on ‘Repair your computer’ and select ‘Troubleshoot’.
- d. Select ‘Automatic Repair’ and select the operating system.
- e. You will then see a blue screen and an option to choose. Choose the option - Troubleshoot and select advanced options.
-  f. You may choose Automatic Repair from Advanced boot option.
-  g. Follow the instructions.
-
- The above steps should fix the issue and get the driver signatures back as - well for the corrupted drivers. If that does not help, then we may not have - any other option than performing a Clean Install of Windows 10 on the machine - / device. You can create a Windows 10 installation Disc and perform a - clean installation on the computer. To create a please find the below link:
- https://www.microsoft.com/en-us/software-download/windows10
-
- Once the media is created by the tool, it will walk you through how to set up - Windows 10 on your PC. During setup, you might be asked to enter a product - key.
-  If you bought Windows 10 and are installing it for the first time, you’ll - need to enter the Windows 10 product key you received in the confirmation - email after your purchase. If you don’t have a product key and you’ve not - previously upgraded to Windows 10, select I need to buy a Windows 10 product - key.

-
-

0xC1900101 - - 0x2000B

-
-

This - error occurs when the device drivers of the hardware connected to the - computer prevent the Windows 10 upgrade from building the migration file - list.

-
-

We - recommended you disconnect the devices that aren't in use when you upgrade - the computer.

-
-

0xC1900101 - - 0x2000c

-
-

The - Setup Platform has encountered an unspecified error during the WINPE Phase. - This is generally caused by drivers which are not updated at the time when - the upgrade was started.

-
-

It - is recommended to select "Download and install updates - (recommended)" during the upgrade process. Additionally, you can contact - the Hardware Vendor and get the updates for the device drivers that - are connected to the system. Ensure all the devices other than the - Mouse; Keyboard and Display are disconnected during upgrade process. Then - start setup again.

-
-

0xC1900101 - - 0x40001

-
-

This - error indicates that we saw an error in the OOBE Phase - Stop 9F.
- This behavior occurs when device drivers do not handle power state transition - requests properly. The error message most often occurs during one of the - following actions:
- 1. Shutting down
- 2. Suspending or resuming from Standby mode
- 3. Suspending or resuming from Hibernate mode

-
-

The - most common causes for this error would be the connected devices on the - machine / device as below and it would have suggested that we disable / - disconnect them from the device /machine before performing the upgrade:
- 1. Internal WIFI Modem
- 2. Any External connected USB devices such as WEBCAMS; Printers; USB Hard - Drives
- 3. Check to be sure your computer and all devices are on the Hardware - Compatibility List (HCL) and have WHQL signed and certified drivers.
-
- The setup.exe will perform a rollback of the OS and would return to the older - OS. Once the rollback is complete if we find the problem causing driver than - we need to check for %SystemDrive%\$Windows.~bt\sources\Rollback\setupmem.dmp - file and have a Microsoft Support Professional look into the same.

-
-

0xC1900101 - - 0x4001E

-
-

This - error indicates that the installation failed in the SECOND_BOOT phase with an - error during PRE_OOBE operation.

-
-

This - is a generic error that occurs during the OOBE phase of Setup. We recommend - you to review the FAQ for Upgrade to Windows 10 - (https://support.microsoft.com/en-us/help/12435/windows-10-upgrade-faq)

-
-

0xc1900106

-
-

This - indicate that upgrade process was forcefully terminated either by Rebooting - or forcefully canceling the setup. 

-
-

We - recommended that when the Windows 10 Upgrade is initiated, one should not - terminate the process at any time until the Setup completes. Before initiating - the setup, we should make sure:
- 1. The device (Laptop or Surface) it should be connected to power source and adequately - charged.
- 2. The user is not cancelling the setup on the Black Screen, when the - setup.exe is installing devices and configuring user settings.
- PS: It takes time on the device configuration and migration depending upon - the Speed of the CPU and the amount of RAM on the system. 

-
-

0xC1900200 - - 0x20008

-
-

This - error occurs when the computer doesn’t meet the minimum requirements to - download or upgrade to Windows 10.

-
-

Refer - http://www.microsoft.com/en-us/windows/windows-10-specifications?OCID=win10_null_vanity_win10specs - and make sure that the machine, on which the upgrade is being initiated, - meets the minimum requirement.
-
- Secondly use the Windows 10 Compatibility Reports to understand upgrade - issues (https://blogs.technet.microsoft.com/askcore/2016/01/21/using-the-windows-10-compatibility-reports-to-understand-upgrade-issues/)

-
-

0xC1900208 - -1047526904

-
-

This - error occurs when the computer does not pass the compatibility check for - upgrading to Windows 10.

-
-

This - error comes when there is software/driver which is not yet certified to be compatible - with windows 10. Hence you might want to re-run the compatibility check - before initiating the Upgrade.
- Refer AskCore Blog: Using the Windows 10 Compatibility Reports to understand - upgrade issues - (https://blogs.technet.microsoft.com/askcore/2016/01/21/using-the-windows-10-compatibility-reports-to-understand-upgrade-issues/)
-
- Once you have found the in-compatible software/drivers:
- 1. Uninstall incompatible software or hardware or driver,
- 2. Now re-run the compatibility check just to verify that there no more - in-compatible software/driver on the machine.
- 3. If it comes clean, initiate the upgrade.
- 4. Else, repeat the steps until the compatibility check is clean.

-
-

0xC190020e
- 0x80070070 - 0x50011
- 0x80070070 - 0x50012
- 0x80070070 - 0x60000

-
-

These - errors would occur if your computer doesn’t have enough free space available - to install the upgrade.

-
-

Typically - to upgrade to Windows 10, you need free space of 16 GB for 32-bit OS and 20 - GB for 64-bit OS. If there is not enough space refer the following article:
- https://support.microsoft.com/en-us/help/17421/windows-free-up-drive-space
-  
- Note: Once the deletion is complete, initiate the upgrade and this time you - should not receive the error if sufficient space has been made. If that is - not enough
- then, you can implement solution as mentioned below.
-  
- Using External Drive
- If your device allows it, you can use an external USB drive for the - upgrade process. Windows setup will backup the previous version of Windows to - a USB external drive. The external drive must be at least 8GB – but having - 16GB is recommended. 
- Some important points to remember if you choose to use an external storage - drive for installing Windows 10:
-  - We recommend that the external drive is formatted in NTFS.  Drives - that are formatted in FAT32 may run into errors due to FAT32 file size - limitations.  To learn   how to format in NTFS, click here.
- - USB drives are preferred over SD cards because drivers for SD cards are not - migrated if the device does not support Connected Standby.

-
-

Couldn't - Update System Reserved Partition

-
-

This - error occurs because the System Reserved Partition (SRP) is full.

-
-

Free - up 15MB of space on the SRP using the appropriate method described in - Knowledge Base article 3086249, and then try the upgrade again.

-
-

MismatchedLanguage, - found HardBlock

-
-

This - error code indicates that the Current Language installed on the machine is - not Supported for the Upgrade to start.

-
-

We - need to have English as the base Language in order to upgrade to Windows 10. - There is a Hard block for the Upgrade to be performed and the compatibility - scan data is saved to - %Systemroot%\$WINDOWS.~BT\Sources\Panther\CompatData_YYYY.txt

-
-

Setup - couldn’t start properly. Please reboot your PC and try running Windows 10 - Setup again

-
-

This - error occurs if the upgrade files are corrupt due to a failed Windows 10 - download.

-
-

The - Setup.exe initializes the temporary folders to copy the data and prepare the - machine for upgrade. The specific folders that are initialized are:
-
- 1. C:\$Windows ~BT (Hidden Folder)
- 2. C:\$Windows~WS (Hidden Folder)
-
- In order to delete the above folders we would suggest that we use the Disk - Clean Up tool and delete the folders and then try to run the upgrade again.
- https://support.microsoft.com/en-us/help/17421/windows-free-up-drive-space 

-
-

Unable - to resurrect NewSystem object. hr=0x80070002

-
-

This - error occurs when the setup.exe is unable to create the newsystem data file - when the upgrade starts.
- If we look at the C:\$Windows.~BT\Sources\Panther\diagerr.xml, we should see - something like:
- CSetupPlatform::ResurrectNewSystem:
- Failure: Win32Exception: \\?\C:\$Windows.~BT\Sources\NewSystem.dat:
- The system cannot find the file specified. [0x00000002] __cdecl    
- UnBCL::FileStream::FileStream(const class UnBCL::String *,enum
- UnBCL::FileMode,enum UnBCL::FileAccess,enum UnBCL::FileShare,unsigned long)
-  

-
-

The - NewSystem.dat is an operational file that is created at the beginning of the - upgrade process and used at various points in the setup phase like driver - migrations; disk space detections; Platforms detections and creating a base - image of the new OS that is extracted from the INSTALL.WIM, which is the - source file for the upgrade.
- There are couple of solutions for this issue:
- Solution 1: Disk Space
- Check and Make sure that we have good amount of free disk space on the OS - partition. Disk space requirements:
- a. For 32-bit: Greater than 16gb
- b. For 64-Bit: Greater than 20gb
-
- Solution 2: Upgrade Path
- We need to make sure that we are upgrading the existing OS, to the New - Version as per the guidelines described in - https://technet.microsoft.com/en-us/itpro/windows/deploy/windows-10-upgrade-paths?f=255&MSPPError=-2147217396
-
- Solution: Media Creation Tool
- Use the Media Creation tool and create an ISO and then start the upgrade of - the OS. The tool can be downloaded from: - http://go.microsoft.com/fwlink/?LinkId=691209

-
+ Error Codes Cause Mitigation + 0x80070003- 0x20007 This error occurs when there is problem with the Internet connection during the Windows 10 upgrade. "Since this error indicates that the internet connection ran into a problem, you may attempt to fix the connectivity issues and reattempt the download of the files. +Alternatively, you may re-create installation media using ""Media Creation Tool"" from a different connected system. Refer: https://www.microsoft.com/en-us/software-download/windows10 -

 

+You can either create a USB drive or an ISO. +" + 0x8007025D - 0x2000C This error occurs if the ISO file's metadata is corrupt. "Re-download the ISO/Media and re-attempt the upgrade. -

 

+You may alternatively, re-create installation media using ""Media Creation Tool"" Refer: https://www.microsoft.com/en-us/software-download/windows10 - +You can either create a USB drive or an ISO using the Media Creation Tool. +" + 0x80070490 - 0x20007 The error comes up during driver installation phase and it means that some of the device driver is incompatible. "Please ensure that all the devices are working correctly. Please review the Device Manager for any errors and troubleshoot accordingly. +Refer: https://msdn.microsoft.com/windows/hardware/drivers/install/troubleshooting-device-and-driver-installations - +Additionally, you can review the following logs to verify which I/O device is causing the problem. + ""%systemroot%\$Windows.~BT\Sources\Panther\setupact.log"" - +If unable to review the logs, post on Windows 10 TechNet Forum (https://social.technet.microsoft.com/Forums/en-us/home?forum=win10itprogeneral&filter=alltypes&sort=lastpostdesc) +" + 0xC1900101 - 0x2000B This error occurs when the device drivers of the hardware connected to the computer prevent the Windows 10 upgrade from building the migration file list. We recommended you disconnect the devices that aren't in use when you upgrade the computer. + 0xC1900101 - 0x2000c The Setup Platform has encountered an unspecified error during the WINPE Phase. This is generally caused by drivers which are not updated at the time when the upgrade was started. It is recommended to select "Download and install updates (recommended)" during the upgrade process. Additionally, you can contact the Hardware Vendor and get the updates for the device drivers that are connected to the system. Ensure all the devices other than the Mouse; Keyboard and Display are disconnected during upgrade process. Then start setup again. + 0xC1900200 - 0x20008 This error occurs when the computer doesn’t meet the minimum requirements to download or upgrade to Windows 10. "Refer http://www.microsoft.com/en-us/windows/windows-10-specifications?OCID=win10_null_vanity_win10specs and make sure that the machine, on which the upgrade is being initiated, meets the minimum requirement. + +Secondly use the Windows 10 Compatibility Reports to understand upgrade issues (https://blogs.technet.microsoft.com/askcore/2016/01/21/using-the-windows-10-compatibility-reports-to-understand-upgrade-issues/) +" + 0x80070004 - 0x3000D SYSTEM, LOCAL, SELF, System, and Network are reserved names that can’t be used for Computer Name. "Ensure that you do not use the reserved names as the Computer names. Rename the system to a valid Computer name. +See KB 3086101 for more details. +" + 0xC1900101 - 0x40001 "This error indicates that we saw an error in the OOBE Phase - Stop 9F. This behavior occurs when device drivers do not handle power state transition requests properly. The error message most often occurs during one of the following actions: 1. Shutting down +2. Suspending or resuming from Standby mode +3. Suspending or resuming from Hibernate mode" "The most common causes for this error would be the connected devices on the machine / device as below and it would have suggested that we disable / disconnect them from the device /machine before performing the upgrade: +1. Internal WIFI Modem +2. Any External connected USB devices such as WEBCAMS; Printers; USB Hard Drives +3. Check to be sure your computer and all devices are on the Hardware Compatibility List (HCL) and have WHQL signed and certified drivers. + +The setup.exe will perform a rollback of the OS and would return to the older OS. Once the rollback is complete if we find the problem causing driver than we need to check for %SystemDrive%\$Windows.~bt\sources\Rollback\setupmem.dmp file and have a Microsoft Support Professional look into the same. +" + 0xC1900101 - 0x4001E This error indicates that the installation failed in the SECOND_BOOT phase with an error during PRE_OOBE operation. This is a generic error that occurs during the OOBE phase of Setup. We recommend you to review the FAQ for Upgrade to Windows 10 (https://support.microsoft.com/en-us/help/12435/windows-10-upgrade-faq) + 0x80070005 - 0x4000D This error code means The installation failed in the SECOND_BOOT phase with an error in during MIGRATE_DATA operation. This issue may occur if we have any application / driver that is causing an issue while the upgrade to Windows 10 is going on. Preform a clean boot on the system. Refer https://support.microsoft.com/en-us/kb/929135 for steps to perform a Clean boot. + 0x80070004 - 0x50012 The Computer account for the system has an invalid name. Please ensure that the machine name does not have any invalid characters (See https://technet.microsoft.com/en-us/library/cc749460(v=ws.10).aspx). Additionally, the names should not be any of the reserved names for systems. Rename the system to a valid computer name and try the Setup again. See KB 3086101 for more details. + "0xC190020e 0x80070070 - 0x50011 +0x80070070 - 0x50012 +0x80070070 - 0x60000" These errors would occur if your computer doesn’t have enough free space available to install the upgrade. "Typically to upgrade to Windows 10, you need free space of 16 GB for 32-bit OS and 20 GB for 64-bit OS. If there is not enough space refer the following article: +https://support.microsoft.com/en-us/help/17421/windows-free-up-drive-space + +Note: Once the deletion is complete, initiate the upgrade and this time you should not receive the error if sufficient space has been made. If that is not enough +then, you can implement solution as mentioned below. + +Using External Drive +If your device allows it, you can use an external USB drive for the upgrade process. Windows setup will backup the previous version of Windows to a USB external drive. The external drive must be at least 8GB – but having 16GB is recommended. +Some important points to remember if you choose to use an external storage drive for installing Windows 10: + - We recommend that the external drive is formatted in NTFS. Drives that are formatted in FAT32 may run into errors due to FAT32 file size limitations. To learn how to format in NTFS, click here. +- USB drives are preferred over SD cards because drivers for SD cards are not migrated if the device does not support Connected Standby. +" + + + + +## Appendix B: Less common errors I haven't edited and don't know how to classify + + + + + + + + + + + + + + + + + + + + + + + + + +
Error Codes Cause Mitigation
Contact your system administrator to upgrade Windows Server or Enterprise Editions This issue occurs if you run the updater tool. The tool works only with the Windows 10 Home, Pro, and Education editions. To resolve this issue, use a different method to upgrade to Windows 10 version 1607. For example, download the ISO, and then run Setup from it.
When doing an upgrade to Windows Version 1607 is it supported to use a custom install.wim (sysprepped) instead of the default install.wim that comes with Windows Version 1607 Unsupported It is not supported to replace the install.wim with custom wim (sysprepped or not). It is supported to do some minor changes to the default install.wim such as injecting latest cumulative update or remove inbox apps.
0xC1420127 The typical conversion of the error means that the specified image in the specified wim is already mounted for read/write access. When we launch the setup.exe, it checks the registry key. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WIMMount\Mounted Images to check for any previously mounted WIM files on the system and if the image is mounted we will get this error. This error would be very rare on Upgrades of WIN10 specially when upgrading to the Anniversary 1607 Build. This issue has been fixed with the Cumulative updates released in June 2016 for Windows 10. When we perform an Upgrade, it is recommended to Perform a Windows Update first and apply all important updates on the current OS and then start the Upgrade process for Windows 10.
0x8004100E This error code indicates that there is a problem with an Application that has an Invalid WMI Namespace In order to fix this problem, we need to open Application Event log and Check for Errors for various applications that could be causing this error. You can use WMIDIAG tool and make sure that the WMI is working well. The step by step instructions are available at: https://technet.microsoft.com/en-us/library/ff404265.aspx
0x80070057 This error means that One or more arguments are invalid This is a very generic error, and it could be due to any of the issues that we would have on the machine. This error may not be related to Upgrade only. It could be due to any programs; device drivers etc. There is no specific resolution for this error
0x8007007e The error indicates one of the modules required to upgrade to Windows 10 was not found, some of these modules could be manifest files, COM Classes, DLL or any app packages that may be missing. "When we start the upgrade of the OS, the Setup engine is responsible to check and confirm that all OS components / modules are running in good health, so that the upgrade succeeds. When we have any issues being reported with manifest files, COM Classes, DLL or any app packages, the setup engine would give this error. In order to fix this error, we would suggest to follow the solutions as below and then start the upgrade again. + +Solution 1: System File Checker +Follow the detailed steps as in: https://support.microsoft.com/en-us/kb/929833 + +Solution 2: Integrated CHKSUR +Run DISM Command to verify the health of the system: +1. Go to Start +2. Search for """"Command Prompt"""" +3. Right Click and select """"Run as Administrator"""" +4. On the prompt type command: Dism /Online /Cleanup-Image /CheckHealth +5. Hit Enter. +6. When you use the /CheckHealth argument, the DISM tool will report whether the image is healthy, repairable, or non-repairable. If the image is non-repairable, you should discard the image and start again. +7. If the image is repairable, you can use the /RestoreHealth argument to repair the image. Dism /Online /Cleanup-Image /RestoreHealth. +"
0x8007045d This error indicates that we ran into an I/O device error. "Please ensure that all I/O devices are working correctly. Please review the Device Manager for any errors and troubleshoot accordingly. +Refer: https://msdn.microsoft.com/windows/hardware/drivers/install/troubleshooting-device-and-driver-installations + +Additionally, you can review the following logs to verify which I/O device is causing the problem. + ""%systemroot%\$Windows.~BT\Sources\Panther\setupact.log"" + +If unable to review the logs, post on Windows 10 TechNet Forum (https://social.technet.microsoft.com/Forums/en-us/home?forum=win10itprogeneral&filter=alltypes&sort=lastpostdesc) +"
0x80070542 The user executing the Setup.exe does not have all permissions required to complete the upgrade. "Please ensure the user performing the upgrade is part of Local Administrators group or is a Local Admin. + +Additionally, to troubleshoot further you may need to identify which process is preventing access to certain resources required for upgrade process. That can be identify by using Process Monitor (https://technet.microsoft.com/en-us/sysinternals/processmonitor). +Use this (https://support.microsoft.com/en-us/kb/939896) to understand how to use Process Monitor and then post the results to Windows 10 TechNet Forum (https://social.technet.microsoft.com/Forums/en-us/home?forum=win10itprogeneral&filter=alltypes&sort=lastpostdesc) +"
0x80070652 This error occurs when another program is being installed at the same time as the upgrade. Ensure that the are no other installation currently in progress. If there is, wait for the installation to complete. Restart the computer and do the upgrade to Windows 10.
0x800F0923 This error code indicates that the user entered Safe Mode during the upgrade process. In order to complete the upgrade successfully, we recommend that you reboot the system in normal mode. If a roll-back occurs, re-initiate the upgrade.
0x80200056 This error indicates when the upgrade attempts to use a security token for some of the operations, but the token is not currently available. You can attempt to re-login to the machine with a local administrator privileges and attempt to re-run the upgrade. Ensure that you do not logoff until the upgrade is complete.
0xC0000005 The error indicates that the setup process lead to an access violation "Please ensure the user performing the upgrade is part of Local Administrators group or is a Local Admin. + +Additionally, to troubleshoot further you may need to identify which process is preventing access to certain resources required for upgrade process. That can be identify by using Process Monitor (https://technet.microsoft.com/en-us/sysinternals/processmonitor). +Use this (https://support.microsoft.com/en-us/kb/939896) to understand how to use Process Monitor and then post the results to Windows 10 TechNet Forum (https://social.technet.microsoft.com/Forums/en-us/home?forum=win10itprogeneral&filter=alltypes&sort=lastpostdesc) +"
0XC0000428 "This error occurs when the digital signatures for one of the Boot Critical Drivers has not been verified. In most cases, we will see an error on Bootup which will be similar to as below: +File: \Windows\system32\boot\winload.exe +Status:0xc0000428 +Info: Windows cannot verify the digital signature for this file." "In order to fix this error, we need to look for the file that is causing the issue. The file listed in the cause section may vary as well. When this error occurs, the machine / device will show a bluescreen and will not be in a useable state. At this point, we would need to perform Automatic Repair using Windows 10 installation media. The Drivers, conflicts with other programs, malware, and memory can all cause startup problems. +Automatic repair can detect and fix problems that prevent your PC from starting. Refer to the steps: + +a. Insert the installation USB media and boot Windows Technical Preview from it. +b. In the ‘Windows setup’ page select the ‘language to install’, ‘Time and currency format’ and the ‘keyboard or input method’ and click on ‘next’. +c. Click on ‘Repair your computer’ and select ‘Troubleshoot’. +d. Select ‘Automatic Repair’ and select the operating system. +e. You will then see a blue screen and an option to choose. Choose the option Troubleshoot and select advanced options. + f. You may choose Automatic Repair from Advanced boot option. + g. Follow the instructions. + +The above steps should fix the issue and get the driver signatures back as well for the corrupted drivers. If that does not help, then we may not have any other option than performing a Clean Install of Windows 10 on the machine / device. You can create a Windows 10 installation Disc and perform a clean installation on the computer. To create a please find the below link: +https://www.microsoft.com/en-us/software-download/windows10 + +Once the media is created by the tool, it will walk you through how to set up Windows 10 on your PC. During setup, you might be asked to enter a product key. + If you bought Windows 10 and are installing it for the first time, you’ll need to enter the Windows 10 product key you received in the confirmation email after your purchase. If you don’t have a product key and you’ve not previously upgraded to Windows 10, select I need to buy a Windows 10 product key. +"
0xc1900106 This indicate that upgrade process was forcefully terminated either by Rebooting or forcefully canceling the setup. "We recommended that when the Windows 10 Upgrade is initiated, one should not terminate the process at any time until the Setup completes. Before initiating the setup, we should make sure: +1. The device (Laptop or Surface) it should be connected to power source and adequately charged. +2. The user is not cancelling the setup on the Black Screen, when the setup.exe is installing devices and configuring user settings. +PS: It takes time on the device configuration and migration depending upon the Speed of the CPU and the amount of RAM on the system. +"
0xC1900208 -1047526904 This error occurs when the computer does not pass the compatibility check for upgrading to Windows 10. "This error comes when there is software/driver which is not yet certified to be compatible with windows 10. Hence you might want to re-run the compatibility check before initiating the Upgrade. +Refer AskCore Blog: Using the Windows 10 Compatibility Reports to understand upgrade issues (https://blogs.technet.microsoft.com/askcore/2016/01/21/using-the-windows-10-compatibility-reports-to-understand-upgrade-issues/) + +Once you have found the in-compatible software/drivers: +1. Uninstall incompatible software or hardware or driver, +2. Now re-run the compatibility check just to verify that there no more in-compatible software/driver on the machine. +3. If it comes clean, initiate the upgrade. +4. Else, repeat the steps until the compatibility check is clean. +"
Couldn't Update System Reserved Partition This error occurs because the System Reserved Partition (SRP) is full. Free up 15MB of space on the SRP using the appropriate method described in Knowledge Base article 3086249, and then try the upgrade again.
MismatchedLanguage, found HardBlock This error code indicates that the Current Language installed on the machine is not Supported for the Upgrade to start. We need to have English as the base Language in order to upgrade to Windows 10. There is a Hard block for the Upgrade to be performed and the compatibility scan data is saved to %Systemroot%\$WINDOWS.~BT\Sources\Panther\CompatData_YYYY.txt
Setup couldn’t start properly. Please reboot your PC and try running Windows 10 Setup again This error occurs if the upgrade files are corrupt due to a failed Windows 10 download. "The Setup.exe initializes the temporary folders to copy the data and prepare the machine for upgrade. The specific folders that are initialized are: + +1. C:\$Windows ~BT (Hidden Folder) +2. C:\$Windows~WS (Hidden Folder) + +In order to delete the above folders we would suggest that we use the Disk Clean Up tool and delete the folders and then try to run the upgrade again. +https://support.microsoft.com/en-us/help/17421/windows-free-up-drive-space +"
Unable to resurrect NewSystem object. hr=0x80070002 "This error occurs when the setup.exe is unable to create the newsystem data file when the upgrade starts. If we look at the C:\$Windows.~BT\Sources\Panther\diagerr.xml, we should see something like: +CSetupPlatform::ResurrectNewSystem: +Failure: Win32Exception: \\?\C:\$Windows.~BT\Sources\NewSystem.dat: +The system cannot find the file specified. [0x00000002] __cdecl +UnBCL::FileStream::FileStream(const class UnBCL::String *,enum +UnBCL::FileMode,enum UnBCL::FileAccess,enum UnBCL::FileShare,unsigned long)" "The NewSystem.dat is an operational file that is created at the beginning of the upgrade process and used at various points in the setup phase like driver migrations; disk space detections; Platforms detections and creating a base image of the new OS that is extracted from the INSTALL.WIM, which is the source file for the upgrade. +There are couple of solutions for this issue: +Solution 1: Disk Space +Check and Make sure that we have good amount of free disk space on the OS partition. Disk space requirements: +a. For 32-bit: Greater than 16gb +b. For 64-Bit: Greater than 20gb + +Solution 2: Upgrade Path +We need to make sure that we are upgrading the existing OS, to the New Version as per the guidelines described in https://technet.microsoft.com/en-us/itpro/windows/deploy/windows-10-upgrade-paths?f=255&MSPPError=-2147217396 + +Solution: Media Creation Tool +Use the Media Creation tool and create an ISO and then start the upgrade of the OS. The tool can be downloaded from: http://go.microsoft.com/fwlink/?LinkId=691209 +"
+ ## Related topics • Windows 10 FAQ for IT professionals