• July 17, 2017
    Announcement: New site design for Microsoft Community

    In July, Microsoft will roll out the first of ongoing site improvements aimed to modernize Microsoft Community and help customers get the most out of their community experience.

    • During the roll out period, you may see the old or new site design depending on your location

    • We expect the roll out to finish by 31 July

    Note: Past private message conversations will not move to the new site design. Please save any private messages you would like to keep.

     Learn more about the upcoming site improvements in this thread.

    Thank you for being part of Microsoft Community!

 
Question
10311 views

Error when upgrading to Windows 10: 0xC1900101 – 0x20017

Scott Atk asked on

When I try to upgrade to Windows 10, the installation fails and rolls back to my previous operating system with the error:

 

We couldn’t install Windows 10.

We’ve set your PC back to the way it was right before you started installing Windows 10.

 

0xC1900101 - 0x20017

The installation failed in SAFE_OS phase with an error during BOOT operation

232 people had this question

Abuse history


The answered status icon Answer
PaulSey... replied on

Hello,

Microsoft is aware some customers are unable to install Windows 10 due to error 0xC1900101 - 0x20017. 

This error indicates a failure to boot Windows 10 occurred during the initial reboot of the upgrade, causing the system to roll back. The most likely causes of this error are:

  • Incompatible antivirus or other security program or utility software

  • Incompatible driver or hardware

In either case, the incompatible program or driver’s defect prevents booting to the intermediary environment necessary to perform upgrade actions. Unfortunately, due to the timing of this failure, there are often no logs, crash dumps or other diagnostic information available to investigate the issue easily, which makes it difficult to determine which, if any, of the drivers or system components are causing the upgrade to fail.

We are currently working with our partner companies to help update problematic drivers whenever they are identified. 

Some basic steps to try if you receive this error:

  • Try temporarily disabling or uninstalling your antivirus software and see if the upgrade will succeed. 

  • Remove any connected USB devices (except the keyboard and mouse) when attempting the upgrade.

  • Make sure you’ve installed all the latest Windows Updates and latest drivers and updates from your hardware and software manufacturers, and uninstall any unnecessary hardware or software prior to upgrading to Windows 10. 

  • Make sure you are not running any drive-encryption software.  If so, you must decrypt your drive before upgrading to Windows 10.

  • Try uninstalling your display adapter driver prior to the upgrade.

For some specific examples that have resolved some customers issues:

  • Customers running Gigabyte motherboards that support the Intel Pentium CPU G3258 processor have had success after installing a BIOS update from the manufacturer to support both processor cores in Windows 10. 

  • Customers running Samsung RF and RV series laptops have had success after temporarily replacing the Wi-Fi Broadband card prior to the upgrade.

We understand that the inability to easily identify the incompatible driver can be incredibly frustrating and we are sorry for the inconvenience.

If you’ve tried all of these steps and are still experiencing this error when upgrading, we can use your help in identifying which hardware or software may be incompatible with Windows 10.  The following hidden log files may offer some insight:

$Windows.~BT\sources\Panther
$Windows.~BT\sources\Rollback
  

We’d also like to gather MSINFO files from customers experiencing this issue.  (To save this file, run msinfo32.exe, and click File and Save and choose a name for the file.)

If you are willing to share these log files with an agent, please post a response in this thread, identifying your issue, and that you have the necessary logs.  A Microsoft agent may send you a private message.  If you receive a private message, check to make sure that the person contacting you has a Microsoft badge in their name.

With your help, hopefully we can more quickly identify the most common culprits and work with our partners to improve compatibility with Windows 10.

Thank you!

35 people found this helpful

Abuse history


progress