Event details
It would be great if updates could be scheduled in general—meaning that quality updates could, for example, be scheduled to be postponed by 3 days, then installed manually 14 days after release, and finally enforced. Drivers are a special case—it would be great if they could be scheduled for a specific day (the release date from Microsoft, just like cumulative updates), because depending on when they’re released, there are months when they come out, say, three times a week and force you to restart. Then it would be possible to schedule them similarly to quality updates. Easy as that!
- AriaUpdated
Microsoft
So you can schedule to postpone by 3 days by setting deferrals to 3 days. Then you could set deadline to 3 days and a grace period to 8 days - this would auto-download and install by day 3, but give the user 8 days to restart (we typically do not show any notifications until a user reaches pending reboot). For drivers, we are adding a capability to have those that require a reboot hold until the monthly Windows security update unless you select to have them apply early, which means you will get that behavior automatically. Hope this makes sense, let me know if you have any questions. :)
Hi Aria,
We are seeing what appears to be a widespread issue across many of our customers' Intune tenants with Windows driver updates.
A driver update reaches the "restart required" state, the device is rebooted, but after the reboot the same driver update still remains in a pending restart state. Once the grace period expires, Windows automatically forces another restart. After that restart, the grace period starts again because the driver is still reported as requiring a reboot.
We are seeing this across different tenants, hardware vendors, device models and drivers. A few examples are:
Lenovo: Dolby - SoftwareComponent - 3.30702.720.0
HP: HP - USB - 12/10/2018 12:00:00 AM - 49.0.4411.18331
Dell: Intel - Extension - 2.1.10103.24
Since the affected drivers vary by manufacturer and model, this does not appear to be related to a specific driver package or hardware vendor.
The impact is significant because users can end up in a continuous reboot cycle driven by Windows Update deadlines and grace periods. As a workaround, we may be forced to increase the grace period considerably to avoid users having to restart their devices repeatedly.
Are you aware of any recent changes, known issues, or ongoing investigations related to driver updates remaining in a pending restart state after a successful reboot?
Apparently, I'm not the only one experiencing this issue:
https://learn.microsoft.com/en-za/answers/questions/5999930/intel-extension-2-1-10103-24-reboot-loop
https://learn.microsoft.com/en-nz/answers/questions/5994825/intel-extension-update-repeatedly-appearing-intel
