Home › Windows 11 Upgrade › 0xC1900200

Windows 11 Upgrade · 0xC1900200 · Windows 10 to Windows 11

Windows 11 Upgrade Error 0xC1900200 - Windows 10 to 11

Error 0xC1900200 indicates hardware requirements not met; fix involves enabling TPM 2.0 and Secure Boot in UEFI.

Error Details

FactValueSource
Exact error stringMOSETUP_E_COMPAT_SYSREQ_BLOCKWindows Event Viewer > Setup > Operational
Affected build rangeWindows 10 to Windows 11Setupact.log
Registry key involvedHKLM\SYSTEM\Setup\MoSetup LabConfigRegistry Editor
Relevant service/endpoint URLmicrosoft.com/en-us/windows/windows-11Microsoft website
Log line signature0xC1900200 or 'SysReqBlock'C:\Windows\Panther\setupact.log

Log Files to Check

What This Error Actually Means

The error code 0xC1900200, specifically named as MOSETUP_E_COMPAT_SYSREQ_BLOCK, is raised during the Windows 11 upgrade process when a system fails to meet the minimum hardware requirements set by Microsoft. This error occurs at the compatibility check stage of the installation process and indicates that one or more critical components such as CPU, TPM (Trusted Platform Module), Secure Boot, RAM, storage capacity, display resolution, or firmware mode are not compliant with Windows 11 standards. The error is generated by the Setup.exe component during the upgrade attempt.

Affected Versions and Scope

This error affects systems attempting to upgrade from any build of Windows 10 to a version of Windows 11. It does NOT affect systems that are already running Windows 11 or those that meet all hardware requirements for direct installation without an upgrade process. The specific range of builds impacted includes every release of Windows 10, regardless of the service branch (Home, Pro, Enterprise), and any attempt to install a version of Windows 11.

Where To Look First: Logs and Event IDs

To diagnose this issue, you should first look at the logs generated during the upgrade process. The primary log files are located in C:\Windows\Panther\setupact.log, C:\$WINDOWS.~BT\Sources\Panther\setupact.log, and C:\Windows\Panther\setuperr.log. You should search for the exact error string '0xC1900200' or 'SysReqBlock'. Additionally, you can find relevant entries in the Windows Event Viewer under Setup > Operational with Event IDs 47 and 53. These logs will provide detailed information about why the upgrade process is failing.

Root Causes

CPU Not Supported by Microsoft for Windows 11

The system's CPU must be from a supported list, typically requiring an Intel Core processor of the 8th generation or later, or an AMD Zen 2 or newer. To identify this issue, check your system’s CPU model and compare it against Microsoft’s official documentation.

TPM 2.0 Not Enabled in UEFI Firmware

The TPM must be enabled and running in CRB (Chipset Root of Trust for Boot) mode rather than TIS/FIFO mode. You can verify this by entering the system's BIOS/UEFI settings, navigating to the Security or Trusted Computing section, and ensuring that 'TPM Device' is set to 'Available' or 'Enabled', and 'TPM State' is also enabled.

Secure Boot Disabled in UEFI

Ensure Secure Boot is enabled in your system's BIOS/UEFI settings under the Boot menu. This setting must be explicitly turned on for Windows 11 installation compatibility.

Less Than Minimum RAM or Storage Capacity

The system should have at least 4 GB of RAM and a minimum of 64 GB storage space available on the primary drive. You can check these requirements using PowerShell cmdlets such as (Get-CimInstance -ClassName Win32_ComputerSystem).TotalPhysicalMemory /1GB -as [int] for memory, and (Get-PSDrive C).Free for free space on the system drive.

Fix Procedure

To resolve this issue, follow these steps:
  1. Identify Non-compliant Hardware: Use the PC Health Check app (microsoft.com/en-us/windows/windows-11) to determine which hardware requirements are not met. This will provide a clear indication of what needs to be addressed.
  2. Enable TPM 2.0 in UEFI Firmware:
    1. Navigate to the Security or Trusted Computing section in your system's BIOS/UEFI settings.
    2. Set 'TPM Device' to 'Available' or 'Enabled', and ensure 'TPM State' is enabled.
  3. Enable Secure Boot:
    1. In the UEFI firmware, go to the Boot menu.
    2. Set 'Secure Boot Control' to 'Enabled'. If your system was previously in Legacy BIOS mode, you will need to convert MBR disks to GPT using MBR2GPT.exe /convert /allowFullOS.
  4. Address Insufficient RAM or Storage:
    1. Check your system's current memory and storage capacity with PowerShell cmdlets: (Get-CimInstance -ClassName Win32_ComputerSystem).TotalPhysicalMemory /1GB -as [int] for memory, and (Get-PSDrive C).Free for free space.
    2. If the system does not meet the minimum requirements, upgrade hardware components accordingly.
  5. Registry Workaround (Not Recommended):
    1. To bypass TPM/CPU checks temporarily, you can modify registry settings under HKEY_LOCAL_MACHINE\SYSTEM\Setup\MoSetup LabConfig. However, this is not recommended for production environments as it may introduce security risks.
    2. Use PowerShell to create or update the necessary keys: New-ItemProperty -Path "HKLM:\SYSTEM\Setup\MoSetup" -Name "LabConfig" -Value 1 -PropertyType DWORD
  6. Re-attempt Upgrade: After addressing all non-compliant hardware, re-run the Windows 11 installation process.
Note: Modifying TPM and Secure Boot settings can affect device security. Ensure you understand the implications before making changes.

Error Code Variants

Error Code Description Distinguishing Factors
0xC1900204 MOSETUP_E_INVALID_PRODUCT_KEY This error occurs when the product key is invalid or not recognized for Windows 11.
0xC1900208 MOSETUP_E_UPGRADE_REQUIRED This indicates that an upgrade to a newer version of Windows is required before proceeding with the installation.

Verification

To verify that the issue has been resolved, check for the absence of error codes 0xC1900200 and 'SysReqBlock' in C:\Windows\Panther\setupact.log. Additionally, you can use PowerShell cmdlets such as Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" -MaxEvents 50 to look for successful setup events. A successful upgrade will also be reflected in the Intune admin center under 'Devices > Managed Devices', showing the updated operating system version.

Prevention

To prevent recurrence of this error, implement a hardware baseline policy that enforces minimum requirements for Windows 11 across all devices. This can include setting up OMA-URI configurations in Intune such as .Device/Vendor/MSFT/Policy/ConfigurationManager/OSUpgradeRequirements to ensure compliance with TPM and Secure Boot settings, among other hardware prerequisites. By following these guidelines, you can effectively troubleshoot and resolve the 0xC1900200 error during Windows 11 upgrades, ensuring a smooth transition for your organization's devices.

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.