Fix error 0xc1900101

0xC1900101 is MOSETUP_E_SETUP_PLATFORM, a generic rollback code: Windows Setup hit an error and restored your old version. Microsoft says it usually means an incompatible driver. Update drivers and BIOS from your PC maker, unplug everything except mouse, keyboard and display, remove non-Microsoft antivirus, then run the upgrade again.

Checked November 10, 2026 against the manufacturer's own pages.

The short version

What to install and where it comes from. Every link goes to the manufacturer or Microsoft, never to a copy.

Code0xC1900101, often followed by an extend code such as 0x4000D
Official nameMOSETUP_E_SETUP_PLATFORM
Where it appearsFeature updates and upgrades (Windows Update, Installation Assistant, setup.exe from media)
Most common causeAn incompatible or outdated device driver
Windows versionsUpgrades to Windows 11 and Windows 10
Microsoft Learn: Windows 10 upgrade resolution procedures (0xC1900101)learn.microsoft.comMicrosoft Learn: Windows 10 upgrade error codes (result and extend codes)learn.microsoft.comMicrosoft Support: How to perform a clean boot in Windowssupport.microsoft.comMicrosoft Support: Troubleshoot problems updating Windowssupport.microsoft.com

Official files only, nothing bundled

Step by step

  1. Write down the full code pair

    Setup reports two parts, for example 0xC1900101 - 0x30018. The second part, the extend code, tells you the phase and operation that failed. Keep it; the table below matches each common pair to a fix.

  2. Update drivers and BIOS from your PC maker

    Go to your laptop or motherboard maker's support page for your exact model and install the newest chipset, storage, graphics, network and BIOS updates. Microsoft says that in most cases the cause of 0xC1900101 is a driver compatibility issue.

  3. Unplug everything you do not need

    Disconnect docks, USB drives, printers, card readers, extra monitors and external disks. Keep only the mouse, keyboard and display, as Microsoft advises for the 0x2000c and 0x30018 cases.

  4. Remove non-Microsoft antivirus for the upgrade

    Microsoft lists uninstalling antivirus applications as a mitigation, because their filter drivers can block Setup. Microsoft Defender takes over meanwhile; reinstall your antivirus afterwards.

  5. Clean boot, then upgrade

    Press Win + R, run msconfig, tick Hide all Microsoft services on the Services tab and choose Disable all, then disable startup apps in Task Manager. Restart and run the upgrade. Undo these settings when it is done.

  6. Accept the setup updates and free space

    When Setup asks, choose Download and install updates (recommended), so it fetches newer drivers and fixes. Keep at least 20 GB free on C: for a 64-bit upgrade.

  7. Read the logs if it rolls back again

    Open C:\$Windows.~BT\Sources\Rollback (show hidden items in File Explorer). Microsoft points to setupmem.dmp, the .evtx event logs and setupapi\setupapi.dev.log there to identify the driver.

Faster option: let a PC tool do the clean-up

The steps above fix this error. Errors like this often come back on a PC full of junk files, broken registry entries and leftovers from removed programs. A maintenance tool clears those in one scan.

Scan and clean up Windows

Finds junk files, invalid registry entries, startup slowdowns and privacy traces, then fixes them in one click.

Auslogics BoostSpeed 14 · Free version · Windows 11, 10, 8, 7 · 30-day refund on Pro

Why Windows rolls back with 0xC1900101

Feature upgrades run in phases: the old Windows prepares, a temporary Safe OS copies the new image, then two boots finish the install and migrate your data. If a driver crashes or stops responding in any phase after the first, Setup cannot trust the new system and restores the old one. Microsoft calls 0xC1900101 a generic rollback code that can appear at any stage except the downlevel phase, and says it usually indicates an incompatible driver that can cause blue screens, hangs or unexpected restarts.

Common extend codes and what they point to

Code pair Phase and step Microsoft’s suggested fix
0xC1900101 - 0x20004 Safe OS, installing the recovery environment Remove antivirus, unused SATA devices and drivers; update drivers and BIOS
0xC1900101 - 0x2000c Safe OS, applying the image Unplug peripherals, get updated drivers, check the disk with chkdsk
0xC1900101 - 0x20017 Safe OS, boot Find the bad driver in setuperr.log and setupact.log; update or uninstall it
0xC1900101 - 0x30018 First boot, sysprep A device driver stopped responding; unplug devices, update drivers
0xC1900101 - 0x3000D First boot, migrating data Often the display driver; update or uninstall it
0xC1900101 - 0x4000D Second boot, migrating data Check the rollback log for the stop code; update the named driver and BIOS
0xC1900101 - 0x40017 Second boot, boot Clean boot and retry; filter drivers from antivirus or encryption tools

Less common: disk encryption or old storage drivers

For 0x20017, Microsoft notes that non-Microsoft disk encryption software can cause the Safe OS boot to fail, and that hardware faults can too. If you use a third-party encryption product, check its maker’s guidance for Windows upgrades before you try again. Microsoft’s advice for 0x20004 points the same way: remove unused SATA devices and drivers for hardware you no longer have, because they load during Setup too.

Questions

What do the extend codes mean?

The first digit is the phase: 2 is Safe OS, 3 is first boot, 4 is the second (OOBE) boot. The last two digits are the operation, for example 0D for migrating data or 17 for boot. Microsoft's error code article lists them all.

Which driver is usually to blame?

Microsoft does not single out one type. Its table mentions display drivers for 0x3000D, out-of-date drivers for 0x20004, and antivirus or encryption filter drivers for 0x40017.

Will I lose files when the upgrade rolls back?

The rollback restores your previous Windows version with its files and apps. Keep a backup anyway before every upgrade attempt.

Is there a Microsoft tool that reads the logs for me?

Yes. Microsoft's SetupDiag tool analyses Windows Setup log files and reports why an upgrade failed. Microsoft's resolution article links to it.