Running the previous build of Windows 11 or Windows 10 and the new build is not showing up for you?
Checked updates in setting with no new build available?
This might be due to policies set on your device trough Group policies or Intune set by you company admin.
If those are not interfering with your attempt to update, you might be facing a compatibility issue.
To find out what’s going on you can check the ‘redreason’ key in the registry.
Option 1: lookup the key with regedit
with registry editor navigate to
This key will have key referring to the target edition your device has checked for compatibility in this case NI22H2.
with that key selected in the navigation pane, the pane on the right should contain a key called RedReason
Option 2: use a PowerShell script
PowerShell script to pull the info without opening regedit:
$Targetversion = 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\TargetVersionUpgradeExperienceIndicators\UNV\' $TargetID = (get-itemproperty -path $Targetversion -Name CurrentTargetOS).CurrentTargetOS $TargetRRPath = ('HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\TargetVersionUpgradeExperienceIndicators\') + $TargetID $TargetRedReason = (Get-ItemProperty -Path $TargetRRPath -Name RedReason).RedReason write 'Your RedReason is:' $TargetRedReason
In the example shown above in the regedit screenshot the system partition was too full, blocking the upgrade attempt.
If you are running into this exact issue here’s the fix: Fix – Windows 11 upgrade fails with ‘We couldn’t update system reserved partition’ – TechNine
If you RedReason is none and you are still not seeing the new build offered, you can re-trigger the compatibility check by Removing the entire ‘TargetVersionUpgradeExperienceIndicators’ key with all subkeys + reboot the device.
To do this with PowerShell (requires run as admin)
Remove-Item 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\TargetVersionUpgradeExperienceIndicators\'