Can't use windbg with Hyper-V on windows 10

I want to debug a driver, so I decided to use kernel debugging. Both the host and the VM are running windows 10.

I used the following commands on the VM to set things up:

  • bcdedit /debug on
  • bcdedit /dbgsettings SERIAL DEBUGPORT:1 BAUDRATE:19200

I then launched WinDbg with the following flags: -k com:pipe,port=\.\pipe\kmdpipe,resets=0,reconnect
but it doesn’t really connect to the virtual machine, all I get is the message:

Opened \.\pipe\kmdpipe
Kernel Debug Target Status: [no_debuggee]; Retries: [0] times in last [7] seconds.
Waiting to reconnect…

The funny thing is that I also a windows 7 machine on hyper-v and it works(although I have to restart the VM). What’s happening here?

Did you set the VM settings to route COM1 to the named pipe kmdpipe?

You can use network debugging. No need to add com port(not sure if you even can add it to generation 2 vms). Plus network debugging very easy to establish with kdnet utility - located in the same directory as windbg.

@Tim_Roberts said:
Did you set the VM settings to route COM1 to the named pipe kmdpipe?
Turns out the pipe was registered with a typo.