Intune Autopatch Reports - Expected Behavior
I utilize the Intune Autopatch Reports for Quality Updates to monitor the deployment of updates across our environment. We currently have a group of devices which have a 30-day deferral period due to the compliance/testing policy we have to follow. My Understanding is that the "Quality Update Status" Report will determine if the device is Up-to-Date based on if the device has the update that has been released to it but I am finding that all devices are marked as Not Up-to-Date even with the 2026.05 QU installed as the 2026.06 QU is not available for the devices. I am wondering if this is expected behavior or if this changed because before the changes to the reports in May (2026.05) it was showing correctly Thanks!
What Happens Outside "Active Hours?"
While looking at the features and functionality of autopatch, I'm being asked for more detailed information on behaviors related to "Active Hours", but more specifically what happens outside of active hours. (Please let me know if additional information is required to answer this) Example: It's 21:30p, the device active hours are being automatically set (05:00a to 20:00p) and a quality update is discovered and installed that requires a reboot to complete. if I'm still interacting with the host, will it try and reboot because its technically outside of active hours? Will it provide a warning or option to pause, reschedule, etc? What is the expected behavior? Does the windows host recognize that activity is occurring and wait until a specific point in time outside of active hours? How best can I explain what happens outside of active hours to the rest of the team so they will better understand expected behaviors? Thank you in advance,Quality Updates Learn More sites are not found error
I am getting an error every time I select Learn More in Update History " Quality Updates". The websites are not found. Just wondering if this is a known issue for windows insider build that I am also running now. I have attached screenshots to explain more about the issue. All the KB Articles cannot be found.
