1. Joined : Aug 2016
    S/E England
    Posts : 1,132
    10 Home x64 (1607), Pro x86 (1511 & 1607)
       18 Sep 2016 #1

    Windows update log problem in 1607


    In Can't install Windows 10 Anniversary update, stuck on build 10240 @dalchina advised...
    You could try reading the Windows update log...
    https://support.microsoft.com/en-gb/kb/902093
    ...which is good advice for the OP who was on 12040. However, being curious (and not having needed to look at it before) I thought I'd have a look at mine.

    I'm on Windows 10 Home Build 14393.187. Apparently since the Anniversary Update 1607 the only thing C:\Windows\WindowsUpdate.log contains is...
    Windows Update logs are now generated using ETW (Event Tracing for Windows).
    Please run the Get-WindowsUpdateLog PowerShell command to convert ETW traces into a readable WindowsUpdate.log.

    For more information, please visit http://go.microsoft.com/fwlink/?LinkId=518345
    So I followed the instructions and generated a WindowsUpdate.log on my Desktop - all well so far. Opening it revealed 99% of the entries were of the form:
    1601/01/01 00:00:00.0000000 988 5532 Unknown( 10): GUID=638e22b1-a858-3f40-8a43-af2c2ff651a4 (No Format Information found).
    Apparently, according to the above 'for more information...' link...

    Notes

    • If you encounter problems decoding the Windows Update log (for example, if you have multiple "GUID" entries that are displayed in the final text log), you may have to delete and then update your symbol cache. You can do this by deleting everything under the %temp%\windowsupdatelog folder.
    • Decoding the ETL files and converting them into a single textual log file requires access to the Microsoft public symbol server on the Internet. If you have Internet access, no other action is required, the powershell cmdlet will automatically download the files needed for the conversion.
    • The first time that you run the Get-WindowsUpdateLog cmdlet, you may see the Microsoft Internet Symbol Store dialog box. To use the Get-WindowsUpdateLog cmdlet, you must accept the presented license terms to enable access to the public symbols that are used by the cmdlet.
    No matter how many times I clear %temp%\windowsupdatelog I never see the Microsoft Internet Symbol Store dialog box and never get a properly decoded update log. Has anyone ever got this to work? If so, what am I doing wrong? I currently don't need to see it to debug problems, but it would be nice to know it's there if I need it.

    PS: I don't have (or want) a Microsoft Account, could that be the issue?
    Last edited by Bree; 18 Sep 2016 at 19:12. Reason: Title
      My System SpecsSystem Spec


  2. Joined : Jan 2014
    Oak Ridge TN, USA
    Posts : 23,934
    Windows 10 Pro x64
       18 Sep 2016 #2

    I think a better subject is needed for this thread because I don't know how many, including myself, will really understand what "W" is for.
      My System SpecsSystem Spec


  3. Joined : Aug 2016
    S/E England
    Posts : 1,132
    10 Home x64 (1607), Pro x86 (1511 & 1607)
       18 Sep 2016 #3

    BunnyJ said: View Post
    I think a better subject is needed for this thread...
    fixed now.
      My System SpecsSystem Spec


  4. Joined : Jan 2014
    Oak Ridge TN, USA
    Posts : 23,934
    Windows 10 Pro x64
       18 Sep 2016 #4

    Bree said: View Post
    fixed now.
      My System SpecsSystem Spec


  5. Joined : Sep 2016
    Posts : 2
    Windows 10 Anniversary Update
       22 Sep 2016 #5

    Bree said: View Post
    No matter how many times I clear %temp%\windowsupdatelog I never see the Microsoft Internet Symbol Store dialog box and never get a properly decoded update log. Has anyone ever got this to work? If so, what am I doing wrong? I currently don't need to see it to debug problems, but it would be nice to know it's there if I need it.

    PS: I don't have (or want) a Microsoft Account, could that be the issue?
    I have exactly the same behavior, and I'm logged in with a Microsoft account, so this is not the issue. I'm wondering if someone with the same build (1607) is able to get any useful message from the so formatted log, since for me it's only a list of "No Format Information found" lines.

    Regards
      My System SpecsSystem Spec


  6. Joined : Aug 2016
    S/E England
    Posts : 1,132
    10 Home x64 (1607), Pro x86 (1511 & 1607)
       30 Sep 2016 #6

    @Moris try again now. Seems to be working now after the latest update was installed. I'm now on Build 14393.222
    Cumulative Update KB3194496 for Windows 10 PC Build 14393.222
      My System SpecsSystem Spec


  7. Joined : Sep 2016
    Posts : 2
    Windows 10 Anniversary Update
       03 Oct 2016 #7

    @Bree Thank you for your tip. I just installed the latest build and now I can see all entries in Windows Update log correctly formatted.
      My System SpecsSystem Spec


  8. Joined : Jan 2016
    Green Valley, AZ
    Posts : 82
    Windows 10 (2), Win 8.1 (1), Win 7 (1)
       12 Dec 2016 #8

    Have the same problem and have the latest build v1607 b14393.479. The %temp%\WindowsUpdateLog folder has been populated. I received no license terms approval request.

    JohnD
      My System SpecsSystem Spec


 

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 00:55.
Find Us
Twitter Facebook Google+



Windows 10 Forums