Closed ttodua closed 1 year ago
A duplicate of https://github.com/ramensoftware/windhawk/issues/25
From the issue above:
this failure is due to unsigned code injection being detected in the VM host process, so VirtualBox refuses to start the VM
The best solution is to exclude VirtualBox in the advanced settings of Windhawk. Let me know if you need help with that.
Thanks, I will try that
when windhawk is running (i have "Middle click to close " mod running ( with "old explorer support" option checked), then it conflicts virtualbox and we can't boot up any Windows guest OS boxes:
After exiting WindHawk, virtualbox works well.
I know this might not be priority, but just giving note to you about this issue.