Forum Discussion
Windows Update - Install and Restart Behavior
We are trying to roll out the Feature updates through Intune. We have been running the quality updates for quite sometime and all looks good. My understanding is that the settings that are configured...
David_Guyer
Microsoft
MicrosoftVinod,
Interesting... the screenshot you have above showed Use Deadline Settings = Not configured, so that's why I thought you weren't using the deadline settings. So, it's probably a good idea to confirm on the device that the deadline settings were configured... for example, on Windows 11 you can go to Advanced options > Configured update policies, and it will show you which ones are configured. On Windows 10, IIRC, it's at the top of the page that some settings are managed by your organization, and a link to see which ones.
The other thing I see in your original post is that you configured the Feature update policy for Immediate Start. What that means is that the update will be made available as quickly as the service is able to do so... so that the next client-initiated scan starts the update process. The amount of time it takes to complete the update is dependent on client settings and user behavior, such as deadline settings, whether the device is connected and turned on, whether the user reschedules the restart, whether settings are for auto download and install, and others... In other words, ImmediateStart != ImmediateUpdateComplete 🙂
In most cases, the download and install finishes within 24 hours of the scan for updates. What then takes the rest of the time is waiting for the restart... which is why we created the deadline settings.
I hope that helps clarify and help you find out what is happening on the device such that it's not finishing up.
-David
Interesting... the screenshot you have above showed Use Deadline Settings = Not configured, so that's why I thought you weren't using the deadline settings. So, it's probably a good idea to confirm on the device that the deadline settings were configured... for example, on Windows 11 you can go to Advanced options > Configured update policies, and it will show you which ones are configured. On Windows 10, IIRC, it's at the top of the page that some settings are managed by your organization, and a link to see which ones.
The other thing I see in your original post is that you configured the Feature update policy for Immediate Start. What that means is that the update will be made available as quickly as the service is able to do so... so that the next client-initiated scan starts the update process. The amount of time it takes to complete the update is dependent on client settings and user behavior, such as deadline settings, whether the device is connected and turned on, whether the user reschedules the restart, whether settings are for auto download and install, and others... In other words, ImmediateStart != ImmediateUpdateComplete 🙂
In most cases, the download and install finishes within 24 hours of the scan for updates. What then takes the rest of the time is waiting for the restart... which is why we created the deadline settings.
I hope that helps clarify and help you find out what is happening on the device such that it's not finishing up.
-David
Thanks David once again. We did configure the following through Settings Catalog and deployed to same set of devices
Even though it is set for deadline of 3 days, we are seeing the device getting restarted 1 day. So it's quite unpredictable when the restart is happening. Also i have a support case opened where there are few devices even after 10 days no restart happened.