Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

Windows Update Reboot Needed collection

I posted a question during this week's PDQ&A about the Needs Reboot column in PDQ Inventory. My issue is that Windows Defender ATP creates a lot of pending file rename operations, triggering the Needs Reboot flag multiple times per day, and thus rendering it not-useful.

These happen multiple times per day

This makes even fully-patched, latest-build PCs seem desperate to reboot.

These computer are all running the latest build

I wanted to know if it's possible to limit the Needs Reboot column to only show me the computers that need to reboot to apply Windows Updates. These are the users who don't celebrate Patch Tuesday, and I need to hound them to get right with Security. The file rename operations can wait.

Thanks to this article, I figured out that the Needs Reboot column is an combination of multiple registry keys. I added the one I wanted, HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired, to the list of scanned registry keys in my default, twice-daily scan and created a new dynamic collection called Windows Update Reboot Needed.

Windows Update Requires Reboot Collection

I wouldn't mind seeing that Needs Reboot column tweaked, because it's easy to find, but this workaround is getting me closer to my goal.

0

Comments

0 comments