Closed mick88 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.
I have been having issues booting up a VM using a VirtualMachine. When looking at VBoxHardening.log, I found this:
after turning off windhawk, Virtualbox is working again.
I also found that someone else reported a similar problem already on Oracle forums: https://forums.virtualbox.org/viewtopic.php?f=6&t=109353