Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | Setup was unable to complete the upgrade. | setuperr.log | -> Error code: 0xC1900101 |
| Affected build range | Windows 10 to Windows 11, or Windows 10 version upgrades | Microsoft Learn documentation | |
| Registry key involved | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\PnpOptions | Event Viewer logs | -> Check for TPM and Secure Boot settings |
| Relevant service/endpoint URL | https://www.microsoft.com/en-us/software-download/windows11 | Microsoft Download Center | |
| Log line signature | [SR] Starting system restore operation to roll back the machine to its previous state. | setupact.log | -> Indicates rollback phase |
Log Files to Check
C:\$WINDOWS.~BT\Sources\Panther\setuperr.logC:\$WINDOWS.~BT\Sources\Panther\CompatData_*.xml
What This Error Actually Means
The error code0xC1900101, also known as MOSETUP_E_COMPAT_SCANONLY, is a generic umbrella term for hardware and driver compatibility issues encountered during the upgrade process from Windows 10 to Windows 11 or between different versions of Windows 10. This error signifies that the setup process has been unable to complete due to an issue with one or more drivers or hardware components on your system. The specific phase where this failure occurs is indicated by a secondary code, such as 0xC1900101-0x20017, which points to the disk or storage driver during the SAFE_OS phase.
Affected Versions and Scope
This error affects systems running Windows 10 that are attempting an in-place upgrade to Windows 11, as well as those upgrading between different versions of Windows 10. It does not affect clean installations of Windows 11 or upgrades from other operating systems such as macOS or Linux.Where To Look First: Logs and Event IDs
To diagnose the issue, you should first examine theC:\$WINDOWS.~BT\Sources\Panther\setuperr.log file for error messages that indicate which driver or hardware component is causing the failure. Additionally, check the C:\$WINDOWS.~BT\Sources\Panther\CompatData_*.xml files to identify specific incompatible devices by their hardware ID.
Event IDs such as 4103 and 6008 can also provide valuable information about system failures during the upgrade process. You should filter Event Viewer logs for these IDs under Windows Logs > System, looking specifically at entries from the source Microsoft-Windows-Kernel-PnP to identify hardware or driver issues.
Root Causes
Incompatible Drivers
One common cause is outdated or incompatible drivers, particularly those related to disk controllers, GPUs, NICs, and storage devices. To distinguish this issue, look for error messages in the setuperr.log file that mention specific .sys or .dll files.TPM 2.0 and Secure Boot Requirements
Another frequent cause is a failure to meet TPM 2.0, Secure Boot, or UEFI requirements necessary for Windows 11 installation. This can be identified by checking the PC Health Check report or examining Event Viewer logs around the time of the upgrade attempt.Insufficient Disk Space on System Partition
A lack of sufficient free space on the system partition (minimum 64 GB) can also trigger this error. You should check the disk space available during the upgrade process to ensure it meets these requirements.Fix Procedure
- Update or Remove Incompatible Drivers: Open Device Manager (
devmgmt.msc) and update drivers from the OEM website for any devices with yellow warning icons. If a driver is incompatible, consider removing it. - Check TPM 2.0 and Secure Boot Settings: Ensure that these settings are enabled in your UEFI/BIOS configuration.
- Free Disk Space: Use the
Get-Volumecmdlet to check available space on system partitions, then free up at least 64 GB of disk space. - Disable Security Software Temporarily: Before upgrading, disable third-party antivirus or security software that may interfere with the upgrade process. Use
Get-Process -Name "antivirusprocessname" | Stop-Processto stop such processes. - Run DISM and SFC Commands: Repair any pre-existing component store corruption using PowerShell commands:
DISM /Online /Cleanup-Image /RestoreHealth, followed bysfc /scannow.
Error Code Variants
| Code | Description | Distinguishing Factors |
|---|---|---|
0xC1900101-0x20017 |
Driver failure during SAFE_OS phase (disk or storage driver) | Error messages in setuperr.log related to disk drivers. |
0xC1900101-0x30018 |
Driver failure during FIRST_BOOT phase (GPU or NIC driver) | Error messages in setuperr.log related to GPU or network drivers. |
0xC1900101-0x4000D |
Driver failure during MIGRATE_DATA phase | Error messages in setuperr.log related to data migration issues. |
0xC1900101-0x40017 |
Driver failure during SECOND_BOOT phase (common with security software) | Error messages in setuperr.log related to security or encryption drivers. |
Verification
To verify that the fix has been successful, you should check for a clean upgrade process without error codes. Look for log lines indicating successful completion of each phase (e.g.,[SR] Starting system restore operation to roll back the machine to its previous state.) in the setupact.log file.
Prevention
To prevent recurrence, implement policies that ensure all devices meet TPM 2.0 and Secure Boot requirements before attempting an upgrade. Use Intune admin center > Devices > Compliance Policies to enforce these settings across your organization. Additionally, create a baseline of compatible drivers for critical hardware components (disk controllers, GPUs, NICs) and update them regularly.Be cautious when disabling security software as it can expose devices to vulnerabilities.
A quick diagnostic shortcut is to run the PC Health Check tool from Microsoft's website to verify hardware compatibility before initiating an upgrade process.
0xC1900101 errors during future upgrades.