Windows 10: 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*Symbol information [SYMCHK] Searching for symbols to c:\windows\system32\ntoskrnl.exe in path srv*f:\symbols*Symbol information DBGHELP: Symbol Search Path: srv*f:\symbols*Symbol information [SYMCHK] Using search path "srv*f:\symbols*Symbol information" 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*Symbol information 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[/quote] (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

:)

 

error 0x8024a105 in Windows 10 update

I have the update of the latest version creators update version 1703 build 15063.13

 

Microsoft and other products update problem in Windows 10 Creators update

Was Win10 1703 (AKA Win10 Creators Update) offered & installed via Windows Update or did you choose to install it manually?

 

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.

 

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.

• Windows 10, x64 retail symbols
• Windows 10, x86 32-bit retail symbols

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.

 

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.