Quantcast
Channel: WSUS forum
Viewing all articles
Browse latest Browse all 12874

Windows Update Logs are not generated properly for Windows Server 2016 build 1607

$
0
0

I am trying to get the Windows Update logs on a System with Windows Server 2016 and Windows 10 build 1607 using powershell commandlet Get-WindowsUpdateLog. However, the output that I get, has random guids as below:

1600/12/31 16:00:00.0000000 956   1608                  Unknown( 25): GUID=6ec578f9-9c46-351d-5238-568542450649 (No Format Information found).

1600/12/31 16:00:00.0000000 956   1608                  Unknown( 207): GUID=0defb9f2-be29-3d72-4390-6806b45a584c (No Format Information found).

1600/12/31 16:00:00.0000000 956   1608                  Unknown( 12): GUID=6ec578f9-9c46-351d-5238-568542450649 (No Format Information found).

1600/12/31 16:00:00.0000000 956   1608                  Unknown( 13): GUID=6ec578f9-9c46-351d-5238-568542450649 (No Format Information found).

1600/12/31 16:00:00.0000000 956   1608                  Unknown( 14): GUID=6ec578f9-9c46-351d-5238-568542450649 (No Format Information found).

1600/12/31 16:00:00.0000000 956   1608                  Unknown( 15): GUID=6ec578f9-9c46-351d-5238-568542450649 (No Format Information found).

1600/12/31 16:00:00.0000000 956   1608                  Unknown( 16): GUID=6ec578f9-9c46-351d-5238-568542450649 (No Format Information found).

1600/12/31 16:00:00.0000000 956   1608                  Unknown( 20): GUID=6ec578f9-9c46-351d-5238-568542450649 (No Format Information found).

1600/12/31 16:00:00.0000000 956   1608                  Unknown( 10): GUID=2fc03aa6-a1fa-3d0c-ba09-b8539ec28a26 (No Format Information found).

1600/12/31 16:00:00.0000000 956   1608                  Unknown( 126): GUID=2fc03aa6-a1fa-3d0c-ba09-b8539ec28a26 (No Format Information found).

1600/12/31 16:00:00.0000000 956   1608                  Unknown( 146): GUID=2fc03aa6-a1fa-3d0c-ba09-b8539ec28a26 (No Format Information found).

1600/12/31 16:00:00.0000000 956   1608                  Unknown( 57): GUID=2fc03aa6-a1fa-3d0c-ba09-b8539ec28a26 (No Format Information found).

1600/12/31 16:00:00.0000000 956   1608                  Unknown( 10): GUID=2fc03aa6-a1fa-3d0c-ba09-b8539ec28a26 (No Format Information found).

1600/12/31 16:00:00.0000000 956   1608                  Unknown( 125): GUID=2fc03aa6-a1fa-3d0c-ba09-b8539ec28a26 (No Format Information found).

1600/12/31 16:00:00.0000000 956   1608                  Unknown( 145): GUID=2fc03aa6-a1fa-3d0c-ba09-b8539ec28a26 (No Format Information found).

1600/12/31 16:00:00.0000000 956   1608                  Unknown( 185): GUID=0defb9f2-be29-3d72-4390-6806b45a584c (No Format Information found).

1600/12/31 16:00:00.0000000 956   1608                  Unknown( 194): GUID=0defb9f2-be29-3d72-4390-6806b45a584c (No Format Information found).

1600/12/31 16:00:00.0000000 956   1608                  Unknown( 241): GUID=0defb9f2-be29-3d72-4390-6806b45a584c (No Format Information found).

I connected the system to internet to update the SymCache. After connecting to the internet, few guids were resolved. However, most of the log is still unreadable.

Is there a way to resolve the entire update log without internet connection?

The size of my current SymCache folder is around 18 MB. What is the expected size of this folder?

Cross-post reference on Microsoft Answers : https://answers.microsoft.com/en-us/windows/forum/all/windows-update-logs-are-not-generated-properly-for/09479264-e1ad-4a68-b619-f752264a0926


Viewing all articles
Browse latest Browse all 12874

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>