Stuck on Windows 11 2-H2? How to Identify and Fix Update Safeguard Holds

Is your PC stuck on an older version of Windows 11 despite being fully “compatible”? Microsoft often places Safeguard Holds on devices when they detect a specific hardware or software conflict that could cause a blue screen or performance issues.

If you are waiting for the GE24H2 (Windows 11, version 24H2) update and it isn’t showing up, here is how to use the Registry and Task Scheduler to find out exactly why.

Step 1: Force a Compatibility Scan

Before checking the results, you need to make sure your PC has recently “talked” to Microsoft about its compatibility status.

1. Open Command Prompt or PowerShell as an Administrator.
2. Copy and paste the following command and press Enter: schtasks.exe /Run /TN “\Microsoft\Windows\Application Experience\Microsoft Compatibility Appraiser“
3. Wait about 5–10 minutes. This task runs in the background to re-evaluate your system against Microsoft’s current blocklist.

Step 2: Check the Registry for “Red” Blocks

Once the appraiser has finished, you can see the verdict in the Windows Registry.

1. Press Win + R, type regedit, and hit Enter.
2. Navigate to the following path:HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\TargetVersionUpgradeExperienceIndicators\XX2XH2

What to look for:

• Red Value: If you see a entry indicating “Red,” your device is officially blocked.
• Safeguard ID: Look for a multi-digit number (e.g., 52796261). This is the specific “case number” for your block.

Step 3: Troubleshooting Common Blockers

Depending on what you find in the Registry, here is how to resolve the most common issues:

Issue A: Policy Restrictions

Sometimes, a local policy is telling Windows Update to stay on a specific version.

• Check here: HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
• The Fix: If you see a value named TargetReleaseVersionInfo set to an older version (like 23H2), delete it or update it to 24H2.

Resolution

If your registry check shows values under the WindowsUpdate key, your system is likely being told to stay on an older version of Windows.

1. The “Safe” Reset Method

In the Policies hive, the only “default” is an empty key. Anything listed there is a manual restriction. To clear them:

1. Navigate to: HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
2. Delete all Values: In the right-hand pane, you may see values like TargetReleaseVersion or ProductVersion. Right-click and Delete all of them.
3. Check the ‘AU’ Subkey: Double-click the AU folder (Automatic Updates) under the WindowsUpdate key. If you see NoAutoUpdate set to 1, delete it or set it to 0.

2. The “Clean Slate” Command (PowerShell)

If you want to be sure everything is wiped and reset to Windows defaults, run this command as an Administrator. This deletes the entire policy folder; Windows will automatically recreate the folder (but empty) when it next checks for updates.

PowerShell

# WARNING: This completely removes the WindowsUpdate policy key and all subkeys.
# Use this if individual value deletion fails to clear the block.

Remove-Item -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" -Recurse -Force

Write-Host "Windows Update policy folder has been completely wiped." -ForegroundColor Red

3. Restart the Update Service

For the changes to take effect immediately without a reboot, run these commands in order:

• net stop wuauserv
• net start wuauserv

Issue B: Hardware Safeguard IDs

If you found a Safeguard ID in Step 2, Microsoft has a known issue with your hardware.

• The Fix: 1. Go to the Windows 11 Release Health dashboard.2. Search for your Safeguard ID.3. Usually, the resolution involves updating a driver (often Intel Smart Sound, Wi-Fi drivers, or specific Anti-Virus software).

Issue C: Outdated BIOS

Newer versions of Windows often require updated microcode to handle power states.

• The Fix: Visit your motherboard or laptop manufacturer’s website and install the latest BIOS/UEFI update.

Step 4: Forcing the Update (Advanced Users)

If you have fixed the drivers and the “Red” status remains, you can attempt to bypass the check, though this is not recommended unless you have a full system backup.

1. Navigate to: HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
2. Create a new DWORD (32-bit) Value.
3. Name it DisableTargetReleaseExperienceIndicator and set the value to 1.
4. Restart and check for updates.

Or

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 background.

Summary Checklist