title: Cannot deploy windows kernel driver to virtual machine
body: <p>I'm trying to deploy a Kernel Mode Driver to a virtual machine.</p>
  
  <p>The targe machine is a virtual machine on Hyper-V (Windows 10 x64 Enterprise), with boot debugging enabled :
  <a href="https://i.stack.imgur.com/6mKTX.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/6mKTX.png" alt="enter image description here"></a></p>
  
  <p>I have setup a named pipe on COM1 serial port :
  <a href="https://i.stack.imgur.com/dvV51.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/dvV51.png" alt="enter image description here"></a></p>
  
  <p>The host machine is also a Windows 10 x64 Enterprise, running Visual Studio 2019. I have followed this "hello world" guide to setup the project <a href="https://docs.microsoft.com/en-us/windows-hardware/drivers/gettingstarted/writing-a-very-small-kmdf--driver" rel="nofollow noreferrer">https://docs.microsoft.com/en-us/windows-hardware/drivers/gettingstarted/writing-a-very-small-kmdf--driver</a> :
  <a href="https://i.stack.imgur.com/iWmQy.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/iWmQy.png" alt="enter image description here"></a></p>
  
  <p>The target device is configured as followed :
  <a href="https://i.stack.imgur.com/WLrsl.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/WLrsl.png" alt="enter image description here"></a></p>
  
  <p>The name of the VM computer is "DESKTOP-IB38LAB". Both computers are on the same workgroup and can ping each other. The both appear in the Network tab. Firewall is disabled on both computers.
  <a href="https://i.stack.imgur.com/mWfhc.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/mWfhc.png" alt="enter image description here"></a></p>
  
  <p><a href="https://i.stack.imgur.com/nYoha.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/nYoha.png" alt="enter image description here"></a>
  The status is "Unavailable", therefore the deploy fails with the message "Could not connect to the remote computer for deployment.".</p>
  
  <p>If I choose "Provision device and choose debugger settings" instead : 
  <a href="https://i.stack.imgur.com/ikPr4.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/ikPr4.png" alt="enter image description here"></a>
  <a href="https://i.stack.imgur.com/nFkDc.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/nFkDc.png" alt="enter image description here"></a></p>
  
  <p>Edit :  I forgot to mention, the step 3 on this guide (<a href="https://docs.microsoft.com/en-us/windows-hardware/drivers/gettingstarted/provision-a-target-computer-wdk-8-1" rel="nofollow noreferrer">https://docs.microsoft.com/en-us/windows-hardware/drivers/gettingstarted/provision-a-target-computer-wdk-8-1</a>) says : </p>
  
  <p>"On the target computer, run the WDK Test Target Setup MSI that matches the platform of the target computer. You can find the MSI in the Windows Driver Kit (WDK) installation directory under Remote.</p>
  
  <p>Example: C:\Program Files (x86)\Windows Kits\10\Remote\x64\WDK Test Target Setup x64-x64_en-us.msi"</p>
  
  <p>But when I installed the WDK on the target computer, I only have these in this folder : 
  <a href="https://i.stack.imgur.com/1R5KE.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/1R5KE.png" alt="enter image description here"></a></p>
  
  <p>The name doesn't really match. I have ran both.</p>
  
  <p>Note : I can bebug the target machine kernel with WinDbg using the named pipe.</p>