UpdateDavid_MSFT

@StevenKister1 @ariaupdated @AdamGell In Settings Catalog you change the Start Date, so if you set it to today, the pause auto expires 30d after today. In ~28d, you can set it to that date again and extend it further. It's intentionally like this so that you don't accidentally leave devices in a insecure state.

@ariaupdated @AdamGell @UpdatedavidM I guess my WU profile question is how can I duplicate the WU Extend option in Settings Catalog? The reason for using Settings Catalog is because of the UI limitation in the update rings. That profile fails on all devices because of the insiders option not being able to disable.

@ariaupdated We raised this a few years ago, but can the Intune update ring profile include a disabled selection for "Enable pre-release builds". The current Enable and Not Configured options cause a policy conflict when using the Settings Catalog to prevent preview builds.

Join me and my colleagues at an AMA about Application Management in Intune on Monday (Jan 26, 9:00 AM PT) ! aka.ms/AMA/ManageApps

@janson Not yet. Thank you for asking, it is something we are looking at potentially adding to AP-DP.

@UpdatedavidM Thankyou for the update. Does this feature also apply to AutoPilot V2 aka AutoPilot Device Preparation?

1/2 What’s New in Microsoft Intune: August 2025 - Microsoft Intune Blog techcommunity.microsoft.com/blog/microsoft… If you've been wondering why I've been so quiet, I've been working on several things, and What's New this month coves one of them, Windows Quality security updates during OOBE.

The doc link didn't seem to work... try this: #install-windows-monthly-security-update-releases" target="_blank" rel="nofollow noopener">learn.microsoft.com/en-us/intune/i…

Latest update. * The 11D QU and ZDP adds the setting set to disabled -more control when to roll out. * Enable updates in ESP, detailed docs are here: Set up the Enrollment Status Page in the admin center * The first update enabled for OOBE will be the 2026-1B QU on Jan 13th.

@inthecloud_247 @bdam555 Please DM me, or if you can reach me on Teams even better. We'll get logs and have this investigated. It's not expected.

@UpdatedavidM @bdam555 I thought installing updates was paused? I'm a bit confused in what is and what is not paused, cause I now have a machine which is downloading and installing updates.

@bdam555 The FE in Intune fully rolled out. What is paused is the OOBE Windows Updates page, so won't check or install updates for now.

@UpdatedavidM Trying to grok this all Only ESP APDP has no control Installs during OOBE (not during technician phase) The BE (Windows and Intune) was fully rolled out FE was partially rolled out Now it's delayed; did you rollback the BE/FE from existing customer or just paused the rollouts?

@MattWreede We'll have to balance that with the extra time spent commuting!

@UpdatedavidM With MSFTs RTO mandate coming into effect next year, maybe we could focus some vibe coding efforts onto ConfigMgr?

@arovik85 @jarwidmark Correct. Stay tuned... keep an eye on my posts, this blog, or the Intune docs for ESP for updates: techcommunity.microsoft.com/blog/Windows-I…

@jarwidmark @UpdatedavidM as I read it you are able to configure it now, but it will not have affect during OOBE yet

@nilsvanwoensel I'm excited to share that we are starting the release process now. Expect to see it in your tenant by Thursday or Friday this week!

@nilsvanwoensel Our engineers are putting the final touches. I'll post a reply on my original post once the rollout starts, hopefully pretty soon!

@ryandengstrom @JulesOfficial84 @Stevenvanbeek @WindowsUpdate @ariaupdated @IntuneSuppTeam Please DM me if you can get me any info on whom you talked to in support saying that. I'll reach out to my contacts and try to help clarify things.

@JulesOfficial84 @Stevenvanbeek @UpdatedavidM @WindowsUpdate @ariaupdated @IntuneSuppTeam Create a settings catalog profile in Intune. Search for Windows Update for Business, then select "Product Version" and "Target Release Version". Set "Windows 11" for product version and "23H2" for the target release version. Assign to a test group of devices, then to prod later.

Anyone else seeing unintended #WUfB feature updates to W11 #24H2? We have a feature update policy to hold at 23H2, and have had a handful end up on 24H2. @WindowsUpdate @ariaupdated @UpdatedavidM @IntuneSuppTeam

@ryandengstrom @JulesOfficial84 @Stevenvanbeek @WindowsUpdate @ariaupdated @IntuneSuppTeam Oh no no no! Just be sure to set Feature Update deferral in Update Rings to 0. If you set the Settings Catalog, you are stuck on that build until you remove those settings. Key thing is to Avoid Conflicts by using one method per device :-).

I wanted to share this recent Skilling snack since I regularly talk to customers that aren't aware of all the options for tracking which devices have, or need, Windows updates. This should help! techcommunity.microsoft.com/t5/windows-it-…

@eskonr If that doesn't make sense, let me know and I'll find an expert to clarify (or correct) further!

@eskonr I'm not so much an expert with WUfB reports, but I think part of the solution here is to find devices in Entra and if they aren't seen via diagnostic data, put them into the missing devices list, with this alert. In essence, solving the missing devices from the missing devices!

These will give you better understanding of devices that don't appear to be updating when Microsoft isn't receiving data needed for detailed device status and errors. This can help you to find settings, firewall, or other conflicts and getting much more useful reports!