Home › Windows 11 › 0xC1900200

Windows 11 · 0xC1900200 · Windows 10 22H2

Windows 11 Upgrade Error 0xC1900200 - Windows 10 22H2

Error due to hardware incompatibility; fix by enabling TPM 2.0, Secure Boot and ensuring UEFI mode.

Error Details

FactValueSourceNote
Exact error stringMOSETUP_E_COMPAT_CHECK_FAILEDEvent Viewer > Windows Logs > Application-> Event ID 5
Affected build rangeWindows 10 22H2Setuperr.log
Registry key involvedHKLM:\SYSTEM\Setup\MoSetup\VolatileRegistry Editor-> CompatCheckResult
Relevant service/endpoint URLaka.ms/cpulistMicrosoft Docs
Log line signatureMOSETUP_E_COMPAT_CHECK_FAILEDC:\Windows\Panther\setuperr.log

Log Files to Check

What This Error Actually Means

The error code 0xC1900200, specifically MOSETUP_E_COMPAT_CHECK_FAILED, indicates that during a Windows 11 upgrade attempt from an affected build of Windows 10 (such as version 22H2), the system's hardware or firmware does not meet the minimum requirements for running Windows 11. This error is raised by Microsoft's setup process when it detects incompatibilities such as missing TPM 2.0, insufficient RAM, unsupported CPU architecture, or other critical configuration issues that prevent a smooth transition to Windows 11.

Affected Versions and Scope

This specific error impacts users attempting to upgrade from Windows 10 version 22H2 to Windows 11. It does not affect systems running earlier versions of Windows 10 or other operating systems such as Windows Server editions, nor will it occur on devices that are already running Windows 11. The scope is limited to those who have attempted the upgrade process and encountered hardware incompatibilities.

Where To Look First: Logs and Event IDs

To diagnose this issue, sysadmins should first look at the following log files: The setuperr.log file will contain an entry with the error code 0xC1900200, and searching for 'MOSETUP_E_COMPAT_CHECK_FAILED' within this log can provide additional context. The compat.xml file lists specific hardware or software requirements that were not met during the upgrade attempt. Additionally, Event Viewer > Windows Logs > Application will contain an event with ID 5 from source 'Microsoft-Windows-WindowsUpdateClient', which also includes the error code 0xC1900200. This log entry is crucial for understanding why the compatibility check failed.

Root Causes

There are several root causes that can lead to this error, each requiring a distinct approach to resolve:

TPM 2.0 Not Enabled or Present

The most common cause is an absence of TPM (Trusted Platform Module) version 2.0 on the system. This can be verified using tpm.msc, which opens the TPM Management snap-in, or through PowerShell with: Get-WmiObject -Namespace 'root\cimv2\security\microsofttpm' -Class Win32_Tpm | Select-Object IsActivated_InitialValue,IsEnabled_InitialValue,SpecVersion The output should show TPM version 2.0 and both activation and enablement status as true.

Insufficient CPU or RAM Requirements

Another common issue is an unsupported processor architecture or insufficient RAM (minimum of 4 GB required). The current CPU can be checked via winver, while the amount of installed RAM can be verified using: (Get-PhysicalMemory | Measure-Object -Property Capacity -Sum).Sum /1GB This PowerShell command returns the total system memory in gigabytes.

Incompatible Boot Mode or Secure Boot Disabled

The system must boot in UEFI mode with Secure Boot enabled. This can be checked via msinfo32.exe, looking for BIOS Mode = UEFI and SecureBoot State = On, or using PowerShell: Confirm-SecureBootUEFI

Fix Procedure

To resolve the issue of 0xC1900200 (MOSETUP_E_COMPAT_CHECK_FAILED), follow these steps:
  1. Enable TPM 2.0: Restart the system and enter UEFI firmware settings by pressing F2 or DEL during boot-up. Navigate to Security > TPM Device or Advanced > PCH-FW Configuration > PTT (Intel) or fTPM (AMD), set it to Enabled, save changes, and restart.
  2. Enable Secure Boot: Within UEFI firmware settings, go to Boot > Secure Boot = Enabled; also ensure Boot Mode = UEFI. If the system was previously in Legacy mode, use MBR2GPT.EXE /convert /disk:0 /allowFullOS from an elevated command prompt.
  3. Check CPU Compatibility: Compare your processor against Microsoft's supported list at aka.ms/cpulist. If unsupported, a hardware upgrade is necessary.
  4. Free Disk Space: Use the Disk Cleanup tool or StorSense to remove unnecessary files. Ensure there is at least 64 GB free on the system drive.
For testing purposes only (not recommended for production), you can bypass TPM and Secure Boot checks via registry: HKEY_LOCAL_MACHINE\SYSTEM\Setup\MoSetup: LabConfig BypassTPMCheck=1, BypassSecureBootCheck=1
Bypassing TPM or Secure Boot in the registry is not supported for production environments. It may lead to security vulnerabilities.
Use Get-WmiObject -Namespace 'root\cimv2\security\microsofttpm' -Class Win32_Tpm | Select-Object SpecVersion to quickly verify TPM version without opening tpm.msc.

Error Code Variants

Error CodeDescription
0xC1900101The upgrade process encountered an unexpected error (generic failure).
0xC1900204A required component is missing or damaged.
0xC1900208The system does not meet the minimum hardware requirements for Windows 11 (similar to MOSETUP_E_COMPAT_CHECK_FAILED).

Verification

To verify that the fix has been applied successfully, check:

Prevention

To prevent recurrence of this issue, ensure that all devices meet the minimum hardware requirements for Windows 11 before initiating an upgrade. This can be enforced through Intune policies or device management baselines: By implementing these preventive measures, organizations can avoid the need to address this error during upgrade processes, ensuring smoother transitions to new operating system versions.

Sources & References

Get new error code fixes by email

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