locked
Windows 2016 WSUS log file contains mainly of: (No Format Information found) RRS feed

  • Question

  • After setting up new Windows 2016 server, i got 0x8024401c error. So i wanted to look at the logfile. But when running Get-WindowsUpdateLog on Windows 2016 server, the log file contains 100% of "No Format Information found" entries.

    Is this ther any fix for this? Known issue?

    1601.01.01 01.00.00.0000000 912   1416                  Unknown( 123): GUID=44e91a30-0234-37f0-d2f9-777240b02428 (No Format Information found).
    1601.01.01 01.00.00.0000000 1464  2676                  Unknown( 12): GUID=eb73583d-5481-33b4-202d-9bb270eddffa (No Format Information found).
    1601.01.01 01.00.00.0000000 912   1696                  Unknown( 122): GUID=44e91a30-0234-37f0-d2f9-777240b02428 (No Format Information found).
    1601.01.01 01.00.00.0000000 912   2560                  Unknown( 25): GUID=6ec578f9-9c46-351d-5238-568542450649 (No Format Information found).
    1601.01.01 01.00.00.0000000 912   2560                  Unknown( 207): GUID=0defb9f2-be29-3d72-4390-6806b45a584c (No Format Information found).
    1601.01.01 01.00.00.0000000 912   2560                  Unknown( 12): GUID=6ec578f9-9c46-351d-5238-568542450649 (No Format Information found).
    1601.01.01 01.00.00.0000000 912   2560                  Unknown( 13): GUID=6ec578f9-9c46-351d-5238-568542450649 (No Format Information found).
    1601.01.01 01.00.00.0000000 912   2560                  Unknown( 14): GUID=6ec578f9-9c46-351d-5238-568542450649 (No Format Information found).
    1601.01.01 01.00.00.0000000 912   2560                  Unknown( 15): GUID=6ec578f9-9c46-351d-5238-568542450649 (No Format Information found).
    1601.01.01 01.00.00.0000000 912   2560                  Unknown( 16): GUID=6ec578f9-9c46-351d-5238-568542450649 (No Format Information found).
    1601.01.01 01.00.00.0000000 912   2560                  Unknown( 20): GUID=6ec578f9-9c46-351d-5238-568542450649 (No Format Information found).
    1601.01.01 01.00.00.0000000 912   2560                  Unknown( 38): GUID=adf11b8c-baac-3d44-1059-4f8c843b025a (No Format Information found).
    1601.01.01 01.00.00.0000000 912   2560                  Unknown( 26): GUID=adf11b8c-baac-3d44-1059-4f8c843b025a (No Format Information found).
    1601.01.01 01.00.00.0000000 912   2560                  Unknown( 11): GUID=36385f84-a58a-32a7-0b79-6a28500f3073 (No Format Information found).
    1601.01.01 01.00.00.0000000 912   2560                  Unknown( 18): GUID=cba37bd3-9a86-3c72-ec07-f2535dabed36 (No Format Information found).
    1601.01.01 01.00.00.0000000 912   2560                  Unknown( 30): GUID=ce331769-0999-3076-1158-3c91cf80ea33 (No Format Information found).
    1601.01.01 01.00.00.0000000 912   2560                  Unknown( 18): GUID=cba37bd3-9a86-3c72-ec07-f2535dabed36 (No Format Information found).
    1601.01.01 01.00.00.0000000 912   2560                  Unknown( 11): GUID=ce331769-0999-3076-1158-3c91cf80ea33 (No Format Information found).
    1601.01.01 01.00.00.0000000 912   2560                  Unknown( 18): GUID=cba37bd3-9a86-3c72-ec07-f2535dabed36 (No Format Information found).
    1601.01.01 01.00.00.0000000 912   2560                  Unknown( 30): GUID=ce331769-0999-3076-1158-3c91cf80ea33 (No Format Information found).
    1601.01.01 01.00.00.0000000 912   2560                  Unknown( 18): GUID=cba37bd3-9a86-3c72-ec07-f2535dabed36 (No Format Information found).
    1601.01.01 01.00.00.0000000 912   2560                  Unknown( 11): GUID=ce331769-0999-3076-1158-3c91cf80ea33 (No Format Information found).
    1601.01.01 01.00.00.0000000 912   2560                  Unknown( 18): GUID=cba37bd3-9a86-3c72-ec07-f2535dabed36 (No Format Information found).
    1601.01.01 01.00.00.0000000 912   2560                  Unknown( 30): GUID=ce331769-0999-3076-1158-3c91cf80ea33 (No Format Information found).
    1601.01.01 01.00.00.0000000 912   2560                  Unknown( 18): GUID=cba37bd3-9a86-3c72-ec07-f2535dabed36 (No Format Information found).
    1601.01.01 01.00.00.0000000 912   2560                  Unknown( 11): GUID=ce331769-0999-3076-1158-3c91cf80ea33 (No Format Information found).
    1601.01.01 01.00.00.0000000 912   2560                  Unknown( 18): GUID=cba37bd3-9a86-3c72-ec07-f2535dabed36 (No Format Information found).
    1601.01.01 01.00.00.0000000 912   2560                  Unknown( 30): GUID=ce331769-0999-3076-1158-3c91cf80ea33 (No Format Information found).
    1601.01.01 01.00.00.0000000 912   2560                  Unknown( 18): GUID=cba37bd3-9a86-3c72-ec07-f2535dabed36 (No Format Information found).


    Tuesday, May 23, 2017 8:46 AM

