Forum Discussion
Unable to deploy out of band update 26200.7628
Sorry, my mistake. I didn't have Windows Update Health Tools https://support.microsoft.com/en-us/topic/kb4023057-update-health-tools-windows-update-service-components-fccad0ca-dc10-2e46-9ed1-7e392450fb3a installed, I mistakenly assumed that they were pre-installed on Win 25H2. For those who have the same problem, I deployed MSI as a win32 app via Intune, as the classic installation did not work: https://www.microsoft.com/en-us/download/details.aspx?id=103324
It sounds like the Expedite Policy might be stuck in the evaluation phase, which is common with OOB (Out-of-Band) updates. First, ensure that the Windows Update Business Deployment Service has successfully synced the new release. Sometimes, a 24-48 hour delay is expected even after the policy is created.
Also, check if there are any conflicting Update Rings or GPO settings that might be overriding the expedite command. I'd recommend checking the 'Update Health' reports in the Intune portal to see if the devices are reporting any specific 'Not Applicable' or 'Pending' status codes. Sometimes a manual 'Sync' from the device side can also help kickstart the process.
Thanks for the detailed breakdown! 🙏
I’ve seen similar delays with OOB updates before, and your point about the 24-48 hour sync window is spot on. I’d also double-check for any overlapping Update Rings or GPO policies — they can silently block expedite commands.
Another trick that’s helped me in the past is a manual ‘Sync’ from the affected devices after confirming the Intune portal shows the correct update status. It doesn’t always fix it immediately, but it often pushes things along.
Really appreciate the mention of checking the 'Update Health' reports — it’s a step that’s easy to overlook but can reveal exactly why some devices are stuck in ‘Pending’ or ‘Not Applicable’.