Install Error 0xC1900101: How to Fix It

Install error 0xC1900101 means Windows Setup rolled back because a driver or another low-level component failed during the upgrade. The prefix identifies a family of driver-related failures, but it is not the complete diagnosis. The numbers that follow it, such as 0x20017 or 0x30018, show which installation phase failed and help narrow down the responsible device or software.

That is why repeatedly pressing Retry often produces the same result. A better approach is to record the complete code, remove likely hardware and driver conflicts, and use Windows Setup’s own diagnostic results when the cause is not obvious.

Record the Complete Error Before Changing Anything

Windows may show a message similar to:

We couldn't install Windows 11
We've set your PC back to the way it was right before you started installing Windows 11.

0xC1900101 - 0x30018
The installation failed in the FIRST_BOOT phase with an error during SYSPREP_SPECIALIZE operation.

Take a photo or copy the entire message. The second code and the named phase are more useful than 0xC1900101 by itself.

Also note what happened immediately before the rollback:

• Did the PC restart or show a blue screen?
• Did it freeze while checking for updates?
• Did a specific device stop working?
• Was a BIOS, driver, antivirus, VPN, or storage utility recently installed?
• Does Device Manager show a warning symbol?

Back up important files before another upgrade attempt. A normal rollback should restore the previous Windows installation, but it should not be treated as a substitute for a verified backup.

If the upgrade has already rolled back repeatedly, read the SetupDiag result before making another batch of changes. A result naming a driver or failed operation gives you a more specific lead than the 0xC1900101 prefix alone. Keep that result with the complete error message.

What the Second Code Tells You

Windows Setup moves through several phases. A failure suffix helps identify where to concentrate the investigation.

Example	Setup area commonly involved	Start by checking
0xC1900101-0x20017	SAFE_OS or early boot	Storage controller, chipset, BIOS, encryption, boot filter, and attached devices
0xC1900101-0x2000C	SAFE_OS while applying the image	Disk health, storage space, filter drivers, and installation files
0xC1900101-0x30018	FIRST_BOOT	Graphics, network, audio, security software, and services loaded during the first boot
0xC1900101-0x3000D	FIRST_BOOT during data migration	User-profile data, drivers, and software migration conflicts
0xC1900101-0x4000D	SECOND_BOOT or migration	User profiles, applications, and incompatible drivers
0xC1900101-0x40017	SECOND_BOOT during boot	A driver or service that loads late in the upgrade

These associations are starting points, not proof that one named device is faulty. Use the full message, SetupDiag, and log files to confirm the cause.

Start With Hardware That Windows Does Not Need

Microsoft recommends removing nonessential hardware when troubleshooting Windows upgrade failures. Disconnect:

• External hard drives and USB flash drives
• Printers, scanners, capture cards, and webcams
• USB hubs and docking stations
• Game controllers and specialist input devices
• Audio interfaces and Bluetooth adapters
• Secondary monitors when they are not required

Keep the keyboard, mouse, primary display, network connection, and power adapter. Restart the computer after disconnecting the other devices, then try the upgrade again.

This simple test is especially important when the error appeared after adding new hardware. The device may work normally in the existing version of Windows while its driver fails during the upgrade environment.

Microsoft’s Windows upgrade and installation error guidance confirms that 0xC1900101 errors are normally driver errors and recommends checking drivers, external hardware, security software, disk space, and system files.

Check Device Manager Before Updating Drivers

Updating every driver is not a reliable strategy. First identify devices Windows already considers problematic.

1. Right-click Start and select Device Manager.
2. Open View and select Show hidden devices.
3. Expand the main hardware categories.
4. Look for a yellow warning symbol, an unknown device, or an old duplicate device that is no longer connected.
5. Open the device’s Properties and read the message under Device status.

Show hidden devices before checking for an old or failed driver that may block Setup.

Do not remove every faded entry. Some hidden devices are legitimate components that are not currently connected. Concentrate on hardware you recognize as obsolete, devices with an error, and software-created adapters left behind by an application you removed.

Update the Drivers Most Likely to Affect Setup

Use the support page for the computer or motherboard model. Prioritize:

1. BIOS or UEFI firmware when the vendor specifically lists upgrade compatibility or stability fixes
2. Chipset and platform drivers
3. Storage, SATA, NVMe, RAID, Intel RST, or AMD storage drivers
4. Graphics drivers
5. Network, Wi-Fi, and Bluetooth drivers
6. Audio drivers and specialist peripheral software

Install one category at a time and restart when requested. This makes it easier to identify what changed.

Avoid unknown driver-updater applications. They can install a technically newer but incorrect package, making the rollback harder to diagnose. Windows Update and the hardware manufacturer’s official support page are safer sources.

When Setup or Windows Update cannot find the network device at all, use the steps in Windows could not find a driver for your network adapter before attempting another upgrade.

Remove Software That Installs Low-Level Drivers

Some applications add filter drivers or background services that remain active even when the main app is closed. Common examples include:

• Third-party antivirus and endpoint-security suites
• Old VPN clients
• Virtual-drive and disc-emulation software
• Disk encryption or partition-management tools
• RGB, fan-control, tuning, and overclocking utilities
• Backup applications with snapshot drivers
• Virtual-machine networking components

Use the program’s normal uninstaller, restart Windows, and then retry the upgrade. Merely disabling an antivirus tray icon may not unload its driver.

Keep installation files, licence keys, and configuration backups for anything you plan to reinstall. Do not remove BitLocker or change storage-controller modes without understanding the recovery and boot implications.

Use a Clean Boot to Isolate a Background Conflict

