Site icon Winhelponline

Error 0xC1900101 Installing Windows 10 Feature Update

When you install a Windows 10 feature update (eg., v1809 on a computer running v1803) via Windows Update, the error 0xC1900101 occurs and the installation fails.

Error 0xC1900101 is a rollback code that indicates that an incompatible driver is present on the computer. Microsoft stated in its blog post that the October 2018 update rollout will be done very carefully. If the system finds any outdated drivers or hardware, incompatible applications, the setup won’t proceed.

Quoting Microsoft:

While the April Update had the fastest Windows 10 update rollout velocity, we are taking a more measured approach with the October Update, slowing our rollout to more carefully study device health data. We will offer the October Update to users via Windows Update when data shows your device is ready and you will have a great experience. If we detect that your device may have an issue, such as an application incompatibility, we will not install the update until that issue is resolved.

Error 0xC1900101 Installing Windows 10 Feature Update

To resolve a rollback due to driver conflicts, make sure that your device drivers are updated. Use your OEM’s driver updater utilities to update every device on your computer. OEMs like Dell include the software update and health checkup tool which allows you to download and install the latest device drivers and BIOS updates pertaining to your computer model.


General troubleshooting procedures for error code 0xC1900101

0xC1900101 – 0x20004

Windows Setup encountered an error during the SAFE_OS with the INSTALL_RECOVERY_ENVIRONMENT operation. This is generally caused by out-of-date drivers.

0xC1900101 – 0x2000c

Windows Setup encountered an unspecified error during Wim apply in the WinPE phase. This is generally caused by out-of-date drivers.

0xC1900101 – 0x20017

A driver has caused an illegal operation.  Windows was not able to migrate the driver, resulting in a rollback of the operating system. This is a SafeOS boot failure, typically caused by drivers or non-Microsoft disk encryption software.

0xC1900101 – 0x30018

A device driver has stopped responding to setup.exe during the upgrade process.

0xC1900101 – 0x3000D

Installation failed during the FIRST_BOOT phase while attempting the MIGRATE_DATA operation. This can occur due to a problem with a display driver.

0xC1900101 – 0x4000D

A rollback occurred due to a driver configuration issue. Installation failed during the second boot phase while attempting the MIGRATE_DATA operation. This can occur due to incompatible drivers.

0xC1900101 – 0x40017

Windows 10 upgrade failed after the second reboot. This is usually caused by a faulty driver — e.g., antivirus filter drivers or encryption drivers.

The following logs may have helpful information on which driver or application caused the problem:

 

Exit mobile version