Getting sensible information out of Windows Update log

General Tech Bugs & Fixes 2 years ago

0 2 0 0 0 tuteeHUB earn credit +10 pts

5 Star Rating 1 Rating

Posted on 16 Aug 2022, this text provides information on Bugs & Fixes related to General Tech. Please note that while accuracy is prioritized, the data presented might not be entirely correct or up-to-date. This information is offered for general knowledge and informational purposes only, and should not be considered as a substitute for professional advice.

Take Quiz To Earn Credits!

Turn Your Knowledge into Earnings.

tuteehub_quiz

Answers (2)

Post Answer
profilepic.png
manpreet Tuteehub forum best answer Best Answer 2 years ago

 

I'm parsing history.log from debian hosts to produce a csv with dates/packages/versions. After running a suite of tests in testing environment, I then update those packages on actual hosts.

I want to do the same thing for Windows Server.
I have generated a .log file using Get-WindowsUpdateLog PowerShell command but apparently, I can't get any useful info out of there, except timestamps. As far as I understood, to be able to see lines in log that actually correspond to installation sessions (packages X,Y & Z installed on this date), I need to enable verbose Windows Update Logs, but how do I do that? I also need to know the actual name of update, not ID. AFAIK, I can manually copy the Update IDs into Microsoft Update Catalog, but I'd like to avoid that. Could enabling verbose logging solve this too? Or it would be too easy?

profilepic.png
manpreet 2 years ago

Use the nice PSWindowsUpdate Powershell Module from PowerShell Gallery: link

There you have a command Get-WUHistory which does want you are looking for.


0 views   0 shares

No matter what stage you're at in your education or career, TuteeHub will help you reach the next level that you're aiming for. Simply,Choose a subject/topic and get started in self-paced practice sessions to improve your knowledge and scores.