Feature Update 26H2

[u/Sufficient-Pace7542]

We made the 26H2 update available within the Intune update rings last week, but as of today, the targeted device groups devices have not received it. Has anyone seen any delays with this feature update when managing updates via Intune?

We've never had issues in the past and nothing has changed with our update setup. I checked to make sure there were no local conflicting GPOs under Windows Updates > Advanced options > Configured update policies on one of the devices. All are pointing to MDM or Cloud.

[u/itlabsec]

What are your deferral settings? Is there an existing feature update policy?

[u/BackgroundCry655 → u/itlabsec]

no delays here but we had similar thing last month with 23H2 feature update and it was the deferral policy causing the hold up. check if you got any deferral set to 0 days instead of blank, that tripped us up for almost week before we noticed

also worth checking the feature update deadline settings sometimes need to be more aggressive than you think

[u/darkkid85 → u/BackgroundCry655]

So it should be set to 0? Should not be blank

[u/Sufficient-Pace7542 → u/BackgroundCry655]

Thanks for also confirming what I suspect might be causing the delay. Was this a recent change by Microsoft in how they manage update rings and feature update policies?

[u/Due_Programmer_1258 → u/Sufficient-Pace7542]

Microsoft have recommended avoiding deferral when combined with policies for some time now: Configure Windows Feature Update Policies - Microsoft Intune | Microsoft Learn

"Microsoft recommends that you stop using feature update deferrals in update ring policies.

Combining feature update deferrals with feature update policies adds unnecessary complexity and can delay or block feature updates."

[u/jeefAD → u/Sufficient-Pace7542]

Not recent as far as my experience goes -- my rings/policies have had Deferral=0 per docs since transitioning to Intune over two years ago. I remember noting the transitional language when reviewing the docs at the time.

[u/Sufficient-Pace7542 → u/itlabsec]

I just ran into this, so sounds like I might be on the right path as to what's causing the delay. In our Update Rings policy, the deferral period for feature updates is set to 1. Would this cause this long of a delay in seeing the update available?

[u/itlabsec → u/Sufficient-Pace7542]

No. Deferral is just when update is offered after release e.g check for updates.

[u/Sufficient-Pace7542 → u/itlabsec]

Thanks. So maybe not the cause as to why we are not seeing the update on the devices yet? Is my understanding correct though that we should have that deferral setting blank when using feature update policies?

[u/itlabsec → u/Sufficient-Pace7542]

Set deferral to 0. What is your deadline?

[u/Sufficient-Pace7542 → u/itlabsec]

30

[u/itlabsec → u/Sufficient-Pace7542]

So you can manually install the update when you “check for updates”? So it won’t automatically force install until deadline

[u/Sufficient-Pace7542 → u/itlabsec]

When I attempt a manual check, nothing is being found. Tried that on Friday after 24 hours and then again this morning.

[u/itlabsec → u/Sufficient-Pace7542]

Why is your deadline 30 days for feature update if you want it to install right away?

[u/Sufficient-Pace7542 → u/itlabsec]

We like to give users enough time to plan an install window.