Please allow ads on our site
Kindly log in to use this feature. We’ll take you to the login page automatically.
LoginGetting sensible information out of Windows Update log
General Tech Bugs & Fixes 3 years ago
User submissions are the sole responsibility of contributors, with TuteeHUB disclaiming liability for accuracy, copyrights, or consequences of use; content is for informational purposes only and not professional advice.
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.
Similar Forum
Explore Other Libraries
Online Exams
Question Bank
Career News
Feeds
Full Forms
Dictionary
Interview Question
Gigs
Quotes
Lyrics
Videos
Courses
Blogs
Tutorials
Forum
Educators
Corporates
Tools
Please allow ads on our site
Kindly log in to use this feature. We’ll take you to the login page automatically.
Login
manpreet![Tuteehub forum best answer]()
Best Answer
3 years ago
I'm parsing
history.logfrom 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-WindowsUpdateLogPowerShell 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?