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 in the update rings for the install and restart settings will be applicable for the feature updates as well. But I do
not see that is happening. We have configured the following
We assigned few devices to these policy and it has been 3 days the update has been done. Checking on the device it says
What am i missing here? The requirement is very simple that if we add the device to the policy then next day morning the feature update should be completed.
4 Replies
David_GuyerMicrosoft
Hi vinod,
The Feature update has started and completed downloading on this device, but the Windows Update client hasn't found an idle time to restart. So, the feature update policy is working. Being in Pending install for awhile can happen when there is an aggressive sleep or hibernate policy, or users shutdown devices when not working on them.
The setting that really helps ensure the update completes faster is setting the deadline. We recommend a 2 day Grace period, and a 2-3 day deadline... but you can set that to your organization's needs.
HTH,
-David- Thanks David. But we did set the deadline r and grace period. It never restarts. Those are the VM’s and laptops as well where I see the device does not go to sleep as per the logs.
- David_GuyerVinod,
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
