Closed kahotv closed 3 years ago
I'm able to reproduce this issue if vmmon64 is not already running. Were you running vmmon64 before booting into Windows? This is a workaround for now.
The problem seems to stem from returning a failure back to Windows during the boot process in the case where the host side isn't ready for communication yet (i.e. kdclient has not been loaded in the vmx process). I am still looking into it.
I believe this issue is now fixed in VirtualKD-Redux 2020.4.
Describe the bug disable driver signature -> BSOD
Host: ...
To Reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Configuration (please complete the following information):
more:
VKD-Redux + disable signature -> BSOD windows 10 + disable signature ->no BSOD