0xC1900101 – 0x20017, Installation failed in SAFE_OS phase

If you try to advance your Windows 11/10 to the next version and see a message – Error 0xC1900101 – 0x20017- the installation failed in the SAFE_OS phase with an error through BOOT operation, then this post will be able to benefit you.

0xC1900101 is a typical experiential code that occurs at any phase of the upgrade procedure; It is also called the standard rollback code that points out the attendance of a mismatched driver. Along with updating the drivers, running Windows Setup using a negligible set of drivers and startup programs is recommended by performing a clean boot before introducing the upgrade procedure.

Installation failed in the SAFE_OS phase with an error during the BOOT operation.

The disappointment happens through an update where OS cannot travel the driver as it causes unlawful operation. Its consequences in a rollback of the functioning system. This is a Safe_OS boot catastrophe, characteristically caused by drivers or non-Microsoft disk encoding software. During the SAFEOS phase, the system confirms that everything, counting drivers, performs as they are projected. Any operation that is not protected or signatures are misplaced will cause a matter regarding system constancy. I have observed that when you force upgrade a mismatched system, it will often result in BSOD.

It is vital that you find the driver causing the error, and it is slightly informal.

Error in Windows 11/10 

Go to %winder%\Panther directory, and then discover the Setuperr.log and Setupact.log files and open them. Amongst the two files, Setupact.log is exactly twisted when an upgrade flops. You will have to look for an orientation for disappointment in the log file and find the driver answerable.

Error in Windows 8/8.1/7

Microsoft proposes looking at the list where it inclines all the log files shaped during the rollback phase. When the Windows upgrade installation flops and you have effectively rolled back the installation to the preceding operating system desktop, these files are here to aid you in troubleshooting.

Fix Windows Setup error 0xC1900101 – 0x20017

There are only two conducts to solve it, update the driver to a well-matched version or roll back the challenging driver. It may occur that you made a fresh update to the drive and then strained to upgrade. If that’s the circumstance, rolling back will aid you in advance. If the upgrade has a matter with the present driver, and you are compelling the update, you should check if the driver has a well-matched version.

  • Guarantee that all the drivers are upgraded
  • Uninstall the problematic drivers
  • Upgrade in Clean Boot State.

You will require admin permission to execute any of these processes.

  1. Ensure that all the drivers are updated

The primary thing you should do is update the drivers with the version which is well-matched with the version you are scheduling to upgrade. Most drivers bid backward compatibility, so that should be a delinquent except mentioned otherwise. In case you have updated, make sure to roll back the driver to the preceding version.

If you cannot find the newest version of the driver, we propose using tools like Double Driver, Driver Doctor, and more.

  1. Uninstall the problematic drivers.

If these are devices that you can move without and substitute with generic drivers, then you should do it. I am telling you this, keeping in mind that the upgrade is vital for you. You can choose to eliminate the hardware and install it over, and this time, you use an alternative drive in its place of the one you copied.

  • Open Device Manager using Win +X followed by M
  • Detect the hardware that is triggering the matter.
  • Right-click and select Uninstall the device
  • Once it is detached, click on Action > Scan for hardware variations
  • The device will be noticed, and Windows will install the driver.

If Windows installs the same driver, you select to install a generic driver by following this director. 

  1. Upgrade in Clean Boot State

When you twitch the computer in the spotless boot, the computer starts by using a pre-selected negligible set of drivers and startup programs. Since the drivers will not be overloaded, you can upgrade, but make sure to upgrade moreover or roll back the driver after everything is ample.

If none of this works, then it’s greatest to wait for an authorized solution from Microsoft. The problem often doesn’t have an explanation because it is not well-matched. I remember performing a forced upgrade, and all I got was a green screen of decease.

How do you fix the installation that failed in the Safe_OS phase with an error during the boot operation?

This can be resolved in two ways; update the driver to a well-matched version or roll back the challenging driver. It typically occurs when you have moreover updated the driver or the OS, and they are not well-matched. Make sure to download the well-matched version with the OS from the OEMs website.

Leave a Comment