Author Topic: Oracle VirtualBox conflict  (Read 945 times)

0 Members and 1 Guest are viewing this topic.

Offline Anton54

  • Newbie
  • *
  • Posts: 5
Oracle VirtualBox conflict
« on: May 27, 2019, 06:17:04 PM »
Since rather recent time (I believe this year), no VM in VirtualBox starts. Checking VB docs and logs reveals that the source of the problem is Avast DLLS. So it is urgent for Avast to provide signed DLLs, so they could load into VB processes.
Maybe there is a workaround such as disabling Avast security for VB processes... but I counld not figure how to do that.

Host: Windows 8.1 x64.

Offline Richard677

  • Newbie
  • *
  • Posts: 3
Re: Oracle VirtualBox conflict
« Reply #1 on: July 05, 2019, 11:12:05 AM »
I was having issues with VirtualBox and Avast.  When running any VM I would randomly see a Sad Screen/BSOD with the error SYSTEM_SERVICE_EXCEPTION.  I also used the logs to determine the error was Avast DLL's.  I had to go into Avast, open the menu, select settings, and select troubleshooting.  I shut off (unchecked) Enable hardware assisted virtualization and rebooted.  The Sad Screen seems to have gone away but I am still waiting to be certain. 

I think the issue is the Windows 10 implementation/hardware implementation of virtualization.  You cannot have multiple applications using the VM hardware services (Intel VT-x or AMD-V) at the same time - sharing doesn't work.  For example if you have Hyper-V installed VirtualBox will crash with similar errors or not start at all. 

I am trying to see if there is a solution since this hinder some sandbox features of avast.