Skip to content

Est. 2011·Microsoft Partner ID 7033487·Delivery under 3 min·Support 7 days a week

Your vault is empty.

License Error 0xC1900101 - 0x30018

0xC1900101 – 0x30018 and 0x20017: a driver stops the upgrade at boot

12 min read Updated October 5, 2026 Windows Update & Setup

Recommended fix

Windows 11 Pro Retail license

Original price was: 25,00 €.Current price is: 14,99 €.

Fix It Now

Fix it now

0xC1900101 is the generic rollback result code and the half after the dash says where it happened. Microsoft publishes a cause and a mitigation for three of the four here, and all three say the same thing: a driver. The published first moves are to strip the machine back to keyboard, mouse and display, and to let setup fetch updated drivers.

Run this after a rollback, in an elevated Command Prompt, from %SystemDrive%\$Windows.~bt\Sources or Windows.old

SetupDiag.exe /Output:C:\SetupDiag\Results.log
  1. Read the results file. SetupDiag ships with Windows Setup, parses the setup logs for you and names the failure it recognises, which beats reading setuperr.log by hand.
  2. Disconnect everything except mouse, keyboard and display. Microsoft names this first for 0x30018 and 0x2000C, and it resolves a large share of these rollbacks on its own. Docks, card readers, external disks and capture devices are the usual offenders.
  3. Accept ‘Download and install updates (recommended)’ at the start of setup so it can fetch current drivers rather than carrying yours forward.
  4. For 0x20017, open %windir%\Panther\setuperr.log and setupact.log, find the driver named around the failure, and update or uninstall it. That is Microsoft’s published mitigation for this one.
  5. For 0x40017, perform a clean boot first, then run the upgrade. That is the published mitigation for the second-restart failure.
  6. Suspend disk encryption before you start: manage-bde -protectors -disable C: -rebootcount 3, having confirmed you can get at the recovery key.

Nothing is lost in a rollback: the machine comes back on the old build with data and applications intact. Reinstalling from fresh media without removing the driver produces the same rollback at the same point.

If the upgrade completes, you are done. If it rolls back again, the next section explains what each extend code is telling you about where the driver failed.

Why it happens

Windows Setup runs the upgrade in phases, and it reports failures as a result code plus an extend code. The result code 0xC1900101 is generic and means a rollback occurred; Microsoft states that in most cases the cause is a driver compatibility issue. The extend code is where the information is. Its first digit is the phase and its last two are the operation, both taken from tables Microsoft publishes.

So 0x30018 decodes as phase 3, FIRST_BOOT, operation 0x18, SYSPREP – and Microsoft’s published cause for that pairing is that a device driver stopped responding to setup.exe during the upgrade. 0x20017 is phase 2, SAFE_OS, operation 0x17, BOOT, published as a driver causing an illegal operation, a SafeOS boot failure typically caused by drivers or non-Microsoft disk encryption software, and possibly by a hardware failure. 0x40017 is phase 4, OOBE_BOOT, the same BOOT operation, published as a failure after the second restart caused by a faulty driver such as an antivirus filter driver or an encryption driver.

0x30017 is the one to be careful about. There is no row for it in Microsoft’s tables. The two halves decode cleanly – FIRST_BOOT and BOOT – and the result code is the generic rollback, but nobody publishes a cause or a mitigation for that specific pairing. Treat it as a first-boot driver failure by analogy with its neighbours and diagnose it from the logs, not from a definition somebody has invented for it.

One documented case is worth knowing by name because it looks like a mystery until you have heard of it. Microsoft documents 0xC1900101 – 0x40017 on machines running Citrix Virtual Delivery Agent: its file system filter driver, CtxMcsWbc, prevents the upgrade writing changes to disk, so the upgrade cannot complete and the system rolls back after the second restart. Microsoft publishes two workarounds – uninstall the VDA and reinstall it after the upgrade, or disable the Citrix MCS cache service and remove the CtxMcsWbc entry in the registry.

An attached peripheral or its driver

You have this one if The rollback happens at boot and the machine has a dock, external storage, a card reader or unusual USB hardware attached.

  1. Shut down and disconnect everything except mouse, keyboard and display, then run the upgrade again.
  2. If the machine uses a dock, connect the display directly and take the dock out entirely for the duration.
  3. Remove SD cards and USB storage; setup can assign drive letters to them and lose track of which volume is which.
  4. Reconnect devices one at a time once the upgrade has succeeded.

