4d61726b / VirtualKD-Redux

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

Virtualbox fails to load kdclient64.dll when starting a Win10 VM #26

Closed aaptel closed 3 years ago

aaptel commented 3 years ago

Describe the bug I cannot get VirtualKD to work. I've followed the tutorial, including installing the certs on the host. Virtualbox fails to load kdclient64.dll

To Reproduce

Expected behavior I expected the Run Debugger to do its thing.

Screenshots image

Configuration (please complete the following information):

4d61726b commented 3 years ago

Can you post the logs for this VM? If you right click the VM in the VirtualBox Manager there is a "Show Log..." button.

Upload the last VBox and VBoxHardening log files. Thanks.

aaptel commented 3 years ago

Sorry I needed to get this working fast and was getting really frustrated so I (tried) uninstalled VirtualKD and started from scratch from a new VM using regular built-in kdnet (windbg NET debug). I don't have the logs anymore

4d61726b commented 3 years ago

I tried it with the versions you used and everything worked on my end. My guess based on that limited error message was that you never imported VKD-Redux_CA.cer into the Trusted Root Certification Authorities certificate store.

If you run into this issue again in the future and are able to post the logs, feel free to reopen the ticket. Thanks.

aaptel commented 3 years ago

I imported the cert (right click, install cert, selected Local Machine) as I mentioned in the report. I still have it probably. Are you sure the code is signed with the right cert?

aaptel commented 3 years ago

image

4d61726b commented 3 years ago

Intermediate Certification Authorities != Trusted Root Certification Authorities. Its in the wrong certificate store.

aaptel commented 3 years ago

Hm ok weird, I followed the instructions on the tutorial though. Maybe it's missing something to make that cert stored as Root cert?

4d61726b commented 3 years ago

You have to explicitly choose where to install the certificate in the wizard. You can't let Windows decide for you, otherwise it can put it in the wrong store. I think that was your issue. See screenshot for correct usage.

image

aaptel commented 3 years ago

Ok well I'll remember next time :) thanks