Hello, The reboot policy for Windows AutoPatching, including driver updates, is governed by the Windows Update for Business policies you set in your environment. These policies can be configured through Group Policy, MDM solutions like Intune, or Configuration Manager. The reboot deadline you’re seeing (3rd Feb 2024) doesn’t seem to match your TEST ring configuration with 0 days deadline and grace period. This could be due to the following reasons: Overlapping Policies: If you have overlapping policies, one of them might be setting a longer deadline. Make sure to check all your update rings and device configurations for conflicting settings. Default Values: If for some reason the policy isn’t correctly applied, the system might be falling back to some default values, which are usually very conservative to prevent unwanted reboots. Driver Updates Policy: Depending on your configuration, driver updates might be treated differently than regular updates. Check your policies related specifically to driver updates. Policy Sync Issues: It could be a policy sync issue, where the device hasn’t picked up the latest policies. You can force a policy sync from the “Company Portal” app or from the “Settings > Accounts > Access Work or School” page. Also, consider using tools such as “gpresult” or “rsop.msc” to view the resultant set of policies applied to the device. This might give you a clue as to which policy is setting the reboot deadline. Best Regards, Hania Lian
If the Answer is helpful, please click "Accept Answer" and upvote it.