Home › Windows 11 Upgrade › 0xC1900101

Windows 11 Upgrade · 0xC1900101 · Windows 10 22H2

Windows 11 Upgrade Fails With Error 0xC1900101 During SAFE_OS Phase - Windows 10 22H2

Driver fault during Windows PE phase or OOBE due to incompatible NVMe, GPU drivers. Use SetupDiag.exe to identify and update/remove faulty driver.

Error Details

FactValueSourceNote
Exact error string0xC1900101-0x20017setuperr.log-> DRIVER_FAULT
Affected build rangeWindows 10 22H2 to Windows 11Microsoft compatibility page
Registry key involvedHKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Boot Status DataRegistry Editor-> Check for driver status
Relevant service/endpoint URLhttps://www.microsoft.com/en-us/windows/compatibilityMicrosoft Learn-> Hardware compatibility checker
Log line signatureError: 0xC1900101-0x20017, SetupDiag.exe analysis required.setupact.log

Log Files to Check

What This Error Actually Means

The error code 0xC1900101-0x20017 is a specific failure encountered during the Windows 11 upgrade process, particularly when transitioning from Windows 10 to Windows 11. The sub-code 0x20017 indicates that a DRIVER_FAULT occurred in the SAFE_OS phase of the installation. This error typically signifies an issue with hardware drivers not being compatible or properly functioning under the new operating system environment. The component responsible for raising this error is the Setup Manager, which is part of the Windows Installer framework and manages the upgrade process from one version to another. During the transition, it checks for driver compatibility and ensures that all necessary drivers are present and correctly configured before proceeding with the installation. If a critical driver fails during this phase, the setup rolls back and logs the error.

Affected Versions and Scope

This issue affects Windows 10 builds from version 22H2 to the initial release of Windows 11. The compatibility issues arise due to changes in how Windows 11 handles hardware drivers compared to its predecessor, Windows 10. Specifically, certain NVMe controller drivers, GPU drivers (particularly those from NVIDIA's 400 series), and chipset INF packages may not be fully compatible with the new kernel of Windows 11. It is important to note that this error does NOT affect systems running earlier versions of Windows 10 or any version of Windows Server. Additionally, it does not impact devices that are upgraded from a build of Windows 10 that has already been updated to include necessary driver updates for compatibility with Windows 11.

Where To Look First: Logs and Event IDs

When encountering this error during the upgrade process, the first step is to locate the relevant logs. The setupact.log and setuperr.log files are crucial in diagnosing the issue. These can be found at C:\$WINDOWS.~BT\Sources\Panther\. Within these log files, you should look for the exact error string 0xC1900101-0x20017, which indicates a driver fault during the setup process. Additionally, inspecting the registry key at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Boot Status Data can provide further insights into the state of the system before and after the upgrade attempt. This key contains information about the boot status data that is recorded during the setup process. Event IDs 107 and 307 are particularly relevant in this context, as they indicate issues related to driver installation and compatibility during the Windows PE phase or OOBE (Out-Of-Box Experience). These events can be viewed using Event Viewer under Windows Logs > Setup.

Root Causes

NVMe Controller Driver Incompatibility

One common cause of this error is an NVMe controller driver that is incompatible with Windows 11. This issue often arises when the manufacturer has not yet released a version of their driver that supports the new OS. To identify if this is the root cause, check the setupact.log and setuperr.log files for any references to NVMe controllers or related hardware components. If you find entries indicating issues with these drivers, it's likely the source of the problem.

GPU Driver Issues (NVIDIA 400 Series)

Another frequent issue is related to GPU drivers from NVIDIA’s 400 series. These GPUs often require specific updates or patches for Windows 11 compatibility. The setupact.log and setuperr.log files will contain entries indicating problems with the NVIDIA driver during the upgrade process.

Chipset INF Package Incompatibility

The chipset INF package, which includes critical drivers for motherboard components such as USB controllers and network interfaces, can also cause this error if it is incompatible with Windows 11. This issue typically manifests when there are discrepancies between the hardware configuration and the expected driver versions.

Fix Procedure

To resolve the issue of 0xC1900101-0x20017, follow these steps:
  1. Analyze Setup Logs: Use SetupDiag.exe to analyze the setup logs located at C:\$WINDOWS.~BT\Sources\Panther\setupact.log and C:\$WINDOWS.~BT\Sources\Panther\setuperr.log. This tool will help identify the specific driver causing the issue.
  2. Update or Remove Incompatible Drivers: Once identified, update the problematic drivers to their latest versions compatible with Windows 11. If updates are not available, consider removing the driver from the upgrade process and manually installing it after the upgrade is complete.
  3. Check Microsoft Compatibility Page: Visit https://www.microsoft.com/en-us/windows/compatibility to verify that your hardware configuration meets Windows 11 requirements and that all drivers are supported.
  4. Run PowerShell Commands for Device Management: Get-MgDeviceManagementManagedDevice -Filter "deviceEnrollmentType eq 'windowsAutoEnrollment'" This command retrieves a list of devices enrolled in Intune, helping you identify which ones need driver updates or removal.
  5. Verify Driver Installation Post-Upgrade: After the upgrade is successful, use Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" -MaxEvents 50 to check for any remaining driver issues. This command retrieves recent events related to device management and can help ensure that all drivers are functioning correctly.
  6. Update Device Policies in Intune: Navigate to the Intune admin center > Devices > Configuration profiles, and update policies to enforce compatibility with Windows 11 for all managed devices.

Error Code Variants

Error CodeDescription
0xC1900101-0x20017Driver fault during SAFE_OS phase.
0xC1900101-0x4000CSystem files are corrupted or missing. This error is often seen when system files critical for the upgrade process are damaged.
0xC1900101-0x2000EInsufficient disk space on the boot volume. Ensure there is enough free space to complete the upgrade.

Verification

To verify that the fix has been successful, look for a log line in C:\$WINDOWS.~BT\Sources\Panther\setupact.log indicating that the setup process completed successfully without encountering any driver faults. Additionally, check the Intune admin center > Devices > Compliance to ensure all devices are reporting as compliant with Windows 11 requirements.

Prevention

To prevent recurrence of this issue, implement a baseline policy in your organization's device management framework that mandates regular updates for drivers and firmware. Use PowerShell cmdlets such as Get-AutopilotDevice | Where-Object serialNumber -eq $serial to automate the process of checking and updating devices before initiating an upgrade. Ensure all hardware vendors are aware of Windows 11 requirements and regularly update their driver packages accordingly. Additionally, enforce strict compliance policies through Intune or other device management solutions to prevent incompatible configurations from being deployed in your environment.
Warning: Removing critical drivers can render devices unusable until the correct drivers are reinstalled. Ensure you have a backup plan for restoring functionality.
A quick diagnostic shortcut is to use dsregcmd /status to check if the device has properly enrolled in your organization's management system, which can affect driver installation and compatibility checks during upgrades.

Sources & References

Related Guides

Get new error code fixes by email

Product-specific solutions for Intune, Autopilot, SCCM and Entra ID — straight to your inbox. No spam.