P
pduthie_au
So, thanks Microsoft for making this a million times harder than it ever was
Completely fresh install of Server 2016 - no updates installed, nothing
get-windowsupdatelog from powershell returns this:
1601/01/01 11:00:00.0000000 848 4304 Unknown( 10): GUID=638e22b1-a858-3f40-8a43-af2c2ff651a4 (No Format Information found).
For 456 lines with only a small amount of useful information.
In case it can't get the correct Symbol files, I've downloaded the latest available symbol files for Server 2016 from here
Download Windows Symbol Packages for Debugging - Windows drivers
And used the command with the -symbolserver pointing to the UNC path to the installed files - still get the same contents.
I have several Server 2016 servers failing to install updates or access the correct WSUS server, and I would like to be able to investigate, but can't.
I've also found references to using tracefmt.exe available by downloading and installing the Windows Driver Kit - but when I install this, the file is not found in the location specified on this website
Tracefmt - Windows drivers
The only thing I can think with this tracefmt not being there is it requires Visual Studio to be installed for it to show up - the installation for the Windows Driver Kit makes reference of this saying that some tools may not be installed without Visual C++ being installed - something which I really don't want to have to do.
This is starting to bug me - something that I could debug in minutes up until Server 2012R2 was released is now flat impossible on Server 2016.
The best reference I could find to help me fix this is for the preview builds of Windows 10 but doesn't appear to work for 2016
Debugging / Viewing Windows Update Log on Windows 10 Insider Builds
Anyone have a way of doing this that works reliably and doesn't require 10 million commands (I exaggerate a little, but not much)?
Continue reading...
Completely fresh install of Server 2016 - no updates installed, nothing
get-windowsupdatelog from powershell returns this:
1601/01/01 11:00:00.0000000 848 4304 Unknown( 10): GUID=638e22b1-a858-3f40-8a43-af2c2ff651a4 (No Format Information found).
For 456 lines with only a small amount of useful information.
In case it can't get the correct Symbol files, I've downloaded the latest available symbol files for Server 2016 from here
Download Windows Symbol Packages for Debugging - Windows drivers
And used the command with the -symbolserver pointing to the UNC path to the installed files - still get the same contents.
I have several Server 2016 servers failing to install updates or access the correct WSUS server, and I would like to be able to investigate, but can't.
I've also found references to using tracefmt.exe available by downloading and installing the Windows Driver Kit - but when I install this, the file is not found in the location specified on this website
Tracefmt - Windows drivers
The only thing I can think with this tracefmt not being there is it requires Visual Studio to be installed for it to show up - the installation for the Windows Driver Kit makes reference of this saying that some tools may not be installed without Visual C++ being installed - something which I really don't want to have to do.
This is starting to bug me - something that I could debug in minutes up until Server 2012R2 was released is now flat impossible on Server 2016.
The best reference I could find to help me fix this is for the preview builds of Windows 10 but doesn't appear to work for 2016
Debugging / Viewing Windows Update Log on Windows 10 Insider Builds
Anyone have a way of doing this that works reliably and doesn't require 10 million commands (I exaggerate a little, but not much)?
Continue reading...