Windows 11 Upgrade Failed and Rolled Back (0xC1900101): Fix It in Microsoft's Order
In plain English
A Windows 11 upgrade that fails, then rolls itself back with 0xC1900101, usually points to a driver, device, or low-level hardware problem rather than a bad password or missing file. Windows has already tried to protect your PC by undoing the half-finished upgrade.
First safe step
Unplug every nonessential device, then try the upgrade once more. Leave only power, your display, keyboard, mouse, and internet connected. If it rolls back again, work through the steps below instead of repeating the same retry.
Work through them in order. Stop when the upgrade succeeds.
A Windows 11 upgrade that fails, then rolls itself back with 0xC1900101, usually points to a driver, device, or low-level hardware problem rather than a bad password or missing file. Windows has already tried to protect your PC by undoing the half-finished upgrade. If you need the bigger picture on where Windows 11 fits now, start with the Windows 10, ESU and Windows 11 decision hub.
This page uses Microsoft's own retry steps, cheapest first, instead of jumping straight to a reset or clean install. That matters because 0xC1900101 often clears after you remove the blocker and try again, especially if the blocker is a USB device, storage driver, security software, or another recent change. If you are not sure your PC still meets the basics, check the quick Windows 11 check before you try again.
The safest first check is simple: disconnect non-essential devices and remove the most likely driver problem before you rerun setup. If the upgrade was blocked by compatibility rules instead of a true rollback failure, see what the Windows 11 readiness message really means. Then work through the steps below in order, so you do not wipe a working PC for a problem that usually has a smaller fix.
What 0xC1900101 means and what to do first
0xC1900101 usually means setup hit a driver problem while Windows 11 was changing over, not that your personal files suddenly vanished. In plain English, a device, controller, or low-level software part did not behave the way setup expected. If you are also seeing a separate compatibility warning, read what the Windows 11 readiness message really means, because that is a different problem from this rollback code.
The rollback is Windows protecting the PC. Setup started, could not finish safely, and put the earlier version back so the computer would still start. If the screen seemed frozen for a long time before that happened, check how long to wait before you assume the upgrade truly failed before treating it as a fresh failure.
Your first retry should be simple. Shut the PC down, unplug nonessential devices, then start it again and try the upgrade one more time. Leave only the basics connected: power, display, keyboard, mouse, and internet if you need it. Before that retry, check you have enough free space: Microsoft asks for at least 16 GB free on 32-bit Windows and 20 GB on 64-bit. Then run Windows Update a few times and install what it offers, because a pending update can itself be the blocker.
Remove things like USB drives, docks, printers, scanners, SD cards, Bluetooth adapters, game controllers, and extra external storage. If you are not sure whether the PC is ready for Windows 11 after you clear the accessories, run the quick Windows 11 check before you try again. If the upgrade fails again with 0xC1900101, move to the next step instead of repeating the same retry over and over.
1 Step 1: Remove the easiest driver and device causes Free
After the first unplug-and-retry check, do one fuller pass on anything Windows setup does not need. Disconnect printers, docks, USB hubs, card readers, game controllers, webcams, external drives, and spare monitors. If you are also unsure whether the PC itself meets Windows 11 rules, read what the Windows 11 readiness message really means and run the quick Windows 11 check before you try again.
Leave connected only power, your main display, keyboard, mouse, and internet if you need it. Then remove or turn off third-party security software, VPN apps, PC tuning tools, RGB control suites, and driver updater tools for the next upgrade attempt. These can load low-level drivers or filter traffic during setup, which is a common reason for 0xC1900101 rollbacks.
If you use a third-party antivirus app, use its own uninstall tool or the normal uninstall option in Control Panel or Settings, then restart before trying again. A simple pause button is sometimes not enough because the driver still loads at startup. If the failed upgrade also left the PC unstable afterward, start with what to do first after an update-triggered crash or rollback.
Think back to the day the upgrade failed. If you had just installed a new graphics, storage, Wi-Fi, Bluetooth, or chipset driver, or updated BIOS or device firmware, write that down as the most likely suspect. Do not change five things at once. Keep that recent change in mind for the rollback step later, and if the next attempt seems frozen, check how long to wait before you assume the upgrade truly failed.
✓ Upgrade went through? You can stop here.
2 Step 2: Check the upgrade path in Update history and setup logs Free
Before you change anything else, confirm which upgrade attempt actually failed. Open Settings > Windows Update > Update history, then look for the Windows 11 feature update entry, its date, and any failed status around the time you saw 0xC1900101. If you want a slower walkthrough, start with checking Update history for the failed upgrade entry.
This matters because Windows can retry an upgrade on its own later, and the newest entry is not always the first failed one. A rollback entry or repeated feature update attempt helps you match the failure to the exact day, which makes the next step more accurate. If the entry is a readiness block instead of a failed install, read what the Windows 11 readiness message really means before you keep retrying.
You can also use setup logs as clue files, but most home users do not need to read them line by line. Check setuperr.log first, then setupact.log. If the upgrade rolled back, the rollback log set lives in $Windows.~BT\Sources\Rollback. If those logs mention a driver name, storage controller, antivirus filter, or a device class near the failure time, treat that as a lead for the next step, not as proof by itself.
If Update history shows no real Windows 11 feature update attempt, stop here and do the quick Windows 11 check before you try again. That helps separate a true rollback from a PC that was never allowed onto the upgrade path in the first place.
3 Step 3: Repair the disk and system files, then retry from a clean boot Free
If the upgrade still rolls back after the device pass, work through Microsoft's repair steps in this order: check the disk, restart cleanly, then repair the system files. Do them one at a time, and retry the upgrade only after all three are done.
- First, check the hard drive for errors. Open Command Prompt as an administrator, type
chkdsk /f C:, and press Enter. If it asks to run at the next restart, accept that, restart the PC, and let the check finish before you do anything else. - Next, do a clean restart into Windows, so only Microsoft services and startup items load. A clean boot keeps third-party drivers and startup programs out of the way while you test the upgrade again.
- Last, repair the system files. In the same administrator Command Prompt, type
DISM.exe /Online /Cleanup-image /Restorehealthand press Enter, then wait for it to finish. Once all three steps are done, try the Windows 11 upgrade once more.
✓ Upgrade installed? You can stop here.
4 Step 4: Roll back the change that is most likely causing the failure Free
If 0xC1900101 came back after the clean retry, stop adding more fixes at random. The next move is to undo the one recent change most likely to have put a bad driver or low-level software in the upgrade path. Think about what changed shortly before the first failed attempt: a graphics driver, Wi-Fi driver, storage controller driver, BIOS update, SSD firmware update, or a new antivirus or VPN package.
Change one thing, then test once. If you remove three drivers, update the BIOS, and uninstall security software all in the same afternoon, you will not know what actually fixed it. If the failure happened right after a Windows patch, use the honest uninstall path if the upgrade left a bad update behind before you try the feature upgrade again.
Start with the newest driver or firmware change, especially display, chipset, storage, Bluetooth, and network drivers. In Device Manager, open the device that changed most recently and look for a rollback option on its driver tab. If a BIOS or firmware update was the last change, do not guess, check the PC maker's support page for their rollback advice, because some firmware updates cannot safely be reversed.
If you recently changed antivirus, endpoint security, disk encryption, VPN, or motherboard utility software, remove only that one product and restart before the next test. If the machine became unstable after the rollback or update attempt, read what to do first after an update-triggered crash or rollback. If the failed entry turns out to be something smaller than a real Windows 11 feature upgrade, go back to checking Update history for the failed upgrade entry so you do not chase the wrong problem.
5 When to stop retrying and move to the next Windows 11 decision
If the upgrade has failed, rolled back, and shown 0xC1900101 more than once after your clean retry, stop there. At that point, this is usually no longer a one-time glitch. It points to a driver, firmware, storage-controller, BIOS, or supportability problem that needs a different decision, not more blind retries.
If you are also seeing mixed messages about Windows 11 support, check what the Windows 11 readiness message really means and run the quick Windows 11 check before you try again. A PC can hit 0xC1900101 during setup and still have a separate requirements issue, so it is worth confirming the upgrade path before you spend more time on setup logs and retries.
If the machine is not a clear Windows 11 fit, move to the Windows 10, ESU and Windows 11 decision hub instead of forcing the upgrade. That is the better next step when the real choice is whether to stay on Windows 10, plan for ESU, replace the device, or upgrade later after a driver or firmware fix from the PC maker.
The rule is simple: repeated 0xC1900101 rollbacks mean stop guessing. Check the PC's upgrade path first, then make the next Windows decision based on support, hardware, and the exact blocker you found.
Frequently asked questions
Will I lose my files if the Windows 11 upgrade rolls back?
Not necessarily. The rollback is meant to return the PC to the previous version of Windows, and Microsoft says only that setup returns the PC to the previous OS desktop. It makes no promise that every file survives, so back up your files before you try the upgrade again. If something looks missing, check the usual folders and the account you signed in with before you try another fix.
How soon can I try the upgrade again after 0xC1900101?
Only after you have removed the device or software cause and checked Update history for the failed entry. A repeat try with nothing changed will usually fail the same way.
Should I do a clean install after repeated rollbacks?
No, not as the next step. A clean install removes apps and settings, so first confirm the PC can run Windows 11 and find whether a driver or device is still blocking setup.
The short version
If 0xC1900101 came back after the device pass, the repair and clean-boot retry, and one rollback of a recent change, the repeat is the clue. Setup is still meeting the same blocker, so another try with the same setup is not likely to change the result.
Stop there, keep the notes from Update history and the change you undid, and use them to pick the next step. That record is what makes the Windows 11 decision clear, whether it is a driver to replace, a device to leave out, or a PC that stays on its current version for now.
Different number on screen?
Type it exactly as it appears and get the plain-English answer.
Pop-up telling you to call?
That is a scam. Microsoft never asks you to phone a number.