Windows Servicing through Intune

Copper Contributor

Hello. I just completed a servicing of a few pc's from 20H2 to 22H2 using the Intune Update Ring and Feature Updates. I was surprised that the entire process took only about 5 minutes from the time the PC rebooted to logging back in.  Confirmed its at 22H2 on the PC and in the console. When I do a servicing via the ISO file, it takes 45 minutes or so.  Is this normal when servicing through Intune? I figure its only downloading what it needs, does that account for the quick turnaround?

7 Replies

Hi @Disp350


You got lucky with the timing. We have recently upgraded from Win 11 21H2 to 22H2 and that took between 15-30 mins for the PC to reboot and user signs again.
I’ll tell you it was quicker than any previous build update but not 5 mins for us. I totally agree with you, it’s so much faster from manual update. 

Hope this helps!


@Moe_Kinani Hi Moe.  Thanks for the reply. I am still trying to figure out why it only takes a few minutes.  I can't get over it completing this quickly.  I was used to Servicing through SCCM that usually took an hour. Any ideas as to why it updates so quickly? I could not find any documentation from Microsoft regarding this.



Hi Phil,


Do you Delivery Optimization enabled in Intune? This is the secret sauce to increase the download bandwidth in your network. 

Answering your question about SCCM, WUFB is pushed to the PCs directly from the cloud using peer to peer technology while SCCM is provided by central servers located directly at your site. So that’s why takes more time with SCCM. Check this article about DO. 

hope this helps!


If latest cumulative update is already installed, then upgrading from 20H2 or later to 21H1 or later is simply installing Enablement Package
Use EKB KB5015684 to update to Windows 10, version 22H2
Use EKB KB5003791 to update to Windows 10, version 21H2
Use EKB KB5000736 to update to Windows 10, version 21H1
Hi abbodi1406. Thanks for the update. I did a little research in the Enablement package. If I understand, it's just activating dormant features and then gets the latest cumulative update? Thats what happened on pc's I upgraded. As soon as they went to 22H2, the November Cumulative update installed. But regardless, the version is still 22H2 now, correct? I have about 500 21H1 machines I need to update so they still get updates after it goes out of support after next weeks updates.
HI Moe. Yes, we have DO enabled. We still have some sites we manage that are remote (as in too far out to be able to get decent bandwidth). We use 1E Nomad with SCCM, so getting DO enabled was critical. And it does work very well - no growling from the network team we are using all the bandwidth!
you can check "Installed Updates" in control panel, you would see:
Feature Update to Windows 10 22H2 via Enablement Package (KB5015684)

Cumulative update is shared between all 20H2>22H2 versions