Connection lost to target after .reload command
<p>In WinDbg: File->Symbole File Path? I set the path to: 
<code>Srv*c:\symbols*https://msdl.microsoft.com/download/symbols</code>
After this path file setting I'm trying to make this example: 
<a href="https://msdn.microsoft.com/en-us/library/windows/hardware/mt269367" rel="nofollow">https://msdn.microsoft.com/en-us/library/windows/hardware/mt269367</a>
In section 5 step 2. when I type <code>.reload /f</code> the debugger lost connect to the 
target.
If I do not set the symbol file path, WinDbg breake up also at the same point.</p>

<p>For me it seems that windbg lost the connection to the target and do not get it 
established again. Even when I reboot the target system on the VM.</p>

<p>Can someone tell me what is going on and what I'm doing wrong or why this happen??</p>

<p>I am working with VMWare Player. My host and Target OS are Windows 10 Pro.
VMWare is configured to use network in NAT.
The Echo driver is successfully installed.</p>

<p>In following you can see the WinDbg log:</p>

<pre><code>&lt;Microsoft (R) Windows Debugger Version 10.0.10586.567 AMD64
 Copyright (c) Microsoft Corporation. All rights reserved.&gt;

&lt;Using NET for debugging&gt;
&lt;Opened WinSock 2.0&gt;
&lt;Waiting to reconnect...
&lt;Connected to target 192.168.2.107 on port 50000 on local IP 192.168.2.107.&gt;
&lt;Connected to Windows 10 10586 x64 target at (Sat May 14 22:41:26.873 2016(UTC + 2:00)), ptr64 TRUE&gt;
&lt;Kernel Debugger connection established.&gt;

&lt;************* Symbol Path validation summary **************&gt;
&lt;Response                         Time (ms)     Location&gt;
&lt;Deferred                                       &gt;
&lt;Srv*c:\symbols*https://msdl.microsoft.com/download/symbols&gt;
&lt;Symbol search path is: &gt;
&lt;Srv*c:\symbols*https://msdl.microsoft.com/download/symbols&gt;
&lt;Executable search path is: &gt;
&lt;Windows 10 Kernel Version 10586 MP (1 procs) Free x64&gt;
&lt;Product: WinNt, suite: TerminalServer SingleUserTS&gt;
&lt;Built by: 10586.306.amd64fre.th2_release_sec.160422-1850&gt;
&lt;Machine Name:&gt;
&lt;Kernel base = 0xfffff801`68a78000 PsLoadedModuleList = 0xfffff801`68d56cd0&gt;
&lt;Debug session time: Sat May 14 22:41:25.623 2016 (UTC + 2:00)&gt;
&lt;System Uptime: 0 days 0:06:44.196&gt;
&lt;Break instruction exception - code 80000003 (first chance)&gt;
&lt;*******************************************************************************&gt;
&lt;*                                                                             *&gt;
&lt;*   You are seeing this message because you pressed either                    *&gt;
&lt;*       CTRL+C (if you run console kernel debugger) or,                       *&gt;
&lt;*       CTRL+BREAK (if you run GUI kernel debugger),                          *&gt;
&lt;*   on your debugger machine's keyboard.                                      *&gt;
&lt;*                                                                             *&gt;
&lt;*                   THIS IS NOT A BUG OR A SYSTEM CRASH                       *&gt;
&lt;*                                                                             *&gt;
&lt;* If you did not intend to break into the debugger, press the "g" key, then   *&gt;
&lt;* press the "Enter" key now.  This message might immediately reappear.  If it *&gt;
&lt;* does, press "g" and "Enter" again.                                          *&gt;
&lt;*                                                                             *&gt;
&lt;*******************************************************************************&gt;
&lt;nt!DbgBreakPointWithStatus:&gt;
&lt;fffff801`68bbfed0 cc              int     3&gt;
&lt;kd&gt; !sym noisy&gt;
&lt;noisy mode - symbol prompts on&gt;
&lt;kd&gt; .symfix&gt;
&lt;DBGHELP: Symbol Search Path: srv*c:\symbols*https://msdl.microsoft.com/download/symbols&gt;
&lt;DBGHELP: Symbol Search Path: cache*;SRV*https://msdl.microsoft.com/download/symbols&gt;
&lt;DBGHELP: Symbol Search Path: cache*;SRV*https://msdl.microsoft.com/download/symbols&gt;
&lt;kd&gt; .sympath+ C:\echo\kmdf\driver\AutoSync&gt;
&lt;DBGHELP: Symbol Search Path:cache*;SRV*https://msdl.microsoft.com/download/symbols;c:\echo\kmdf\driver\autosync&gt;
&lt;DBGHELP: Symbol Search Path:cache*;SRV*https://msdl.microsoft.com/download/symbols;c:\echo\kmdf\driver\autosync&gt;
&lt;Symbol search path is: srv*;C:\echo\kmdf\driver\AutoSync&gt;
&lt;Expanded Symbol search path is:cache*;SRV*https://msdl.microsoft.com/download/symbols;c:\echo\kmdf\driver\autosync&gt;

&lt;************* Symbol Path validation summary **************&gt;
&lt;Response                         Time (ms)     Location&gt;
&lt;Deferred                                       srv*&gt;
&lt;OK                                             C:\echo\kmdf\driver\AutoSync&gt;
&lt;kd&gt; .sympath&gt;
&lt;Symbol search path is: srv*;C:\echo\kmdf\driver\AutoSync&gt;
&lt;Expanded Symbol search path is: &gt;
cache*;SRV*https://msdl.microsoft.com/download/symbols;c:\echo\kmdf\driver\autosync&gt;
&lt;&gt;
&lt;************* Symbol Path validation summary **************&gt;
&lt;Response                         Time (ms)     Location&gt;
&lt;Deferred                                       srv*&gt;
&lt;OK                                             C:\echo\kmdf\driver\AutoSync&gt;
&lt;kd&gt; .reload /f&gt;
&lt;? Retry sending the same data packet for 64 times.&gt;
&lt;The transport connection between host and kernel debugger and target Windows seems lost.&gt;
&lt;please try resync with target, recycle the host debugger, or reboot the target Windows.&gt;
&lt;...Retry sending the same data packet for 128 times.&gt;
&lt;...Retry sending the same data packet for 192 times.&gt;
&lt;...Retry sending the same data packet for 256 times.&gt;
</code></pre>

<p>Regards.</p>