Windows 11 24H2 Upgrade Not Offered? Fix Missing Update Issues with CSP Policies

Windows 11 24H2 Upgrade Not Offered: Why Some Devices Are Stuck and How to Fix It

Many IT admins are hitting the same wall when trying to roll out the Windows 11 24H2 update using CSP policies in Intune or group-based deployment scripts. While some devices upgrade smoothly, others stay stuck on Windows 10 22H2 with no sign of the update — even though they meet all hardware requirements.

This post summarizes one admin’s experience and the community’s best troubleshooting insights.

---

The Problem

An IT admin attempted to upgrade a fleet of Dell laptops to Windows 11 24H2 using a CSP (Configuration Service Provider) policy — the same method they successfully used for the 21H2 → 22H2 upgrade.

However, only about 20% of the devices upgraded. The rest showed no upgrade offer, no errors, and no compatibility issues.

Key findings:

• The registry showed the policy for 24H2 was applied.
• Another registry value, CurrentTargetOs, strangely displayed “20H1”, which was never configured.
• Keys under HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate were missing.
• The Microsoft Compatibility Appraiser task ran but didn’t fix the issue.
• Devices continued to receive other Windows updates normally.
• All Dell models in the fleet were Windows 11–compatible, and no WSUS was used.

---

Community Feedback and Fixes

Several admins in the thread shared similar experiences — devices showing the same stuck behavior without clear errors or redreason logs.

The most effective fix came from users who manually created or updated registry keys to target Windows 11 24H2 directly.

Recommended Registry Fix

Add or confirm these values under:

HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate

Value Name	Type	Data
ProductVersion	REG_SZ	Windows 11
TargetReleaseVersion	REG_DWORD	1
TargetReleaseVersionInfo	REG_SZ	24H2

After setting these keys, most users reported that Windows Update immediately offered the 24H2 feature update.

---

Possible Causes

Based on discussion and testing, several root causes were proposed:

• CSP Policy Drift: Some devices may lose the Windows Update policy key due to sync inconsistencies.
• Old CurrentTargetOs Value: A leftover key (like 20H1) can confuse the update engine and prevent proper targeting.
• Intune Delay: Policy refresh intervals can delay update detection for hours or days, even if compliance appears fine.
• Driver Readiness: Dell firmware or driver updates may be staged unevenly, delaying eligibility checks.

---

Best Practices for IT Admins

1. Verify Policy Application
   • Check registry: HKLM\SOFTWARE\Microsoft\PolicyManager\current\device\Update
   • Ensure TargetVersion shows “24H2” and ProductVersion is “Windows 11.”
2. Manually Add Missing Keys
   • Use a script, Group Policy, or Intune Custom OMA-URI profile to deploy the keys above.
3. Re-run Compatibility Check
   • Task Scheduler → Microsoft\Windows\Application Experience\Microsoft Compatibility Appraiser
   • Run it manually to refresh upgrade eligibility.
4. Force Windows Update Scan usoclient StartScan or use: PowerShell.exe (New-Object -ComObject Microsoft.Update.AutoUpdate).DetectNow()
5. Monitor Logs
   • Use WindowsUpdate.log and UpdateOrchestrator logs for confirmation.
   • If still stuck, try removing stale registry keys before reapplying the policy.

---

Summary

The Windows 11 24H2 rollout exposes some hidden quirks in CSP-based deployments. Even with correct targeting, devices may silently ignore the update due to missing registry paths or mismatched target values.

The simplest and most reliable fix:
✅ Explicitly set
ProductVersion="Windows 11",
TargetReleaseVersion=1,
and TargetReleaseVersionInfo="24H2"
under the WindowsUpdate policy path.

Once applied, affected systems usually detect the feature update within a few hours.