Upgrade from 4.3 to 5.0 issue

[JMR001]

I was running vbox 4.328 on a Windows 8.1 pro Lenovo Yoga with an I5 processor and 8GB of ram. It was running fine until I upgraded to version 5 and now I get the following error when I try to launch a Windows 7 VM. I have attached the log mentioned in the error

Failed to open a session for the virtual machine 7-10.

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

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

Any Ideas would be greatly appreciated.

[JMR001]

I uninstalled 5.0 and did a fresh install which seems to have fixed the issue.

Hope this helps someone else.

[noteirak]

In an elevated prompt, type this and post back the output:

Code: Select all

sc.exe query vboxdrv

[ysrd]

Uninstalling and reinstalling every day is getting old.
It worked Friday, and it fails today. Windows 7 pro. McAfee AV 8.8 enterprise.
None of the VMs work and it won't make new ones.
I am trying to use VBox 5.0.0
Can you maybe make a version of VBox that doesn't have the security so we can actually use it while you try to fix this? Just a suggestion.

[zigzag]

I was running vbox 4.328 on a Windows 8.1 pro Lenovo Yoga with an I5 processor and 8GB of ram. It was running fine until I upgraded to version 5 and now I get the following error when I try to launch a Windows 7 VM. I have attached the log mentioned in the error

Failed to open a session for the virtual machine 7-10.

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

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

Any Ideas would be greatly appreciated.

I got same error, so I ran sc.exe query vboxdrv with result

Typ: 1 KERNEL_DRIVER
Stav: 1 STOPPED
....

then I tried ran sc.exe start vboxdrv, but also with error, because this service wasn' t in my system,
so I installed driver C:\Program Files\Oracle\VirtualBox\drivers\vboxdrv\VBoxDrv.inf, for sure started service sc.exe start vboxdrv
and then virtualmachine started and looks like working

[mpack]

This would imply that the software was not installed properly to begin with, otherwise this and other drivers would have been installed at that time. Check the security levels on your host, make sure that you are at least prompted when drivers are about to be installed (i.e. they should not be silently rejected). Use "Run as administrator" when running the installer.

[VickersNick]

Notice dozens of "[lacks WinVerifyTrust]" in the startup logs (posted as well as my own). Is this related to that problematic Windows patch?

BTW - I tried installing 5.0 fresh (after uninstalling 4.24) both As Administrator and Run Elevated...same MachineWrap error as OP.

[codetricity]

I recently upgraded from 4.3 to 5.0. I was not able to import any of my VMs form 4.3 to 5.0. the VM manager indicated that the VMs needed to be in OVF format. On 4.3, I have a large number of linked clones.

Are there directions on what I need to do to upgrade from 4.3 to 5.0? It wasn't as simple as downloading 5.0 and installing it. Was it supposed to be this easy?

[mpack]

You don't need to "import" VirtualBox's own VMs, regardless of version. VirtualBox would have found the existing VMs automatically if they were in the standard place. If the VMs have been moved then read Howto: Move a VM.

And yes, upgrading is as simple as downloading the installer and running it. The existing VMs should be right there in the manager after this is done. If that isn't what you saw then there must be something missing from your story.

Incidentally, there has never been a VirtualBox 4.3. Please be accurate about identification. Depriving us of important information makes diagnosis of your problem less likely.

[lawaluwa]

Hello,

I have the same problem.

I just installed the newest VB to my newly bought VPS server, and I just cannot manage to install any windows in it.

After I hit start, this error msgs pop up:
http://pasteboard.co/21ybmn1N.png
http://pasteboard.co/21FQ1s1l.png

I have tried to reinstall; reinstall, start in admin mode; register manually the Vboxdrv.inf, but no succes..

Please help me with this!

[codetricity]

You don't need to "import" VirtualBox's own VMs, regardless of version. VirtualBox would have found the existing VMs automatically if they were in the standard place.
And yes, upgrading is as simple as downloading the installer and running it. The existing VMs should be right there in the manager after this is done. If that isn't what you saw then there must be something missing from your story.

Incidentally, there has never been a VirtualBox 4.3. Please be accurate about identification. Depriving us of important information makes diagnosis of your problem less likely.

Thanks. This was worked! I appreciate the help. I actually had installed the VirtualBox 5.0.0 binary in a different location from the 4.3.30 version. When I installed 5.0.0 in the same location as 4.3.30, everything started working. I'm very curious if people have tested the USB 3 throughput of the VMs. I'm running Linux guests on a Windows 8.1 host. previous performance was poor. Thanks.

[jonesvzla]

I installed VB 5 and when I try to execute it then show this errors
"Fallo al crear el objeto COM de VirtualBox.
La aplicación se cerrará ahora.
Receptor RC: REGDB_E_CLASSNOTREG (0x80040154)"



I am executing it like administrator.

Host: Windows 7 X64

Thank in advance

[mpack]

That does not seem to be the same as the OPs question.

Please don't hijack other people's topics - start your own.

[ysrd]

I uninstalled 5.0 and did a fresh install which seems to have fixed the issue.

Hope this helps someone else.

Did it fix over more than one reboot?
Question, now that I have run the VMs with 5 will they still work if I go back to a 4 version that worked.