Hi
I have been searching the net and many post about the error I am getting without any luck. I do hope that now I might solve my problem.
So I have been using Oracle Vmbox without any headaches for a long time. But since Last week I believe after my corporation did some windows updates all my virtual machine would not start normally. I was able to successfully start on headless mode my ubuntu servers.
The error:
Failed to open a session for the virtual machine ' ubuntu server'.
Failed to open a session for the virtual machine ubuntu server.
The virtual machine 'ubuntu server' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005).
Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
I did all of the usual recommendations:
Uninstall and reboot the machine.
Remove the 5 vbox*. from WIndows\system32\drivers\
Reinstall the Oracle VM VirtualBox as administrator.
Tried to start the VMboxes but same error.
I also fallowed some recommendation to disable Hypervisor from an elevated CMD.
I was able to copy my vms to another machine and they started without a problem. So no error in the actual VM:s.
My Host is a windows 10 20H2.
I am not sure bu tI believe one of these are guilty.
KB5012599
KB5012117
Servicing Stack 10.0.19041.1704
I can't uninstall to test because it is a corporate machine that will install them back again .
We have Cylance Protect as anti-virus But I do not see anything that it says it blocks.
I do hope I have given enough information about my problem.
Please help.
Best Regards
Failed to open a session
-
- Posts: 3
- Joined: 24. May 2022, 09:22
Failed to open a session
- Attachments
-
- VBoxSVC.zip
- (20.97 KiB) Downloaded 16 times
-
- Posts: 3
- Joined: 24. May 2022, 09:22
Re: Failed to open a session
Hi
So i found part of a solution:
It was for some reason Cylance Protect:
I did the fallowing:
In the Cylance dashboard, edit the device policy that is applied to the affected machines.
Those where already in place:
Under memory actions, exclude \Program Files\Oracle\VirtualBox\virtualbox.exe
Under protection settings, add an exception for C:\Program Files\Oracle\VirtualBox\
And I added also
Under memory actions, exclude \Program Files\Oracle\VirtualBox\virtualboxVM.exe
After that all is working well
So i found part of a solution:
It was for some reason Cylance Protect:
I did the fallowing:
In the Cylance dashboard, edit the device policy that is applied to the affected machines.
Those where already in place:
Under memory actions, exclude \Program Files\Oracle\VirtualBox\virtualbox.exe
Under protection settings, add an exception for C:\Program Files\Oracle\VirtualBox\
And I added also
Under memory actions, exclude \Program Files\Oracle\VirtualBox\virtualboxVM.exe
After that all is working well
-
- Site Moderator
- Posts: 39156
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Failed to open a session
It has been reported on these forums for several years that Cylance Protect interferes. It is notorious for it in fact.
https://www.google.com/search?hl=en&as_ ... type=&tbs=
https://www.google.com/search?hl=en&as_ ... type=&tbs=
-
- Posts: 3
- Joined: 24. May 2022, 09:22
Re: Failed to open a session
Hi
The problem is making the support of the platform believe you. There are no logs showing in Cylancer de-Protect lol.
Anyway I am happy after one week of work I could find a solution.
The problem is making the support of the platform believe you. There are no logs showing in Cylancer de-Protect lol.
Anyway I am happy after one week of work I could find a solution.
-
- Site Moderator
- Posts: 20965
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Failed to open a session
The extra exclusion is needed because VirtualboxVM.exe is the program that actually runs the VMs, whereas Virtualbox.exe is only the main Virtualbox window.foxerthefixer wrote:Those where already in place:
Under memory actions, exclude \Program Files\Oracle\VirtualBox\virtualbox.exe
Under protection settings, add an exception for C:\Program Files\Oracle\VirtualBox\
And I added also
Under memory actions, exclude \Program Files\Oracle\VirtualBox\virtualboxVM.exe