0xC1900200 MOSETUP_E_COMPAT_SYSREQ_BLOCK — Windows Error Code

Q: What does the Windows error code 0xC1900200 mean?

It is the Win32 / NTSTATUS code MOSETUP_E_COMPAT_SYSREQ_BLOCK (decimal -1056505344). System does not meet minimum requirements for the Windows upgrade.

Q: How do I decode 0xC1900200 in PowerShell?

Run [ComponentModel.Win32Exception]::new(-1056505344).Message in any PowerShell session. For HRESULT-style codes, use err.exe from the Windows SDK or the WinDbg !error command.

Q: Where does Windows typically log this error?

It depends on the originating subsystem (Windows Update → %WinDir%\WindowsUpdate.log; AD/Kerberos → Security event log on the DC; BSOD → minidump under C:\Windows\Minidump; MSI → %TEMP%\msi*.log; WMI → Microsoft-Windows-WMI-Activity). Always cross-reference the timestamp and module name with the Application and System event logs.

Description

MOSETUP_E_COMPAT_SYSREQ_BLOCK (hex code 0xC1900200, decimal -1056505344) is a Windows critical-level error code in the Windows Update & Feature Updates family. Microsoft surfaces this code through the Win32 API, the Common Language Runtime, the kernel, the event log, PowerShell, command-line tools (sfc, dism, gpupdate, sc), and Windows-side applications such as Outlook, Teams, Office, and System Center.

System does not meet minimum requirements for the Windows upgrade.

This page documents what triggers 0xC1900200, the most common scenarios where it appears, the likely root causes, and a step-by-step troubleshooting workflow you can run against affected endpoints. It is intended for system administrators, MSP technicians, helpdesk engineers, and anyone diagnosing Windows behavior in a managed environment.

In-depth explanation

This is a critical-severity Windows error. It typically indicates a kernel-mode failure, an unrecoverable security violation, hardware failure, or a fatal driver bug. Treat any occurrence as a P1 incident: isolate the host, capture a memory dump if available, and pull the latest minidump from C:\Windows\Minidump for analysis.

It is part of the Windows Update / WUA error space and typically surfaces in the Settings app, WindowsUpdate.log, the CBS log, or in WSUS / Intune / Configuration Manager reports.

The code can be looked up programmatically in PowerShell with [ComponentModel.Win32Exception]::new(-1056505344).Message (for Win32 / NTSTATUS codes that map cleanly), or with net helpmsg <decimal> for the legacy decimal range. For HRESULT-style codes, decode the facility and code with err.exe from the SDK or via the WinDbg !error command.

Common causes

Corrupted Component-Based Servicing (CBS) store.
WSUS / Intune / SCCM serving the wrong update or a deprecated revision.
Insufficient free space on the system drive (Windows requires several GB free for feature updates).
Antivirus or EDR blocking wuauserv or the cbs.log writer.
Pending reboot from a previous installation locking the WinSxS store.

Troubleshooting steps

Run the official Windows Update Troubleshooter (Settings > System > Troubleshoot).

Stop the relevant services and reset the local cache:

net stop wuauserv bits cryptsvc msiserver
ren %SystemRoot%\SoftwareDistribution SoftwareDistribution.old
ren %SystemRoot%\System32\catroot2 catroot2.old
net start wuauserv bits cryptsvc msiserver

Repair the component store: DISM /Online /Cleanup-Image /RestoreHealth followed by sfc /scannow.
If a feature update fails, free up disk space (15+ GB on C:), unplug non-essential USB devices, and update or roll back the displaying drivers.
For domain-managed clients, verify GPO scoping, WSUS / Intune assignment, and check %WinDir%\WindowsUpdate.log (run Get-WindowsUpdateLog on Windows 10/11).

Decode in PowerShell

# Decode 0xC1900200 (-1056505344) in PowerShell
[ComponentModel.Win32Exception]::new(-1056505344).Message

# Or via WinDbg / err.exe (Windows SDK)
# err 0xC1900200

# Or net helpmsg (legacy decimal range only)
# net helpmsg <decimal>

Frequently asked questions

What does the Windows error code 0xC1900200 mean?

It is the Win32 / NTSTATUS code MOSETUP_E_COMPAT_SYSREQ_BLOCK (decimal -1056505344). System does not meet minimum requirements for the Windows upgrade.

How do I decode 0xC1900200 in PowerShell?

Run [ComponentModel.Win32Exception]::new(-1056505344).Message in any PowerShell session. For HRESULT-style codes, use err.exe from the Windows SDK or the WinDbg !error command.

Where does Windows typically log this error?

It depends on the originating subsystem (Windows Update → %WinDir%\WindowsUpdate.log; AD/Kerberos → Security event log on the DC; BSOD → minidump under C:\Windows\Minidump; MSI → %TEMP%\msi*.log; WMI → Microsoft-Windows-WMI-Activity). Always cross-reference the timestamp and module name with the Application and System event logs.

Is this code recoverable?

Critical-severity codes usually require kernel-level investigation (driver, hardware, system file repair). Error and warning codes are typically recoverable through the troubleshooting workflow on this page — start with the elevated-shell + log review steps.

Should I open a Microsoft support case for this?

Open a case if the error reproduces after applying the troubleshooting steps, particularly if it blocks production workloads, occurs across multiple endpoints, or is associated with a security boundary (BitLocker recovery, Kerberos failure, DCOM hardening, SmartScreen / WDAC). Have a fresh CBS log, minidump, or Get-WinEvent export ready before opening the case.