No symbols available from MS for Creators Update 1703 (15063.13)?


  1. Posts : 2
    Windows 10 Pro x64 (10.0.15063.138)
       #1

    No symbols available from MS for Creators Update 1703 (15063.13)?


    Has anyone been able to download symbols from the MS symbol server for the public release of Creators Update 1703 (build 15063.13)?

    I've posted this at MSDN but so far no answers. Am I missing something?

    Soon after upgrading this week from 1607 to 1703 (via the Upgrade Assistant) I got a BSOD, and prepared to investigate with WinDbg. But it kept saying that symbols weren't available for ntoskrnl.exe. I also tested downloading symbols for it using SymChk:
    Code:
    C:\Program Files (x86)\Windows Kits\10\Debuggers\x64>symchk.exe /v c:\windows\system32\ntoskrnl.exe /s srv*f:\symbols*http://msdl.microsoft.com/download/symbols 
    [SYMCHK] Searching for symbols to c:\windows\system32\ntoskrnl.exe in path srv*f:\symbols*http://msdl.microsoft.com/download/symbols
    DBGHELP: Symbol Search Path: srv*f:\symbols*http://msdl.microsoft.com/download/symbols
    [SYMCHK] Using search path "srv*f:\symbols*http://msdl.microsoft.com/download/symbols"
    DBGHELP: No header for c:\windows\system32\ntoskrnl.exe.  Searching for image on disk
    DBGHELP: c:\windows\system32\ntoskrnl.exe - OK
    SYMSRV:  BYINDEX: 0x1
             f:\symbols*http://msdl.microsoft.com/download/symbols
             ntkrnlmp.pdb
             854C263917E4437F8014205806E2FBC01
    SYMSRV:  UNC: f:\symbols\ntkrnlmp.pdb\854C263917E4437F8014205806E2FBC01\ntkrnlmp.pdb - path not found
    SYMSRV:  UNC: f:\symbols\ntkrnlmp.pdb\854C263917E4437F8014205806E2FBC01\ntkrnlmp.pd_ - path not found
    SYMSRV:  UNC: f:\symbols\ntkrnlmp.pdb\854C263917E4437F8014205806E2FBC01\file.ptr - path not found
    SYMSRV:  HTTPGET: /download/symbols/index2.txt
    SYMSRV:  HttpQueryInfo: 80190194 - HTTP_STATUS_NOT_FOUND
    SYMSRV:  HTTPGET: /download/symbols/ntkrnlmp.pdb/854C263917E4437F8014205806E2FBC01/ntkrnlmp.pdb
    SYMSRV:  HttpQueryInfo: 80190194 - HTTP_STATUS_NOT_FOUND
    SYMSRV:  HTTPGET: /download/symbols/ntkrnlmp.pdb/854C263917E4437F8014205806E2FBC01/ntkrnlmp.pd_
    SYMSRV:  HttpQueryInfo: 80190194 - HTTP_STATUS_NOT_FOUND
    SYMSRV:  HTTPGET: /download/symbols/ntkrnlmp.pdb/854C263917E4437F8014205806E2FBC01/file.ptr
    SYMSRV:  HttpQueryInfo: 80190194 - HTTP_STATUS_NOT_FOUND
    SYMSRV:  RESULT: 0x80190194
    DBGHELP: ntoskrnl - no symbols loaded
    [SYMCHK] MODULE64 Info ----------------------
    [...]
    [SYMCHK] ------------------------------------
    SymbolCheckVersion  0x00000002
    Result              0x00010001
    DbgFilename         ntoskrnl.dbg
    DbgTimeDateStamp    0x00000000
    DbgSizeOfImage      0x00000000
    DbgChecksum         0x00000000
    PdbFilename         ntkrnlmp.pdb
    PdbSignature        {854C2639-17E4-437F-8014-205806E2FBC0}
    PdbDbiAge           0x00000001
    [SYMCHK] [ 0x00000000 - 0x00010001 ] Checked "c:\windows\system32\ntoskrnl.exe"
    SYMCHK: ntoskrnl.exe         FAILED  - ntkrnlmp.pdb mismatched or not found
    
    SYMCHK: FAILED files = 1
    SYMCHK: PASSED + IGNORED files = 0
    (I get the same results whether I use http:// or https:// for the symbol server URL.)

    I tried the manual symbol download package for version 1703 from here:
    https://developer.microsoft.com/en-us/windows/hardware/download-symbols
    but it is for a different build (15063.0?).

    Am I missing something?

    Thanks,
    JW
    Last edited by JD330; 10 Apr 2017 at 13:18. Reason: Fix line
      My Computer


  2. Posts : 2
    Windows 10 Pro x64 (10.0.15063.138)
    Thread Starter
       #2

    Installed the cumulative update, which took the build to 15063.138. No symbols for this build either...
      My Computer


  3. Posts : 83
    Windows 10 Professional
       #3

    JD330 said:
    Installed the cumulative update, which took the build to 15063.138. No symbols for this build either...
    I am having the same issue. All my debugger analyses say that .dmps are corrupt because "Kernel symbols are WRONG" for the .dmp files.
      My Computer


  4. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #4

    According to the MS web site: Download Windows Symbol Packages the 15063 symbols should be in the download:

    Windows 10, version 1703 and Windows Server 2016 symbols
    The packages released in April of 2017 contain the full set of symbols required to debug the following: Windows 10, Windows 10 Enterprise, Windows Server 2016, Standard, Windows Server 2016 Datacenter, Windows Storage Server 2016 Workgroup, Windows Storage Server 2016 Standard, Windows Server 2016 Essentials, and Microsoft Hyper-V Server 2016.



    Downloading now, will see what I get and post results here.

    Edit: It's for 15063.0.

    Edit#2: Still have symbol problems with a 15063.13 dump.
    Last edited by Ztruker; 13 Apr 2017 at 11:05.
      My Computers


  5. Posts : 83
    Windows 10 Professional
       #5

    Ztruker said:
    According to the MS web site: Download Windows Symbol Packages the 15063 symbols should be in the download:

    Windows 10, version 1703 and Windows Server 2016 symbols
    The packages released in April of 2017 contain the full set of symbols required to debug the following: Windows 10, Windows 10 Enterprise, Windows Server 2016, Standard, Windows Server 2016 Datacenter, Windows Storage Server 2016 Workgroup, Windows Storage Server 2016 Standard, Windows Server 2016 Essentials, and Microsoft Hyper-V Server 2016.



    Downloading now, will see what I get and post results here.

    Edit: It's for 15063.0.

    Edit#2: Still have symbol problems with a 15063.13 dump.
    That is unfortunate. I was going to try installing those and see if it helped. Hopefully Microsoft updates their symbols post haste. It's difficult to help with bluescreen debugging if I cannot fully utilize the WinDbg tools and have to guess based on BugCheck codes.
      My Computer


  6. Posts : 459
    Windows 8&10
       #6

    I am getting the same errors on the dump files my system generated. I have the latest Windbg and the manual install of the 15063 symbols. It is like the dump files are corrupt or possibly not yet available for the normal install.

    The utility works fine on a 14393 dump file so I am waiting for someone with the new build to supply a dump file from that version.
      My Computer


 

  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 12:56.
Find Us




Windows 10 Forums