Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | 0xC1900101-0x20017 | setupact.log | -> driver failure during Safe OS phase |
| Affected build range | Windows 10 to Windows 11 | SetupDiag tool report | |
| Registry key involved | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\PnpManager\DriverStore | Registry Editor | -> check for outdated drivers |
| Relevant service/endpoint URL | microsoft.com/en-us/windows/windows-11/setup | Microsoft website | -> SetupDiag tool |
| Log line signature | Operation: Upgrading the OS Result: 0xC1900101 | setupact.log |
Log Files to Check
C:\Windows\Panther\setupact.logC:\$WINDOWS.~BT\Sources\Panther\setupact.log
What This Error Actually Means
The error code 0xC1900101-0x20017 is a specific sub-code under the broader category of MOSETUP_E_DRIVER_CONFLICT, which indicates that there are driver compatibility issues preventing an in-place upgrade from Windows 10 to Windows 11. This particular sub-code (0x20017) points towards a failure during the Safe OS phase, where the system attempts to load drivers necessary for the installation process but encounters a problem with one or more of these drivers. The error is raised by the setup.exe component when it detects that a critical driver required for the upgrade process does not meet Windows 11's requirements.Affected Versions and Scope
This specific error code affects systems attempting to upgrade from any version of Windows 10 to Windows 11. The issue is particularly prevalent in environments with custom hardware configurations, such as enterprise desktops or laptops that may have unique storage controllers (like RAID/NVMe), network interface cards (NICs), and graphics processing units (GPUs). It does not affect systems running other versions of Windows or those that are being freshly installed rather than upgraded.Where To Look First: Logs and Event IDs
To diagnose this issue, the first place to look is in the setupact.log file located atC:\Windows\Panther\setupact.log. Search for the exact error string "0xC1900101" along with its sub-code (0x20017) and locate the log entry that includes 'Operation: Upgrading the OS' and 'Result: 0xC1900101'. Additionally, examine C:\$WINDOWS.~BT\Sources\Panther\setupact.log for any rollback details related to drivers.
For a more detailed analysis, review the Windows Event Viewer logs under Windows Logs > System. Look for critical error entries around the timestamp of when the upgrade attempt was made. The relevant event IDs are typically in the range of 7034 and 6012, which indicate driver loading failures during system startup or installation phases.
Root Causes
Incompatible Storage Controller Drivers
One common cause is outdated or incompatible storage controller drivers. These include RAID controllers and NVMe SSDs that may not be fully supported in Windows 11. To identify if this is the issue, check the setupact.log for entries mentioning specific driver failures related to storage devices.Antivirus Software Conflicts
Another frequent cause is conflicts with third-party antivirus software installed on the system. Antivirus applications often include kernel drivers that can interfere with Windows updates and installations. To determine if this is the problem, uninstall your current antivirus solution temporarily before attempting an upgrade again.Incompatible UEFI Firmware Drivers (Option ROMs)
UEFI firmware drivers or option ROMs may also cause issues due to incompatibility with Windows 11's Secure Boot requirements. These drivers are loaded early during boot and can prevent the system from reaching a state where it can proceed with an upgrade.Fix Procedure
- Generate Compatibility Report: Run the setup.exe /compat scanonly command from the Windows 11 ISO to generate a CompatData_
.xml file in C:\Windows\Panther. This XML file lists all incompatible drivers. - Update Drivers: Use Device Manager or visit your hardware manufacturer's support site to update any listed drivers. Focus on storage controllers, network adapters, and graphics cards.
- Uninstall Antivirus Software Temporarily: If antivirus software is suspected, uninstall it before attempting the upgrade again. After successful installation of Windows 11, reinstall your preferred security solution.
- Use SetupDiag Tool for Detailed Diagnostics: Visit
microsoft.com/en-us/windows/windows-11/setupto download and run the SetupDiag tool. This utility provides detailed logs and identifies specific failing drivers. - Check Registry Key: Inspect the registry key at
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\PnpManager\DriverStore. Ensure that all driver entries are up-to-date and compatible with Windows 11. - Run PowerShell Commands for Detailed Analysis: Execute these commands to gather more information:
Get-WinEvent -LogName "Setup" | Where-Object {$_.Message -like "*0xC1900101*"} | Format-Table TimeCreated, ProviderName, Id, MessageGet-MgDeviceManagementManagedDevice -Filter "deviceEnrollmentType eq 'windowsAutoEnrollment'"
Note: Be cautious when modifying registry keys or uninstalling critical software like antivirus solutions. Incorrect changes can render your system unstable and unbootable.
Error Code Variants
| Error Code | Description |
|---|---|
| 0xC1900101-0x30018 | Driver failure during the first boot phase after upgrade. This is distinct from 0x20017 as it occurs post-upgrade. |
| 0xC1900101-0x4000D | Driver failure during migration of user settings and data. Unlike the Safe OS phase, this happens later in the upgrade process. |
Verification
To verify that the issue has been resolved, attempt another upgrade from Windows 10 to Windows 11 without encountering any errors related to driver conflicts (0xC1900101). Check for successful entries inC:\Windows\Panther\setupact.log indicating a clean installation process. Additionally, confirm that the system boots normally and all critical drivers are loaded correctly.
Prevention
To prevent recurrence of this issue, implement policies to ensure all devices have their drivers updated before attempting any major OS upgrades. Use Intune or another MDM solution to push out driver updates automatically. Also, consider setting up a baseline configuration that includes the latest compatible drivers and firmware for your hardware fleet.
TIP: Utilize the
This guide should provide a comprehensive approach for sysadmins encountering the 0xC1900101 error during Windows 11 upgrades, ensuring they have all necessary steps and resources at hand.microsoft.com/en-us/windows/windows-11/setup page to stay updated on any new tools or scripts Microsoft releases specifically designed to help with Windows 11 upgrades.