VBoxHardening issue (AV software)

[gingleby]

Windows 7 Enterprise SP1 Virtual Box 5.1.10 was working fine until company pushed an update to my workstation.

I think the issue is related to Cylance Protect as that software seems to have been updated the day VB broke. It's also possible kernel32.dll was updated by a windows update.

Error starting ALL VMs..

The virtual machine 'DeleteMe' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in 'C:\Users\MyProfile\VirtualBox VMs\DeleteMe\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005) Component: MachineWrap Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

The workstation/host has Cylance Protect and Symantec Endpoint Protection enabled (and I can't disable them to test).

I tried test builds.

5.1.10 original had the issue. 5.1.14 - same issue 5.1.15 - test build same issue. 5.1.51 - dev build same issue

[gingleby]

I was able to disable the CylanceSvc service and VirtualBox started the VMs OK. I am not however permitted to run without CylancePROTECT enabled - which prevents VirtualBox from operating correctly.

[JPagan]

Are there any updates on this ticket. I am having the same problem as gingleby. My company won't allow me to run without CylancePROTECT.

[Socratis]

Have a look at the thread ​"(Solved) VirtualBox Vs Cylance Protect" in the forums.

[bugmenotplease]

I have the same issue. When you look at the thread, you can see only advice - try to whitelist anything related to VBox, which is not very helpful.

[Socratis]

Why in the seven kingdoms are you coming to the ticket when we're already talking in the forum?

[bugmenotplease]

I don't know what is the correct procedure for resolving bug here, but forum seems to me like something just for a community help, whereas this bug report looks like something the developers should take a look at and actually fix.

Plus the word "solved" in the name of the thread might lead to the conclusion that the issue is resolved, which is not; so I think I should let people know here.

[Socratis]

You are going to get community help here as well because we're the ones that "shield" the developers from explaining and solving 95% of the issues. That allows them to actually work and focus on solving the remaining 5% of real issues.

Yes, the issue is marked as resolved because ... it was resolved. It was explained 3 times; put an exception for VirtualBox on Cylance Protect. You keep coming coming back with "which parts", to which I told you that you have the following options:

• The whole VirtualBox directory.
• Everything .exe
• And finally (and more importantly) since you have a support contract with Cylance Protect, and since the Original Poster said that it was resolved after contacting Cylance Protect, you could do the same.

The problem with hardening can be better explained in the FAQ: ​Diagnosing VirtualBox Hardening Issues. Cylance Protect needs to address this too. For the moment you have an easily implemented workaround.