virtualbox.org

Hello, please, I was unable to solve a hardening issue with the latest version of VirtualBox running on Windows 10. I followed the recommended steps on page "Diagnosing VirtualBox Hardening Issues", but I was not able to read out the problem from the log.

Trying to install different past versions did not help; neither disabling the windows features. Previously, I have been using VB to run Xilinx ISE 14.7 SW, but since I uninstalled that software, I was not able to run, e.g. virtual linux machine.

Thanks in advance.

Is there anything, besides the log, that might be helpful for diagnosis?

For a test, uninstall Bitdefender Endpoint Security, reboot the host, start a VM, and post a new VBoxHardening.log file if the problem persists.

As the PC is in business network, I would like to avoid removing of the anti-virus software. I noticed a new version of VB is released, I tried to again delete all old VB files and install it. Behavior of VB changed, now it shows me a black screen instead of previous error message. I include the new hardening log: now, there is "Quitting: ExitCode=0x0" instead of previous 0x1. Is that because I shut-down the black-screen machine myself?

Thank you.

If you can't uninstall the third-party Anti-Virus/Security software, then you need to find out how to 'white list' the VirtualBox installation in the Bit Defender software. As you're using a business system, your IT support people should be able to help, as you may not have the required permission levels to make the necessary changes.

kolarja wrote:I include the new hardening log: now, there is "Quitting: ExitCode=0x0" instead of previous 0x1. Is that because I shut-down the black-screen machine myself?

No, probably not. Regarding Bitdefender Endpoint Security, it is possible that VirtualBox was capable of defending itself against it this time (pun intended ). There was a reason why I suggested to uninstall it for a test: It could or could not play a role, we cannot be sure about that.

The black-screen problem hints to the ubiquitous Hyper-V problem. Look at a VBox.log file in combination with HMR3Init: Attempting fall back to NEM (Hyper-V is active).