search

4d61726b / VirtualKD-Redux

VirtualKD-Redux - A revival and modernization of VirtualKD
GNU Lesser General Public License v2.1
777 stars 136 forks source link

Debugger can't start normally #51

Closed xia0ji233 closed 1 year ago

xia0ji233 commented 1 year ago

Describe the bug I did operations according to README file,but get unexpected result.

To Reproduce Steps to reproduce the behavior:

  1. Create Virtual Machine in Vmware Workstation 16.2.4 build-20089737 pro.
  2. ISO file was downloaded from https://www.microsoft.com/zh-cn/software-download/windows10ISO,the version is Windows10 22H2
  3. Running the file in target64 on this Virtual Machine,and an entry was created normally.
  4. Then I start vmmon64.exe on my physical machine, successfully patched but can't connenct to windbg.

Expected behavior windbg will auto start and connect the virtual machine normally

Screenshots image

I have searched in google and issue in this project but get no result for me.I would appreciate it very much if someone could give me some helpful advice

4d61726b commented 1 year ago

From your screenshot, it seems like kdclient.dll was successfully loaded on your host.

Can you:

  1. Start vmmon64.exe before powering on any VMs.
  2. Power on the VM, make sure vmmon64.exe reports success for your VM before moving on to the next step. Just look for the green circle in the PID column.
  3. In the VM at the "Windows Boot Manager" screen, ensure the [VKD-Redux] entry is highlighted then press F8 and select "Disable Driver Signature Enforcement".
xia0ji233 commented 1 year ago

Following your steps,I see the problem.I didn't press F8 and select "Disable Driver Signature Enforcement" option when it start.So I can connect to windbg when I follow your steps.Mabey most tutorials online don't metion this detail,so I only choose the new entry when the virtual machine booting. Thank you very much for your help.Best wishes.