Problem starting any VM after upgrading to v 5.0.6 r

Discussions related to using VirtualBox on Windows hosts.

Problem starting any VM after upgrading to v 5.0.6 r

Postby digitiger » 11. Oct 2015, 13:00

Hi I have been using VirtualBox for years. Recently I had a need to import Win 7 professional version guest which was originally exported using higher version of VirtualBox, so I too upgraded my Virtualbox version to 5.0.6 (latest available on oracle site).

Now after the upgrade, it fails to start ANY VM old or new and gives almost same error message saying something like

Failed to open a session for the virtual machine Win7-64x.

The virtual machine 'Win7-64x' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\admin\VirtualBox VMs\Win7-64x\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}


I have uninstalled VirtualBox, cleaned registery, removed all related folders including from profile, .virtualbox etc , resistalled and have tried all that but without any success :? .

The log file is also attached. Basically it seems to be starting to fail with
NtOpenDirectoryObject failed on \Driver: 0xc0000022

Please help.
Attachments
VBoxHardening.rar
compressed log file (as uncompressed is bit bigger then that allowed by this website policies)
(8.44 KiB) Downloaded 487 times
digitiger
 
Posts: 1
Joined: 11. Oct 2015, 12:52

Re: Problem starting any VM after upgrading to v 5.0.6 r

Postby mpack » 11. Oct 2015, 14:10

The error is VirtualBox's security (hardening) features kicking in, and it means that it thinks somebody is injected unsigned or hacked DLLs into the VirtualBox executable process space.

Looking at the log, my attention is caught by sxs.dll, midimap.dll, tiptsf.dll.

You might want to Google for these, and look for updates to whatever they're part of. My own quick search indicated that these might be RealTek audio drivers.
mpack
Site Moderator
 
Posts: 32670
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

VirtualBox v5.0.8 Error when starting on Windows 7

Postby Masoud » 29. Oct 2015, 01:02

Hi,
I am new to VirtualBox and I am trying to setup Ubuntu on my Windows 7. I get the following error. I searched similar pages and removed the two windows update as well as running as administrator, or trying a fresh install. None of them worked! Would you please tell me what to do? I appreciate if you explain it to me exactly what to do as I am new to VirtualBox. BElow is the message. I also attach the log file.

Thanks in advance.

Failed to open a session for the virtual machine Ubuntu.

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

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}
Attachments
VBoxHardening.log
Log file
(74.88 KiB) Downloaded 583 times
Masoud
 
Posts: 1
Joined: 29. Oct 2015, 00:39

Re: Problem starting any VM after upgrading to v 5.0.6 r

Postby gperpetuo » 30. Oct 2015, 10:50

Hi, I'm having the same kind of problem, also.

The virtual machine 'win7' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\Utilizador\VirtualBox VMs\win7\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}

Could someone point me what the problem could be?
Thank you!
Attachments
VBoxHardening.zip
(11.92 KiB) Downloaded 341 times
gperpetuo
 
Posts: 1
Joined: 30. Oct 2015, 10:40

Re: Problem starting any VM after upgrading to v 5.0.6 r

Postby mpack » 30. Oct 2015, 13:03

VBoxHardened.log wrote:1cb4.2c44: supR3HardenedDllNotificationCallback: supR3HardenedScreenImage failed on 'C:\Windows\system32\COMDLG32.dll' / '\??\C:\Windows\system32\COMDLG32.dll': 0xc0000190

Hacked system DLL, it would seem. This is the common dialogs dll (common open file dialog etc), so I assume you've installed a hacked UI theme on your Win10 host, or e.g. something that hacks the filesystem to show bluetooth devices. You can try putting a copy of the original (unhacked) DLL into the VirtualBox "Program Files" folder.
mpack
Site Moderator
 
Posts: 32670
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Problem starting any VM after upgrading to v 5.0.6 r

Postby zacsees » 10. Oct 2017, 18:01

i have problem using my vm 5.1.28
Failed to open a session for the virtual machine win7.

The virtual machine 'win7' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\XXX\VirtualBox VMs\ZZZ\Logs\VBoxHardening.log'.

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

Can some one help me set it up please?
zacsees
 
Posts: 8
Joined: 10. Oct 2017, 17:58

Re: Problem starting any VM after upgrading to v 5.0.6 r

Postby mpack » 10. Oct 2017, 18:22

mpack
Site Moderator
 
Posts: 32670
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Problem starting any VM after upgrading to v 5.0.6 r

Postby sagartalod » 26. Feb 2018, 10:32

I was facing the same issue after I updated my system's OS.
Then I took the latest update of Virtual Box and the problem was solved.
Try this if you are having the same scenario.
sagartalod
 
Posts: 1
Joined: 26. Feb 2018, 10:24


Return to VirtualBox on Windows Hosts

Who is online

Users browsing this forum: No registered users and 25 guests