If you’re trying to upgrade your Windows 10 to the next version and you see a message – Error 0xC1900101 – 0x20017, the installation failed in the SAFE_OS phase with an error during BOOT operation, this post can help.
0xC1900101 is a frequently observed code that occurs at any stage of the upgrade process; It is also called generic restore code which signals the presence of an incompatible driver. In addition to updating the drivers, it is suggested that you run Windows Installer using a minimal set of drivers and startup programs with a minimal boot before starting the update process. at the level.
Installation failed in SAFE_OS phase with an error during BOOT operation
The failure occurs during an update where the operating system is unable to migrate the driver because it causes an illegal operation. This results in a restoration of the operating system. This is a SafeOS startup failure, usually caused by drivers or non-Microsoft disk encryption software. During the SAFEOS phase, the system checks that everything, including the pilots, behaves as expected. Any unsecured operation or absence of signatures will cause a system stability problem. I have noticed that many times when you force upgrade from an incompatible system, this will result in BSOD.
It is essential that you find the driver that is causing the problem, and it is quite easy.
Windows 10
Go to % windir% Panther directory, then locate and open the Setuperr.log and Setupact.log files. Of the two files, Setupact.log is specifically created if an upgrade fails. You will need to look for a failure reference in the log file and find the driver responsible.
Windows 8 / 8.1 / 7
Microsoft suggests checking the list here where it lists all the log files created during the restore phase. When the installation of the Windows upgrade fails and you have successfully restored the desktop installation of the previous operating system, these files are there to help you resolve the issues.
Fixed Windows 10 installation error 0xC1900101 – 0x20017
There are only two ways to fix it, either update the driver to a compatible version or restore the problematic driver. So you may have done a recent driver update and then tried to upgrade. If so, going back will help you with the upgrade. If the upgrade presents a problem with the existing driver and you are forcing the update, you need to check if the driver has a compatible version.
- Make sure all drivers are updated
- Uninstall problematic drivers
- Upgrade to a minimal boot state.
You will need administrator authorization to do any of these.
1]Make sure all drivers are updated
The first thing to do is to update the drivers to the version compatible with the version you plan to upgrade. Most drivers offer backward compatibility, so this should be a problem unless otherwise noted. If you have updated, be sure to restore the driver to the previous version.
If you are unable to find the latest version of the driver, we suggest using tools such as Double Driver, Driver Doctor, etc.
2]Uninstall problematic drivers
If these are devices without which you can live and replace them with generic drivers, you should do so. I suggest this, keeping in mind that upgrading is essential for you. You can choose to remove the hardware and install it again, and this time uses a different player instead of the one you downloaded.
- Open Device Manager using Win + X followed by M
- Find the hardware that is causing the problem.
- Right click and choose to uninstall the device
- Once deleted, click Action> Check for hardware changes
- The device will be detected and Windows will install the driver.
If Windows installs the same driver, you choose to install a generic driver by following this guide.
3]Upgrade in minimum boot state
When you start the computer at minimal boot, the computer starts using a pre-selected minimum set of drivers and startup programs. Since the drivers will not be loaded, you will be able to upgrade, but be sure to upgrade or restore the driver after everything is done.
If none of these works, it is best to wait for an official solution from Microsoft. Often the problem has no solution because it is not compatible. I remember doing a forced upgrade, and all I got was a green screen of death.
Related readings:
