Virtualbox causes SYSTEM_SERVICE_EXCEPTION on Win10

[woli]

When starting an imported OVA on a fresh install of WinBox my Win10 machine ends up in a BSOD.

Winbox 5.2.6r120293 Windows 10 Enterprise 64bit

[woli]

VBox Log files

[woli]

multiple windows minidump files

[Socratis]

• Uninstall all TrendMicro software for starters. Not disabled, uninstalled.
• Address the following:

  00:00:03.016844 WARNING! 64-bit guest type selected but the host CPU does NOT support HW virtualization.
  00:00:03.286152 HM: HMR3Init: Falling back to raw-mode: VT-x is not available
  

And that's as far as your log will go. What are you trying to install? From where?

[woli]

OK, fair enough - TrendMicro is running, and I cannot easily stop it. Got administrative rights on this corporate computer, but cannot control Office Scan. Will need to take this with the IT department.

The warning about "VT-x is not available" will come from the fact that I have disabled the Hyper-V windows feature so to not compete with VirtualBox. That was the one action I tried to get it running, besides stopping the firewall service.

If you like you can put this ticket on hold or close it for now.

[Socratis]

VT-x not available is *not* due to the fact that you have Hyper-V disabled, on the contrary. Disabling Hyper-V makes VT-x available. So something else is using VT-x. It could be the TrendMicro, lately antivirus has a tendency to require hardware virtualization for some reason. Most of the times this "feature" can be disabled.

[woli]

thanks for the hint - I will try to convince our IT department to make an exception here. Otherwise I will be lost and have to give up the plan to use virtualbox on our office machines...

[angel.navarro]

I have the same problem, i attached my logs