Custom Query (16363 matches)
Results (802 - 804 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #14888 | obsolete | After upgrade to Version 5.0.10 r104061, image has become unstable | ||
| Description |
I upgraded to latest, (the prior was probably the latest too, I keep updating as each time one comes out). My image worked mostly, but would crash after long running. Now it won't load at all :( --> Failed to open a session for the virtual machine XP VS2008. The virtual machine 'XP VS2008' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\zibratjt\VirtualBox VMs\XP VS2008\Logs\VBoxHardening.log'. Result Code: E_FAIL (0x80004005) Component: MachineWrap Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}
|
|||
| #9081 | fixed | After upgraded to v4.0.8 from v4.0.6, windows 7 wouldn't boot | ||
| Description |
After upgrading to v4.0.8, Windows 7 wouldn't but. I restore an older snapshot and still wouldn't boot. I then downgraded it back to v4.0.6 and the machine restored, but after reboot, it went into chkdsk and found disk error, once error was fixed, the Windows boot past the logo and then mouse cursor showed up and the machine stay in this state and doesn't proceed. |
|||
| #9135 | fixed | After upgrading from 4.0.8 to 4.0.10 VM fails to start | ||
| Description |
After upgrading from 4.0.8 to 4.0.10 the existing Win-XP VM fails to start. The error message is complaining about network interfaces and unexpected exception. When open Settings for this particular VM there is an error warning stating that under network there is a host-only adapter without selected device. When trying to select - drop-down list is empty. Workaround - uninstalled 4.0.10 and re-installed 4.0.8. VM is loading normally as it use to. |
|||