A clean boot temporarily prevents non-Microsoft services and startup apps from loading.

1. Press Windows + R, enter msconfig, and press Enter.
2. Open the Services tab.
3. Select Hide all Microsoft services.
4. Select Disable all.
5. Open the Startup tab and select Open Task Manager.
6. Disable nonessential startup applications.
7. Restart Windows and run the upgrade again.

Hide Microsoft services before disabling third-party services for a clean-boot test.

Do not leave the computer in a clean-boot state permanently. After the upgrade or test, return to System Configuration, restore normal startup, and re-enable the services you intentionally use.

Repair the Windows Image and Check the Drive

Open Terminal (Admin) or Command Prompt (Admin) and run:

DISM /Online /Cleanup-Image /RestoreHealth

After DISM completes, run:

sfc /scannow

Restart Windows even when both tools report success. When SFC cannot start or repeatedly returns the same protection error, follow SFC scannow not working rather than running the command over and over.

Check the file system with:

chkdsk C: /scan

This online scan does not normally require an immediate restart. Back up important data and investigate the drive’s health when CHKDSK reports errors it cannot repair, the drive disappears intermittently, or Windows records storage-related warnings.

Also check Settings > System > Storage. I would create at least 30 GB of free space before a major upgrade when possible. Setup needs working space for the new image, temporary files, migrated data, and rollback files.

Let SetupDiag Identify the Failure

SetupDiag is one of the most valuable parts of this repair because it examines Windows Setup logs and tries to match the failure to a known rule. Microsoft includes SetupDiag with Windows Setup in currently supported Windows versions, and it normally runs automatically after a failed upgrade.

Look for the automatic result here:

C:\Windows\Logs\SetupDiag\SetupDiagResults.xml

Open the file in a browser or text editor and look for fields such as:

• FailureData
• FailureType
• FailureCode
• FailureDetails
• LastPhase
• LastOperation

The last phase and operation provide more direction than the 0xC1900101 prefix alone.

Microsoft recommends using the latest SetupDiag version when running it manually. The official SetupDiag documentation explains the automatic result location, manual command options, and the rules used to detect upgrade blockers.

For a manual run:

1. Download the current SetupDiag from Microsoft’s documentation.
2. Create a folder such as C:\SetupDiag.
3. Place SetupDiag.exe inside it.
4. Open Command Prompt as administrator.
5. Run:

C:\SetupDiag\SetupDiag.exe /Output:C:\SetupDiag\Results.log

Open Results.log and note the matched rule, phase, operation, driver, or application. Microsoft notes that when SetupDiag finds multiple failures, the last logged failure is typically the fatal one.

Read the Rollback Logs When SetupDiag Is Inconclusive

Windows Setup stores logs in different folders as the upgrade moves through its phases. After a rollback, start with:

C:\$WINDOWS.~BT\Sources\Rollback\setupact.log
C:\$WINDOWS.~BT\Sources\Rollback\setuperr.log

Also check:

C:\$WINDOWS.~BT\Sources\Panther\setupact.log
C:\$WINDOWS.~BT\Sources\Panther\setuperr.log

The $WINDOWS.~BT folder is hidden. In File Explorer, enable View > Show > Hidden items.

setuperr.log is shorter, but the last error shown is not always the root cause. Use setupact.log to read the events surrounding the failure time. Search for:

• A .sys driver filename
• A device or vendor name
• BlockMigration
• Error
• Failed
• The second part of the installation code

Do not delete drivers only because their names appear once in a log. Look for repeated failures and confirm what device or software owns the file.

Retry With Current Installation Media

After correcting the identified conflict, use current official installation media rather than an old ISO left from an earlier release.

For an in-place upgrade:

1. Start Windows normally.
2. Mount the current Windows 11 ISO.
3. Run setup.exe from File Explorer.
4. Confirm Keep personal files and apps before selecting Install.
5. Choose Not right now when Setup repeatedly fails while downloading Dynamic Updates.

The last choice only skips updates during the installation attempt. Windows Update can run after Setup succeeds. See Windows 11 Setup stuck at 46% for the difference between an update-stage freeze and a driver-related rollback.

Users moving from Windows 10 should also follow the supported checks in how to upgrade from Windows 10 to Windows 11.

When BIOS or Hardware Testing Becomes Relevant

A BIOS update is not the first response to every 0xC1900101 error. Consider it when:

• The PC manufacturer lists a Windows upgrade compatibility fix.
• SetupDiag points to firmware, boot, storage, or ACPI behavior.
• The error occurs in SAFE_OS or during an early boot phase.
• The system uses an older BIOS revision and newer chipset or storage hardware.

Follow the manufacturer’s instructions exactly and maintain stable power. Do not interrupt a firmware update.

Test memory and storage when Windows also experiences random restarts, file corruption, drive timeouts, or blue screens outside Setup. A BSOD mentioning memory management may need the focused checks in MEMORY_MANAGEMENT BSOD before another upgrade attempt.

Repairs to Avoid

Several popular suggestions can make diagnosis worse:

• Do not install a bundle of drivers from an unknown updater.
• Do not delete the entire DriverStore folder.
• Do not disable driver-signature enforcement as a routine upgrade fix.
• Do not change AHCI, RAID, or Intel VMD settings without the manufacturer’s guidance.
• Do not force-install Windows 11 on unsupported hardware and assume every rollback is a removable driver problem.
• Do not perform a clean installation before saving the complete code and checking SetupDiag.

A clean installation can bypass migration-related conflicts, but it removes applications and may erase files depending on the choices made. Use it only after diagnosis, backup verification, and consideration of an in-place upgrade with fresh media.