Apparently windows 10 changed the windows 10 log format and you now need to run a power shell command to generate the log file as a text file that normal humans can read.<\/p>\n
Open Powershell with “Run as Administrator”
\ngive the command:<\/p>\n
Get-WindowsUpdateLog<\/p><\/blockquote>\n
Then wait until all the log files have been found and parsed and you get the PowerShell command prompt back. Below is an example.<\/p>\n
If you find that your windows update log goes back to the beginning of time and the resulting text log file is too large to read, you can temporarily move older log files from C:\\Windows\\Logs\\WindowsUpdate<\/p>\n
More details see: https:\/\/support.microsoft.com\/en-us\/help\/3036646\/how-to-read-windows-update-logs-in-windows-10-version-1607<\/a><\/p>\n
\nPS C:\\Windows\\system32> Get-WindowsUpdateLog<\/p>\n
Converting C:\\Windows\\logs\\WindowsUpdate into C:\\Users\\labadmin\\Desktop\\WindowsUpdate.log …<\/p>\n
Input
\n—————-
\nFile(s):
\n C:\\Windows\\logs\\WindowsUpdate\\WindowsUpdate.20171011.120412.263.1.etl<\/p>\n0.00%100.00%<\/p>\n
Output
\n—————-
\nDumpFile: C:\\Users\\labadmin\\AppData\\Local\\Temp\\WindowsUpdateLog\\wuetl.CSV.tmp.00000<\/p>\nThe command completed successfully.<\/p>\n
WindowsUpdate.log written to C:\\Users\\labadmin\\Desktop\\WindowsUpdate.log<\/p>\n
PS C:\\Windows\\system32><\/p><\/blockquote>\n","protected":false},"excerpt":{"rendered":"
Apparently windows 10 changed the windows 10 log format and you now need to run a power shell command to generate the log file as a text file that normal humans can read. Open Powershell with “Run as Administrator” give … Continue reading