Forum Discussion
Unable to deploy out of band update 26200.7628
Hello, I need to deploy OOB 26200.7628 on our computers. We use deployment rings. The 2026.1 OOB update appeared in Releases on January 24. I created an expedite policy with a group of users I want to target with this update (with a restart within 0 days). But nothing has happened since Monday, everyone is still on 26200.7623. Where am I going wrong? Thank you.
2 Replies
- JackjanCopper Contributor
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.
- RyanSteele-CoVIron Contributor
Unfortunately, the Expedited Updates feature has never worked well, for me or many others: Did expediting the 2024-08 Quality Updates fail for anyone else? | Microsoft Community Hub
Recently, the issues seem to be less severe than they were initially, at least on Windows 11 24H2. I can't speak for earlier versions as I am only testing the feature on a small handful of 24H2 workstations every month to check the status.
I can tell you that I deployed the 2026.1 OOB update to my group of four test machines on Friday, January 23, with the enforced reboot set to one day. These machines are powered on and connected to the internet all the time, and the update just finished installing on the last of those machines last night. Two more completed overnight on the evening of the 26th, and one completed on the evening of the 25th. So an update that should have installed and forced a reboot within one day ended up taking between two and five days. (Oh, and the "Windows 10 and later expedited updates" report still says the last of those machines to update is in the "Offer ready" status.)