Windows Office Hours: September 18, 2025

Hi, is there a reason why the csp doc for the servicing channel 
Update Policy CSP | Microsoft Learn
descriptions for the different values is still showing the old servicing names 
Windows Insider build - Fast
Windows Insider build - Slow

instead of the dev/canary

thks

Hi, what could explain that changing something as simple as the 'Servicing channel' took more than 2 days to apply on my device?

The MDM report was showing that it was at the new setting, but it was still on the old servicing channel until it finally changed after two days to the Dev channel.

thks in advance

The release of Windows 11 25H2 was delayed for the 'Windows Insider - Release Preview' Servicing Channel. We usually see OS releases around May/June each year - 25H2 only came through a couple of weeks ago on that particular channel.
With this in mind, will the release of 25H2 to the 'General Availability' Servicing Channel also be delayed? This usually comes through around November time each year.

Just getting an idea on timelines for when we'll need to go through our usual ringed approach for end user testing, apps etc etc

As Intune does not natively supportive W11 Multi-App kiosks, will free extended support be offered for the W10 Multi-App ones we're currently running when W10 goes EOL mid-Oct?

If you have a mix of W11 computers (23H2, 24H2 and 25H2) in a group assigned to a Windows Update policy with hotpatching enabled, does it cause any issues? Hoping it's clever enough to only hotpatch the 24H2+ computers?

Autopilot question - I wonder if you could give more detail around the status of being able to apply Quality Updates during OOBE.

We saw the toggle appear in the ESP config and done some initial testing. There was a new "Checking for Windows Updates" screen that appeared during the User config part of OOBE/AP, but it didn't apply anything. Once landed in Windows, there were a bunch of Updates available to download/install within Windows Update Settings, so it had done some sort of check as the WUfB policies hadn't kicked in from Intune yet and taken over, but didn't install anything.

Further reading suggests that this configuration part of Autopilot has now been paused?? Having devices fully up to date before they hit the Windows desktop is a no brainer, even if it does slow down the user provisioning process. Once it's back up and running, are there plans to be able to built this process into the device provisioning/pre-provisioning stages? Having it fully updated before it even sees a user would be the icing on the cake.

Also, is it this registry setting that it's trying to set to allow updates to apply during OOBE?

HKLM\SOFTWARE\Microsoft\Windows\Autopilot\EnrollmentStatusTracking\Device\Setup\Policy\InstallQualityUpdates - with a DWORD value of 1

Thanks