Security or encryption software with a filter driver

You have this one if 0x40017 or 0x20017 on machines running third-party antivirus, disk encryption or an endpoint agent.

  1. Uninstall the product rather than disabling it. A disabled product still has its drivers installed and they still load.
  2. Use the vendor’s own removal tool where the ordinary uninstall leaves components behind, and confirm with fltmc filters that the driver has gone.
  3. Suspend BitLocker with manage-bde -protectors -disable C: -rebootcount 3 before starting.
  4. Reinstall the product afterwards on a build the vendor supports.

Microsoft Defender takes over while a third-party product is absent, so the machine is not unprotected during the upgrade.

The storage controller driver cannot start in the new build

You have this one if 0x20017 or 0x40017 on a machine using a vendor RAID or rapid-storage driver rather than the standard controller driver.

  1. Get the current storage controller driver for the exact model from the manufacturer’s support site and install it before upgrading.
  2. Retry with setup.exe /auto upgrade /migratedrivers none so setup installs its own drivers instead of carrying yours across.
  3. If the vendor driver is no longer maintained, moving to the standard controller driver may be the only route forward.

Do not change the disk controller mode in firmware to work around this. Changing it on an installed system can leave Windows unable to boot, and Microsoft does not publish it as a mitigation for these codes.

A stale driver package is still in the store

You have this one if The same driver keeps appearing in the setup log after you have removed the device or updated the driver.

  1. List third-party packages with pnputil /enum-drivers and find it by original file name and provider.
  2. Note its published name in the form oemNN.inf and remove it: pnputil /delete-driver oemNN.inf /uninstall.
  3. Restart, then in Device Manager turn on Show hidden devices from the View menu and remove ghosted devices for hardware that is gone.

The known Citrix VDA filter driver case

You have this one if 0x40017 specifically, after the second restart, on a machine running Citrix Virtual Delivery Agent.

  1. Uninstall Citrix VDA with its own setup application, run the upgrade, then reinstall it.
  2. If you cannot uninstall it, set the Start value to 4 under the CtxMcsWbc subkey of the class key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class{4d36e967-e325-11ce-bfc1-08002be10318}, then delete the CtxMcsWbc entry from the class key itself and restart.
  3. Retry the upgrade.

Full reference

Decoding an extend code yourself

The extend code is two published tables joined together. The leading digit is the phase: 1 DOWNLEVEL, 2 SAFE_OS, 3 FIRST_BOOT, 4 OOBE_BOOT, 5 UNINSTALL. The final two digits are the operation, including 0x04 INSTALL_RECOVERY_ENVIRONMENT, 0x08 PREPARE_SAFE_OS, 0x0C APPLY_IMAGE, 0x0D MIGRATE_DATA, 0x17 BOOT and 0x18 SYSPREP. Reading them tells you where setup was, which is often enough to know which log to open.

Extend code Phase and operation Published cause
0x20017 SAFE_OS / BOOT A driver caused an illegal operation; a SafeOS boot failure
0x30017 FIRST_BOOT / BOOT No published cause for this pairing
0x30018 FIRST_BOOT / SYSPREP A device driver stopped responding to setup.exe
0x40017 OOBE_BOOT / BOOT Failure after the second restart caused by a faulty driver

Where the evidence is kept

Location What it holds
%windir%\Panther\setuperr.log Errors, retained after a rollback
%windir%\Panther\setupact.log The full action log
$Windows.~BT\Sources\Rollback Rollback logs, event logs and any setupmem.dmp
$Windows.~bt\Sources\setupapi\setupapi.dev.log Device and driver installation detail, useful when the rollback is at SYSPREP
%SystemDrive%\$Windows.~bt\Sources Where setup extracts SetupDiag during an upgrade

After a successful upgrade SetupDiag is moved to %SystemDrive%\Windows.old, and it goes when that folder is deleted. If you need it later, Microsoft publishes it as a separate download.

Setup options worth knowing

