Win11 24H2 upgrade via Intune failed, wont retry

Question

I'm using WUfB and I pushed a 24H2 FeatureUpdate policy to devices. It installed fine but on one device in particular it [presumably] failed - given it's still on Win10 (I haven't been able to obtain logs yet unfortunately) - but regardless it now won't retry or even show Win11 as available in Windows Update UI.

As background, the update modified the Boot Manager to show Win11 as a boot option, which we are seeing on a few devices which have attempted to move to 24H2. That's a separate frustration, and I have since cleaned up Boot Manager and cleaned up prior Windows Update folder/files (eg $Windows.~BT). Just thought i would mention it.

I have also :

• cleared the WUfB policies to confirm Windows Update is still working, which it is (using default/direct config) as i saw it had new preview updates it was able to install. So WuAgent appears fine. Resync'd the Intune/WUfB policies back and still no Win11.
• run HwReadiness to confirm hardware is compatible.

Any ideas why this isn't re-offered? Thanks.

Answer 1

@dridley Thanks for posting in our Q&A.

For this issue, it is suggested to refer to the following article to confirm whether the Intune policy has been successfully deployed to the target device.

https://techcommunity.microsoft.com/t5/intune-customer-success/support-tip-troubleshooting-windows-10-update-ring-policies/ba-p/714046

For feature update policy, if the device is not updated to windows 11 24H2, please look into the feature update report to get more information.

https://learn.microsoft.com/en-us/mem/intune/protect/windows-update-reports#use-the-windows-10-feature-updates-organizational-report

Hope the above information can help.

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

It was actually this key because of 2x failed attempts (due to incompatibility with RSAT tools that were installed under win10): HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\OSUpgrade\Rollback /v Count /t REG_DWORD