Failed to open a session for the virtual machine muah.
The virtual machine 'muah' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\Anna\AppData\Local\Droid4X\muah\Logs\VBoxHardening.log'.
Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}
Falied to open a session for a virtual machine
Falied to open a session for a virtual machine
- Attachments
-
VBoxHardening.log- (93.66 KiB) Downloaded 19 times
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: Falied to open a session for a virtual machine
Please zip logs in future.
What's with the strange log file location? Is this using Vagrant, Portable VirtualBox, anything like that?
FAQ: Diagnosing VirtualBox Hardening Issues.
What's with the strange log file location? Is this using Vagrant, Portable VirtualBox, anything like that?
5.0.40? It seems long past time to update VirtualBox. Support for the 5.0 branch ended two years ago.22b4.209c: Log file opened: 5.0.40r115130 g_hStartupLog=0000000000000068 g_uNtVerCombined=0xa042ee00
I'm not altogether sure what the above means. I assume it means that some piece of code or data in memory is not the expected size. You could start by checking the certification on this DLL yourself. Also run "sfc /scannow". And update VirtualBox.16c8.15b0: Error (rc=0):
16c8.15b0: supR3HardenedScreenImage/LdrLoadDll: rc=Unknown Status -626 (0xfffffd8e) fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume4\Windows\System32\bcrypt.dll: Grown load config (244 to 256 bytes) includes non-zero bytes: 00 00 00 00 90 a9 01 80 01 00 00 00
FAQ: Diagnosing VirtualBox Hardening Issues.