Any way to fix up the Windowsupdate.log file to remove the 1600/12/31?


  1. Posts : 79
    10
       #1

    Any way to fix up the Windowsupdate.log file to remove the 1600/12/31?


    Every time I run the get-windowsupdatelog command to view the windowsupdate.log file, it's full of entries that state 1600/12/31 18:00:00.0000 Unknown GUID stuff. This happens on every machine I've run it on.

    Is there some way to make it not do that as the log file is mostly useless the way it is now since it's all convoluted with those entries mixed in with the actually useful entries.

    I've tried clearing out the folder and did get the prompt for the Symbol thing but it had no effect at all.

    Thanks.
      My Computer


  2. WOT
    Posts : 471
    Win 10 Pro 15063.332 (ex-Insider)
       #2

    You can clear the log history entirely and start over if you wish:

    Reset Windows Update in Windows 10
      My Computers


  3. Posts : 25,070
    10 Home x64 (21H2) (10 Pro on 2nd pc)
       #3

    Kelemvor said:
    Every time I run the get-windowsupdatelog command to view the windowsupdate.log file, it's full of entries that state 1600/12/31 18:00:00.0000 Unknown GUID stuff. This happens on every machine I've run it on.

    Is there some way to make it not do that as the log file is mostly useless the way it is now since it's all convoluted with those entries mixed in with the actually useful entries.

    I've tried clearing out the folder and did get the prompt for the Symbol thing but it had no effect at all.

    Thanks.
    What version of Windows 10? An Insider build?
    If you're using Windows 10 Insider Preview, you may not always be able to decode the Windows Update log. Public symbols are published only for certain prerelease builds. Therefore, if public symbols are not available, you may be unable to successfully decode the log.
    https://support.microsoft.com/en-gb/...0-version-1607

    Looks like you're not getting the public symbols. You may have better luck if you download the public symbols yourself.
    Download Windows Symbol Packages

    FWIW, I have no problems on 1703, os build 15063.250
      My Computers


  4. Posts : 79
    10
    Thread Starter
       #4

    No, this is a regular, Windows 10 Enterprise machine. Not a preview. Just upgraded to Anniversary edition. I'll run it again and see if it's still having issues.
      My Computer


  5. Posts : 25,070
    10 Home x64 (21H2) (10 Pro on 2nd pc)
       #5

    Kelemvor said:
    ...this is a regular, Windows 10 Enterprise machine...
    Enterprise? In a business environment? can you see this: Microsoft® Symbol Server through the firewall?
    https://msdn.microsoft.com/library/w...(v=vs.85).aspx
      My Computers


  6. Posts : 79
    10
    Thread Starter
       #6

    Yes. We don't block much as far as web traffic goes.
    When I click that link it says:
    Microsoft® Symbol Server

    Welcome to the Microsoft Symbol Server. This site is provided by Microsoft to enhance debugging by automatically retrieving symbols for various Microsoft products during a debugging session.

    The data at this site is not browseable. Instead, it is accessed by the debuggers that ship with Debugging Tools for Windows .
    For more information about how to use the Microsoft Symbol Server click here .
      My Computer


  7. Posts : 25,070
    10 Home x64 (21H2) (10 Pro on 2nd pc)
       #7

    If you can see that server then there's no obvious reason why you shouldn't be getting the symbols from it. Apparently you're not though, if every machine behaves like this. Have you tried downloading the symbols from here?
    If you prefer to download the entire set of symbols for Windows 10, Windows 8.1, Windows Server 2012 R2, Windows 8, Windows Server 2012, Windows 7, Windows Server 2008 R2, Windows Server 2008, Windows Vista, Windows Server 2003, or Windows XP, then you can download a symbol package and install it on your computer.
    https://developer.microsoft.com/en-u...wnload-symbols
      My Computers


  8. Posts : 79
    10
    Thread Starter
       #8

    It must have been something to do with the 1511 or whatever version I was on. I just reran the command now that I have anniversary installed and everything looks normal. Or else installing 1607 just flushed something out that was causing the issues. Either way, it is now fine.

    Thanks!
      My Computer


  9. Posts : 25,070
    10 Home x64 (21H2) (10 Pro on 2nd pc)
       #9

    Ah, 1511, that probably explains it. Everything changed with 1607...

    In Windows 10 Version 1607, Windows Update client uses Event Tracing for Windows (ETW) to generate diagnostic logs. This method improves performance and reduces disk space usage. However, the logs are not immediately readable as written.

    To decode the resulting ETL files and create a single, text based log file, you can run the new Windows PowerShell cmdlet Get-WindowsUpdateLog.
    https://support.microsoft.com/en-gb/...0-version-1607
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 20:56.
Find Us




Windows 10 Forums