virtualbox.org

"Failed to open a session for the virtual machine xp.
The virtual machine 'xp' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\db\VirtualBox VMs\xp\Logs\VBoxStartup.log'.
Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}"

Should I post log to get more details? I'm stuck.

Right click the VM in the VirtualBoxGUI. Select "Show Log". Save "VBox.log" to a file. Compress that file and attach it to a message here. Make sure the VM is fully shut down beforehand.

Ok, I have attached zip of log. Any feedback would be very much appreciated!

Is there a better place to go for info? I'm stuck...
Tech support?

I'm stuck and my VM won't start anymore.

Read the following links.

http://support.microsoft.com/kb/3024777
viewtopic.php?f=6&t=66639

I've installed that patch, and rolled back to an older version of Virtualbox.

I still get the exact same message when I try open any VM.
Is there a hint in my log file?

The log file shows the issue to be a bad update from micorsoft. This must be fixed before you can install and use VirtualBox.

Perryg wrote:The log file shows the issue to be a bad update from micorsoft. This must be fixed before you can install and use VirtualBox.

I ran KB3024777 as suggested above , which UAC says is 'KB3024777 Removal'.

When I look at Windows Update or Belarc Advisor, it says all the updates are good.
Do you have any info on *what* update is bad, or causing the issue?

The one i posted above is what caused the issue. How to actually fix it is beyond my assistance I am afraid.

There was a discussion about it earlier here when it first happened but I don't know exactly where. Maybe someone else remembers.

Perryg wrote:The one i posted above is what caused the issue. How to actually fix it is beyond my assistance I am afraid.

There was a discussion about it earlier here when it first happened but I don't know exactly where. Maybe someone else remembers.

I went back to an old version of Vbox and it works.

Very disappointing that there is no tech support from Oracle, even in these forums.

The original update that caused the problem was KB3004394. I wouldn't be too disappointed about support. There are plenty of commercial programs that offer poor or no support much less free support for a free program. Often times those that do offer support are wrong.

loukingjr wrote:The original update that caused the problem was KB3004394. I wouldn't be too disappointed about support. There are plenty of commercial programs that offer poor or no support much less free support for a free program. Often times those that do offer support are wrong.

I followed all that I could find about KB3004394, as I mention above. Surely tons of people win win7 have this issue now..
Is there any indication that the Vbox team is working on the fix?

from what I remember Microsoft eventually repaired and re-released KB3004394. As far as VirtualBox it's not up to them to patch their software around every flaw in Windows or other Applications.

Besides, it hasn't been an issue for a very long time as far as I know.

loukingjr wrote:from what I remember Microsoft eventually repaired and re-released KB3004394. As far as VirtualBox it's not up to them to patch their software around every flaw in Windows or other Applications.

Besides, it hasn't been an issue for a very long time as far as I know.

If Vbox wont even run in a full normally patched Wndows 7, it seems like they'd want to fix that...

drb wrote: If Vbox wont even run in a full normally patched Wndows 7, it seems like they'd want to fix that...

Why is it when something isn't running on their own computer people assume it doesn't run on anyones?