Option Accepted values Why you would use it
/Auto Clean, DataOnly, Upgrade upgrade keeps apps and data
/MigrateDrivers All, None None stops setup carrying the current drivers forward
/DynamicUpdate Enable, Disable, NoDrivers, NoLCU, NoDriversNoLCU NoDrivers keeps the cumulative update but stops fresh driver acquisition
/Compat IgnoreWarning, ScanOnly ScanOnly runs the compatibility scan and exits
/CopyLogs A local or UNC path Collects the logs from an unattended run

When it rolls back with no driver named

  • Check the rollback folder for a setupmem.dmp and read the stop code; a bug check names the module far more reliably than the setup logs do.
  • Run the upgrade from mounted media rather than through Windows Update, so you can pass options and read the logs as it runs.
  • Repair the component store with DISM.exe /Online /Cleanup-image /Restorehealth and then sfc /scannow before another attempt.
  • Free disk space. Setup needs headroom for the new image and the rollback copy, and behaves unpredictably without it.
  • Check the vendor’s support site for a build of the driver that names your target Windows version explicitly, rather than the newest one on offer.

When a licence is the actual fix

This is a driver problem and not a licensing one, and on a machine that is already activated the upgrade costs nothing: a device with a digital licence keeps it across an in-place upgrade and reactivates on its own. Two situations move the conversation to a licence. The first is a machine still on Windows Home where you want the management, encryption or policy behaviour that only the business editions carry – a Windows 11 Pro upgrade licence changes the edition, and it changes nothing about the driver that is causing the rollback. The second is a machine whose vendor driver has no build for the version you are upgrading to; that is a hardware support decision, and buying an operating system licence does not create a driver. Work through the peripheral, filter driver and driver store causes above first. If the rollback survives all of them, you have a driver question for the hardware vendor, not a purchase to make.

Every code this article covers

Code What it points at Source
0xC1900101 - 0x30018 A device driver stopped responding to setup.exe during the upgrade; the extend code is FIRST_BOOT / SYSPREP Microsoft Learn
0xC1900101 - 0x20017 A driver caused an illegal operation: a SafeOS boot failure, typically drivers or non-Microsoft disk encryption software, possibly hardware Microsoft Learn
0xC1900101 - 0x30017 No published cause for this pairing; the halves decode as the generic rollback code with FIRST_BOOT / BOOT, so treat it as a first-boot driver failure and use the logs Microsoft Learn phase and operation tables
0xC1900101 - 0x40017 The upgrade failed after the second restart because of a faulty driver, for example an antivirus filter driver or an encryption driver Microsoft Learn

Confirm the fix worked

  1. winver reports the build you were upgrading to.
  2. Device Manager shows no device with a warning icon, particularly under storage controllers and system devices.
  3. fltmc filters shows the filter drivers you expect and none you thought you had removed.
  4. manage-bde -status C: shows protection back on if you suspended BitLocker.
  5. The machine restarts twice without rolling back, which is the point at which an OOBE_BOOT failure would have appeared.

Questions people ask about this

Will I lose my files if the upgrade rolls back?

No. A rollback returns the machine to the previous build with data and applications intact – that is what the rollback is for. It is disruptive rather than destructive.

Do I need to buy a licence to upgrade to Windows 11?

Not to clear these codes. A device with a valid digital licence for the edition keeps it across an in-place upgrade. A licence purchase only enters the picture if you are also changing edition.

Does /migratedrivers none mean I lose my drivers?

It means setup does not carry the current driver set forward, so the new installation uses the drivers it ships with or fetches. That is often exactly what you want when an old vendor driver is causing the rollback; you can reinstall specific drivers afterwards.

What is 0xC1900101 – 0x30017?

An extend code with no published row. The phase and operation decode as FIRST_BOOT and BOOT from Microsoft’s tables, and the result code is the generic rollback. Anyone offering you a precise cause for that exact pairing is extrapolating.

How many times should I retry before changing something?

Once. A rollback that repeats with the same extend code will keep repeating; the second attempt tells you the failure is deterministic, and everything after that should be a change rather than a retry.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

License Error 0x80248015 and 0x8024002E: an expired service registration or a policy block License Error 0xC1900101 – 0x20004 and 0x8007042B: drivers and killed processes roll the upgrade back License Error 0xC1900101 – 0x4000D and 0x2000C: the upgrade fails applying the image or migrating data License Error 0x800F0906 in DISM: Windows cannot download the repair source files
← Back to Knowledge Base