New
#1
What WU Methods actually write the Update History in Win 10/11
All
Been reviewing different "methods" to better manage Windows updates for a small office layout that I manage. There are a couple of servers along with about a dozen Win 10/11 workstations.
For the last several years - I stood up a WSUS server and it's been fine, but I am starting to wonder about the longer term as it seems that MS has long since given up on this.
My layout is too small for InTune and definitely not a candidate for something like Software Center/Configuration Manager. But not small enough to just let users click "Check for Updates" on a non-managed Windows Update on the workstations.
I am now testing ManageEngine Endpoint Central and Powershell scripting using PSWindowsUpdate (which is actually quite good).
But my question today revolves around the OS actually "recording" what updates have been applied to a specific machine - the data that usually appears under "Settings->Windows Update->Update History.
When I install updates via WSUS - there is a full history entry for each update - just as would appear if I did the update manually by clicking "Check for Updates->Install".
When I install updates via ManageEngine Endpoint Central - there is a "basic" entry for each update - listing something like (Security Update KB5043226) or similar. Not as good as the MS entry but better than nothing.
Finally - when I install updates via Powershell scripting using PSWindowsUpdate - there is nothing at all in the Update history area. I am assuming that the system knows it is up to date - but I have no way of confirming this.
Knowing what has been installed to a machine is valuable but I am wondering if anyone knows what actually process does the "updating" of this Update History database when it records a specific update installation.
Cheers
Sonic.