title: Force WinDbg to load pdb using `.reload` is not working
body: <p>I have a dump collected for my executable <code>App.exe</code>: <code>App.DMP</code></p>
  
  <p>Unfortunately, we didn't save the <code>.pdb</code> for this specific build, but since we have build number we could rebuild the same version and reconstruct the <code>.pdb</code></p>
  
  <p>This didn't help and I couldn't load the symbols with <code>Visual Studio</code>.</p>
  
  <p>So I tried to open the dump with <code>WinDbg</code> and force loading the should-match symbols, following these <a href="https://blogs.msdn.microsoft.com/emeadaxsupport/2011/04/10/setting-up-windbg-and-using-symbols/" rel="nofollow noreferrer">instructions</a>:</p>
  
  <pre><code>0:000&gt; !sym –noisy
  0:000&gt; .reload /f /i C:\Tests\dump-e\App.exe
  SYMSRV:  BYINDEX: 0x34
           C:\Program Files (x86)\Windows Kits\10\Debuggers\x86\sym
           App.pdb
           CEE75F0AAD5348458938777BBD4165B01
  SYMSRV:  UNC: C:\Program Files (x86)\Windows Kits\10\Debuggers\x86\sym\App.pdb\CEE75F0AAD5348458938777BBD4165B01\App.pdb - path not found
  SYMSRV:  UNC: C:\Program Files (x86)\Windows Kits\10\Debuggers\x86\sym\App.pdb\CEE75F0AAD5348458938777BBD4165B01\App.pd_ - path not found
  SYMSRV:  UNC: C:\Program Files (x86)\Windows Kits\10\Debuggers\x86\sym\App.pdb\CEE75F0AAD5348458938777BBD4165B01\file.ptr - path not found
  SYMSRV:  RESULT: 0x80070003
  SYMSRV:  BYINDEX: 0x35
           https://msdl.microsoft.com/download/symbols
           App.pdb
           CEE75F0AAD5348458938777BBD4165B01
  SYMSRV:  UNC: C:\Program Files (x86)\Windows Kits\10\Debuggers\x86\sym\App.pdb\CEE75F0AAD5348458938777BBD4165B01\App.pdb - path not found
  SYMSRV:  UNC: C:\Program Files (x86)\Windows Kits\10\Debuggers\x86\sym\App.pdb\CEE75F0AAD5348458938777BBD4165B01\App.pd_ - path not found
  SYMSRV:  UNC: C:\Program Files (x86)\Windows Kits\10\Debuggers\x86\sym\App.pdb\CEE75F0AAD5348458938777BBD4165B01\file.ptr - path not found
  SYMSRV:  HTTPGET: /download/symbols/App.pdb/CEE75F0AAD5348458938777BBD4165B01/App.pdb
  SYMSRV:  HttpQueryInfo: 80190194 - HTTP_STATUS_NOT_FOUND
  SYMSRV:  HTTPGET: /download/symbols/App.pdb/CEE75F0AAD5348458938777BBD4165B01/App.pd_
  
  SYMSRV:  HttpQueryInfo: 80190194 - HTTP_STATUS_NOT_FOUND
  SYMSRV:  HTTPGET: /download/symbols/App.pdb/CEE75F0AAD5348458938777BBD4165B01/file.ptr
  SYMSRV:  HttpQueryInfo: 80190194 - HTTP_STATUS_NOT_FOUND
  SYMSRV:  RESULT: 0x80190194
  SYMSRV:  BYINDEX: 0x36
           c:\tests\dump
           App.pdb
           CEE75F0AAD5348458938777BBD4165B01
  SYMSRV:  UNC: c:\tests\dump\App.pdb\CEE75F0AAD5348458938777BBD4165B01\App.pdb - path not found
  SYMSRV:  UNC: c:\tests\dump\App.pdb\CEE75F0AAD5348458938777BBD4165B01\App.pd_ - path not found
  SYMSRV:  UNC: c:\tests\dump\App.pdb\CEE75F0AAD5348458938777BBD4165B01\file.ptr - path not found
  SYMSRV:  RESULT: 0x80070003
  DBGHELP: Failed copying the file 'D:\Agt\Def\04\_w\36\s\App\x64\Release\App.pdb' to the cache
  DBGHELP: D:\Agt\Def\04\_w\36\s\App\x64\Release\App.pdb - file not found
  *** WARNING: Unable to verify checksum for App.exe
  *** ERROR: Module load completed but symbols could not be loaded for App.exe
  DBGHELP: App - no symbols loaded
  </code></pre>
  
  <p>Why isn't the force loading working? what is it with <code>D:</code> drive? I don't have such drive.. is it related to this GUID (CEE75F0AAD5348458938777BBD4165B01) not matching my dump? shouldn't the force cover this?</p>