Error "Failed to open a session for the virtual machine..."

[Brainbuster]

The host is Windows 7 Ultimate.

I'm trying to start this guest, which was working just fine before I switched to Windows 7 Ultimate.

Now it won't even start at all.

I get this error: VirtualBox Error "Failed to open a session for the virtual machine Brainbuster..."

I click on Details, and it says,

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


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

Anyone, will you help me please?

[mpack]

Anyone, will you help me please?

Zip up the "VBoxStartup.log" file mentioned in the error message, and attach here.

Read the security sticky discussion first.

[Brainbuster]

Thank you!
Attached is the log file.

Host: Windows 7 Ultimate

AV: Avira free antivirus with real-time protection enabled.

[mpack]

You have a bunch of "lacks WinVerifyTrust" followed by an exit code 1 abort. I have no idea what it means.

Actually, there is an earlier error :-

1874.1d0c: Error -104 in supR3HardenedWinReSpawn! (enmWhat=5)
1874.1d0c: Error relaunching VirtualBox VM process: 5
Command line: '60eaff78-4bdd-042d-2e72-669728efd737-suplib-3rdchild --comment Laura --startvm e56d02a1-4f9e-4ac8-8ae4-e939597cbe9c --no-startvm-errormsgbox "--sup-startup-log=C:\Users\Jon\VirtualBox VMs\Laura\Logs\VBoxStartup.log"'

However the process continues after this so I can't tell if the error is significant.

You could try uninstalling and then reinstalling VirtualBox, being sure to use "Run as administrator" when running the installer.

[Freek]

Had the same error "Failed to open a session for the virtual machine..." for VirtualBox 5.0.0r101573 on Win7 Prof 32bits, after I ran an update for Avira Antivirus.

Failed to open a session for the virtual machine testxp32.

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

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

Uninstalled Avira, and VirtualBox was back in business. Reinstalled Avira, and then got the VirtualBox error again. Just disabling Avira''s real time protection didn't help.
Looks like I need a new antivirus program...

Regards,
Freek.

[Brainbuster]

Freek, I love you!!!

I just uninstalled Avira, and it works now.

[AlexCastillo]

Fallo al abrir una sesión para la máquina virtual Android4.4Kitkat.

The virtual machine 'Android4.4Kitkat' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\My DELL\VirtualBox VMs\Android4.4Kitkat\Logs\VBoxStartup.log'.

Código Resultado: E_FAIL (0x80004005)
Componente: MachineWrap
Interfaz: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}

[mpack]

I encountered with this error after updating to Windows 10 and Virtual Box 5.
Solved it by replacing the "imagehlp.dll" file in "c:\windows\systtem32" folder with the one from previous windows 7 installation. The working dll file attached...

imagehlp.zip

[mpack]

@MrBean, that's a rather random piece of advice. I take it that you discovered that that particular file had been modified by some unknown agent on your PC. That's fine, but unless you know why then I don't think we can assume that your results will be applicable to others.

I also can't have you using this site to distribute unknown executable code without permission from the copyright holder, so I have disabled that download. For people who want imagehlp.dll - it is part of Windows and can be found on the Windows install DVD.

[mpack]

@AlexCastillo: try reinstalling VirtualBox, be sure to use "Run as administrator" - while logged in as the correct user - when running the installer.

Anyone reading this topic should also be reading the security sticky discussion.

[vKs]

I'm getting the same error after upgrading to windows 10. I only managed to run the VM for the first time, after the fresh install.I've been getting the error since then. Hellp!

[bilbaxo]

Solved it by replacing the "imagehlp.dll" file in "c:\windows\systtem32" folder with the one from previous windows 7 installation. The working dll file attached...
imagehlp.zip

Yes, it works allright.

Go to the old windows directory and copy the imagehlp.dll (74 ko) from the system32 directory
Change the rights of the system32 directory of the actual version of windows (windows directory) and paste the imagehlp.dll in place of the bad one..
Thank's and whatever the reasons, it works.

[mpack]

It would be nice to pin down exactly why imagehlp.dll is being corrupted or modified. If anyone else spots this problem then it would be useful to note the modification time stamp on the file, and see if it corresponds to any software installation, or Windows Update etc.

Also note that, although the error messages may sound similar, the specific cause may be different for each user. Only a look at the VBoxStartup.log file can pinpoint the individual cause. AFAICS, none of the logs posted in this thread show that DLL as being a problem. We have had two people posting about it, but no logs. OTOH there has been one additional topic where a VBoxStartup.log was posted which showed this problem. However that sample of one is not enough to draw many conclusions.

[jal1234]

I had this problem on a Win10 x32 installation done yesterday on an Asus T100 running r101957. Replaced the imagehlp.dll as above, and it cured the startup problem. Date stamp on the Windows 10 .dll was July 10, 2015, 3:24:55PM, 89k. Old version which solved the problem was Oct 28, 2014, 10:06PM, 74k. Note that the old file is significantly smaller. I had installed virtualbox as an admin, and also run it as an admin.

VBoxstartup.log is attached. It may not or may not be of help because it is from after I got it working, but I didn't delete the log before replacing the DLL.

I can run the programs I need under the WinXp x32 virtual installation, but it will not successfully save the machine state; I have to shut down the virtual computer instead.

Interestingly, on a different computer running the x64 version of Windows 10, the same image starts fine under r101957.

Hope this helps.

[mpack]

You replaced a Windows system DLL with one from a previous Windows version? That hardly seems like a good idea. OTOH it is probably something you should discuss with Microsoft.