How to Bypass Windows Upgrade Blocks by Removing the “RedFlag” Registry Key |Powershell

If you’ve been checking Windows Update hoping to see the latest version of Windows 11, but you’re met with a “This PC doesn’t meet requirements” message—despite having modern hardware—you might be a victim of a Safeguard Hold or a stale RedFlag. To resolve this issue, you may need to perform an upgrade to bypass these blocks.

In this guide, we’ll explain what the RedFlag registry value is and provide a PowerShell script to clear it so you can force Windows to re-evaluate your PC’s eligibility for an upgrade and successfully install the latest version.

What is the “RedFlag” in Windows?

Windows uses a background service called the Microsoft Compatibility Appraiser to scan your system for hardware and software issues. When it finds a “Hard Block” (something that would cause a crash or failed installation), it writes a value named RedFlag into your Registry.

As long as this flag exists, Windows Update will “shield” your PC from the upgrade, even if you’ve since updated your drivers or fixed the underlying issue.

The Registry Path

The flag is typically hidden deep within the registry here: HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\TargetVersionUpgradeExperienceIndicators

Under this path, you will see folders like GE24H2 or NI22H2. Inside those folders, a RedFlag value of 1 means “Stop: Do not upgrade.”

Automating the Fix with PowerShell

Manually hunting through the registry is tedious. We can use PowerShell to find every instance of a RedFlag across all targeted Windows versions and delete them.

Note: You must run this script as an Administrator.

# PowerShell Script to Clear Windows Upgrade RedFlags
# Run as Administrator

$regPath = "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\TargetVersionUpgradeExperienceIndicators"

if (Test-Path $regPath) {
    $subKeys = Get-ChildItem -Path $regPath
    foreach ($key in $subKeys) {
        if (Get-ItemProperty -Path $key.PSPath -Name "RedFlag" -ErrorAction SilentlyContinue) {
            Write-Host "Removing RedFlag from $($key.PSChildName)..." -ForegroundColor Yellow
            Remove-ItemProperty -Path $key.PSPath -Name "RedFlag" -Force
        }
    }
    
    Write-Host "Triggering a fresh compatibility scan..." -ForegroundColor Cyan
    Start-Process -FilePath "CompatTelRunner.exe" -ArgumentList "-m:appraiser.dll -f:DoScheduledTelemetryRun"
    
    Write-Host "Success! Restart your PC." -ForegroundColor Green
} else {
    Write-Host "Registry path not found." -ForegroundColor Red
}

What Happens After Running the Script?

1. The Block is Lifted: The script removes the “No” signal from your registry.
2. The Appraiser Runs: The command CompatTelRunner.exe tells Windows to look at your hardware right now instead of waiting for the weekly scheduled scan.
3. The Verdict: * If your PC is actually compatible, Windows Update should eventually offer the upgrade.
   • If your PC still has a hardware issue (like no TPM 2.0), the RedFlag will reappear.

Warning: Use with Caution

Removing the RedFlag is a way to bypass Microsoft’s “SafeGuards.” If Microsoft has blocked your PC because of a known bug with your specific SSD or processor, forcing the upgrade could lead to system instability or data loss. Always back up your data before attempting a major OS upgrade.

Is your PC still blocked after running the script? Drop a comment below with your RedReason value, and we’ll help you figure out which hardware component is causing the hold!

Force a Re-Scan for the Newest Version

If the device doesn’t even have a folder for GE24H2 (the 24H2 code name) in that registry path, it means the compatibility appraiser hasn’t even tried to check for the latest version yet. Run this as Administrator to force it to look for the latest version:

DOS

CompatTelRunner.exe -m:appraiser.dll -f:DoScheduledTelemetryRun

Note: This can take 5–10 minutes to finish in the ba