Windows Update

Windows upgrade error 0xC1900101: what it means and how to fix it

Error 0xC1900101 is a rollback code that usually means a driver stopped a Windows upgrade. Read the extended code, update or remove drivers, then try again.

By EpiFive Editorial TeamSources checked How we check our guides

What the error means

0xC1900101 appears when a Windows feature upgrade fails and Windows rolls back to the version you had before. Microsoft's IT pro article calls it "a generic rollback code" that "usually indicates that an incompatible driver is present." It can be raised at almost any stage of the upgrade, and the incompatible driver can cause blue screens, hangs or unexpected restarts during setup. The consumer upgrade page sums it up as "usually a driver error."

The code rarely appears alone. Windows Setup normally adds an extended code after a dash, and that second number is the useful part, because it records the phase in which the failure happened. Microsoft documents these combinations:

  • 0x20004: an error while installing the recovery environment in the SafeOS phase, caused by out-of-date drivers.
  • 0x2000c: an unspecified error while applying the Windows image in the WinPE phase, caused by out-of-date drivers.
  • 0x20017: a driver caused an illegal operation and could not be migrated. It is a SafeOS boot failure, typically from drivers or non-Microsoft disk encryption software, and occasionally hardware.
  • 0x30018: a device driver stopped responding to setup.exe.
  • 0x3000D: installation failed while migrating data at first boot, often from a display driver.
  • 0x4000D: a rollback during the second boot phase from a driver configuration issue.
  • 0x40017: failure after the second restart, caused by a faulty driver such as an antivirus filter or encryption driver.

The broader guide Windows 11 update stuck or failing covers rollback loops in general; the steps below are specific to this code.

Common causes

  • Out-of-date or incompatible drivers, especially network, display and storage drivers.
  • Third-party antivirus or security software with filter drivers.
  • Non-Microsoft disk encryption software.
  • External devices, docks and extra drives connected during the upgrade.
  • Too little free disk space, which Microsoft lists as the first check.

How to fix it

1. Free space and install every pending update

Make sure you have at least 16 GB free for a 32-bit system or 20 GB for a 64-bit system. Then run Windows Update a few times and install everything it offers, including hardware and third-party driver updates. Microsoft lists both as the first steps for any 0xC1900101 error.

2. Unplug extra hardware

Disconnect external storage, docks and anything else that is not needed for basic use. For several extended codes Microsoft says to leave only the mouse, keyboard and display connected.

3. Update or reinstall drivers

Open Device Manager and look for devices with a yellow exclamation mark; right-click each one and update or uninstall the driver. Microsoft's Windows 11 steps single out network and display adapters: expand Network adapters or Display adapters, right-click the adapter and select Uninstall device, then restart. Alternatively select Update driver and then Search automatically for drivers. Get drivers for added hardware from the manufacturer's website.

4. Remove third-party security software for the upgrade

Microsoft says to remove third-party security software before upgrading. Keep your product keys and installers so you can reinstall it afterwards; Windows Defender protects the PC in the meantime.

5. Repair the disk and system files, then do a clean boot

From an elevated Command Prompt, repair disk errors and restore system files. The disk check asks you to restart:

chkdsk /f C:
DISM.exe /Online /Cleanup-image /Restorehealth

Then perform a clean boot, which starts Windows with a minimal set of drivers and startup programs, and run the upgrade again. Microsoft recommends this specifically for rollbacks caused by driver conflicts.

If nothing works

Read the logs to find the driver. Microsoft points to Setuperr.log and Setupact.log in %windir%\Panther, and to the rollback folder $Windows.~bt\Sources\Rollback, which holds setupmem.dmp, event logs and setupapi.dev.log. Its free SetupDiag tool analyzes these files and reports the likely cause. For 0x4000D Microsoft also suggests checking for BIOS updates from your hardware vendor. When you start the upgrade again, accept "Download and install updates (recommended)" so Setup can fetch updated drivers.

What we checked

On 2026-11-19 we read three Microsoft pages that mention 0xC1900101. The Windows 10 upgrade resolution procedures on Microsoft Learn describe it as a generic rollback code that usually means an incompatible driver, list the extended codes with their causes and mitigations, and name the log files. The upgrade and installation errors page on support.microsoft.com gives the consumer steps, from free space to DISM and a clean boot. The Windows Update troubleshooting page lists it as an incompatible driver and gives the Device Manager steps. We read the vendor documentation and did not reproduce the error.

Last checked: 2026-11-19.

Official sources

Questions people ask

What does the number after 0xC1900101 mean?

It is an extended code that tells you the setup phase where the rollback happened. For example, Microsoft says 0x30018 means a device driver stopped responding to setup.exe, and 0x3000D points to a display driver problem during data migration.

Which drivers usually cause 0xC1900101?

Microsoft names out-of-date drivers in general, network and display adapter drivers in its consumer steps, and antivirus filter drivers or non-Microsoft disk encryption software in its IT pro article.

Where are the logs for a 0xC1900101 rollback?

Microsoft points to Setuperr.log and Setupact.log in %windir%\Panther, and to the rollback logs, minidump and setupapi.dev.log under $Windows.~bt\Sources\Rollback. Its free SetupDiag tool can read these for you.

  • 0x800f0922 (Windows Update)

    Error 0x800f0922 means an update could not install, most often because of low disk space, a VPN blocking the update servers or a full System Reserved partition.

  • 0x80070002 (Windows Update)

    Windows Update error 0x80070002 means a file the update needs could not be found. Restart, run the troubleshooter, free space, then repair the update files.

  • 0x8007000d (Windows Update)

    Error 0x8007000d means Windows Update downloaded invalid or corrupted data. Run the troubleshooter, clear the update cache, download again, then repair with DISM.

  • 0x80073712 (Windows Update)

    Error 0x80073712 means the Windows component store is damaged, so a file Windows Update needs is missing. Repair it with DISM and SFC, then update again.

Not your code?

Search the error code library, or report a code we don't cover. Spotted something out of date on this page? Report a correction.