Answers

  • Hi Roy.Antonsen,

    Looks like the server needs to reach a symbol server on the internet to generate the file, please make sure you are allowed to reach the internet when you generate the file, check if the issue will be resolved with Internet connection.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, June 7, 2017 6:21 AM

All replies

  • Hi Roy.Antonsen,

    Please install the latest monthly rollup for Server 2016, check if the issue will be solved after then:

    https://support.microsoft.com/en-us/help/4018124/windows-10-update-history

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, May 24, 2017 9:09 AM
  • All uppdates/rollups is installed
    Friday, May 26, 2017 9:11 AM
  • Hi Roy.Antonsen,

    What is the version of the windows server 2016 at present?

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, June 1, 2017 6:14 AM
  • Version 1607 (OS build 14393.1198)
    Thursday, June 1, 2017 7:33 AM
  • Hi Roy.Antonsen,

    Looks like the server needs to reach a symbol server on the internet to generate the file, please make sure you are allowed to reach the internet when you generate the file, check if the issue will be resolved with Internet connection.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, June 7, 2017 6:21 AM
  • Also Having an identical problem with the same build. I have also tested with the following commands:

    Get-WindowsUpdateLog -SymbolServer <Local Path>

    Get-WindowsUpdateLog -SymbolServer https://msdl.microsoft.com/download/symbols

    Where the local path is the download location for "Windows 10, version 1607 and Windows Server 2016 Symbols" and the URL can be accessed.

    I have also tried clearing the cache by deleting contents of the %localappdata%\Temp\WindowsUpdateLog folder



    Wednesday, June 7, 2017 2:32 PM
  • Hi Roy.Antonsen,

    Just to check if the above reply could be of help? If yes, you may mark useful ones as answer, if you have other concerns, welcome to feedback.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, June 9, 2017 3:18 AM
  • Having this same issue here. Build 14393.1198. That logfile is useless once generated. No issues accessing the symbol server. I can wipe out the SymCache and watch it repopulate when running the cmdlet with the -symbolserver parameter pointed at the MS symbol URL. 

    Once again, Microsoft has left us high and dry with their fancy Get-WindowsUpdateLog cmdlet. Can't say I'm surprised!
    Wednesday, June 14, 2017 9:24 PM
  • Same problem here: Hello Microsoft?
    Thursday, November 23, 2017 1:10 PM
  • Same problem.  Help!
    Friday, December 8, 2017 2:11 PM
  • I had the same problem in Windows 2016(Version 1607),Now I fixed it;

    First:Download and install the KB4132216

    Then:Download the lastest monthly security patch and reboot

    Last:
    1> Remove the bad client from WSUS console.
    2> Run WSUS Server Cleanup Wizard.
    3> Modify WSUS IIS WSUSPool Private Memory to 0.
    4> On the client, fun following script in the elevated CMD.
    net stop bits
    net stop wuauserv
    reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v AccountDomainSid /f
    reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v PingID /f
    reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientId /f
    reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientIDValidation /f
    rd /s /q "C:\WINDOWS\SoftwareDistribution"
    net start bits
    net start wuauserv
    wuauclt /resetauthorization /detectnow
    usoclient.exe startscan

    Thursday, February 14, 2019 6:18 AM