VMs won't load after upgrading 4.2.4-81684 to 4.3.18-96516

[gjcdeluxe]

Hello, I just upgraded from VirtualBox-4.2.4-81684-Win to VirtualBox-4.3.18-96516-Win, having first uninstalled the old version, and now my VMs (WinXP x2 and Win7 x1) fail to open, with the following error message:

Failed to open a session for the virtual machine Win7.

Unable to load R3 module C:\Program Files\VirtualBox/VBoxDD.DLL (VBoxDD): GetLastError=1790 (VERR_UNRESOLVED_ERROR).

Result Code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}

Any ideas, anyone?

cheers,
Gabe

[Perryg]

Post the guests log file ( as an attachment )

[gjcdeluxe]

I can find the following log files in C:\Users\Administrator\.VirtualBox:
VBoxSVC.log
selectorwindow.log
VirtualBox.xml

Is one of those the guests log?

[Perryg]

Rt. click the guest in the main manager then show log. Save and post as an attachment.

[doveman1]

I'm having the same problem. I even created a new VM and it aborts after Windows 7 starts loading files from the CD.

I've attached the logs from both my pre-existing VM and the new one I created.

[Perryg]

Unfortunately the logs do not show what the error is. They seem to stop at the point of loading the video but that may only be a red herring.

What happens if you try to install a new guest?

Maybe you should go ahead and post the VBoxSVC.log

[doveman1]

One of those logs is from my attempt to install a new guest.

I've attached the VBoxSVC.log and the previous one in case the latter shows anything useful in addition.

[Perryg]

I don't see a reason there either. You should raise a ticket at bugtracker

[TAiNiUM]

I am having this issue also. I went from VirtualBox-4.3.16-95972-Win to VirtualBox-4.3.18-96516-Win.

The Error I am getting is Failed to open a session for the virtual machine Win 8.1 Enterprise Admin.

The virtual machine 'Win 8.1 Enterprise Admin' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in 'C:\Temp\VirtualBox VMs\Win 8.1 Enterprise Admin\Logs\VBoxStartup.log'.

Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

VBoxStartup.log

(63.07 KiB) Downloaded 5 times

VBox.log

(94.25 KiB) Downloaded 5 times

[doveman1]

I don't see a reason there either. You should raise a ticket at bugtracker

After rebooting (I changed a few things, like removing a PCI SATA card and connecting the HDD back to the motherboard but Virtualbox was working with the PCI card before I updated it so I doubt that's relevant), it's no longer closing the VM but it's not booting either and is just hanging on the Windows boot screen (Not Responding) with the old VM and about 3/4 of the way through the "Windows is loading files" progress bar for the new VM.

Logs attached for both VMs.

[doveman1]

Could only attach 3 files, so here's the missing log for the new VM

[TAiNiUM]

I am having this issue also.

The Error I am getting is Failed to open a session for the virtual machine Win 8.1 Enterprise Admin.

The virtual machine 'Win 8.1 Enterprise Admin' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in 'C:\Temp\VirtualBox VMs\Win 8.1 Enterprise Admin\Logs\VBoxStartup.log'.

Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

VBoxStartup.log

VBox.log

I downgraded to VirtualBox-4.3.16-95972-Win and it works fine now. Must be something in the new release?

[doveman1]

Ticket opened: https://www.virtualbox.org/ticket/13566

[doveman1]

It took about four attempts to get the VM to launch at all after downgrading back to 4.3.16, as it was just throwing up some error box but it worked eventually.

[doveman1]

It's actually not fixed properly even by downgrading. I installed a fresh Win 7 x32 VM and was rebooting after each batch of Windows Updates and that was fine but then I shutdown and had the same problem when starting it again, just getting some error message for four or five tries before it finally worked. So it looks like I'll get this every time I start the VM from cold, or maybe even resuming from saved state.