Permanently stuck Starting VM

Discussions related to using VirtualBox on Windows hosts.
Locked
User98763245
Posts: 1
Joined: 24. Sep 2014, 16:59

Permanently stuck Starting VM

Post by User98763245 »

When I create a new OS it's permanently stuck when I try to start it
Attached large image.

I've tried a lot of things to no avail.
I can't even get to the step to select the image for the OS.

My Setup
> Windows 7 Desktop, 64bit, SP1, up to date
> 3 graphics: GTX 650 Ti, GTS 450, 8400 GS
> 4 monitors
> i7 970

Tried
> Restart Windows
> Disable AntiVirus/Firewall
> Uninstall, Reinstall VirtualBox
> Delete \Users\me\.VirtualBox files
> Different settings for the VM including Ubuntu, CentOS, dynamical and fixed space, 512mb ram to 4gb ram, 4mb to 128mb graphics ram
> Formatted Drive I'm installing VB on and the VMs on

> Used an older VirtualBox version: throws this error during installation: Attached small image

> Observations: When VB is stuck I can't shut it down or shut down Windows anymore. Closing or cancelling the windows doesn't work. Killing processes through Task manager has no effect. Shutting down Windows won't complete. Can only reset PC to get a fresh boot.


Help please

Log file from \users\me\.virtualbox (there are several)

Code: Select all

VirtualBox COM Server 4.3.16 r95972 win.amd64 (Sep  9 2014 17:22:20) release log
00:00:00.000000 main     Log opened 2014-09-24T14:33:16.947104000Z
00:00:00.000000 main     Build Type: release
00:00:00.000000 main     OS Product: Windows 7
00:00:00.000000 main     OS Release: 6.1.7601
00:00:00.000000 main     OS Service Pack: 1
00:00:00.015600 main     DMI Product Name: X58A-UD5
00:00:00.031200 main     DMI Product Version:  
00:00:00.031200 main     Host RAM: 12286MB total, 10452MB available
00:00:00.031200 main     Executable: T:\VirtualBox\VBoxSVC.exe
00:00:00.031200 main     Process ID: 4644
00:00:00.031200 main     Package type: WINDOWS_64BITS_GENERIC
00:00:00.577201          HostDnsMonitorProxy: Host's DNS information updated:
00:00:00.577201          DNS server 1: 192.168.1.254
00:00:00.577201          DNS domain: home
00:00:00.608401          VDInit finished
00:01:50.417636          ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={480cf695-2d8d-4256-9c7c-cce4184fa048} aComponent={Machine} aText={This machine does not have any snapshots}, preserve=false
00:02:30.059923          ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={480cf695-2d8d-4256-9c7c-cce4184fa048} aComponent={Machine} aText={Machine is not locked for session (session state: Unlocked)}, preserve=false
00:07:43.676184          ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={c20238e4-3221-4d3f-8891-81ce92d9f913} aComponent={ProgressProxy} aText={Result code is not available, operation is still in progress}, preserve=false
00:07:49.042594 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={05f2bbb6-a3a6-4fb9-9b49-6d0dda7142ac} aComponent={Medium} aText={Medium 'T:\Virtuals\CentOS-6.5\CentOS-6.5.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false
00:07:49.042594 Watcher  ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={fafa4e17-1ee2-4905-a10e-fe7c18bf5554} aComponent={VirtualBox} aText={The object is not ready}, preserve=false


No idea what to do :(
Attachments
gh8fsBv.png
gh8fsBv.png (67.24 KiB) Viewed 1950 times
RcuBBmo.png
RcuBBmo.png (7.62 KiB) Viewed 1950 times
Bhajan
Posts: 3
Joined: 26. Sep 2014, 02:44

Re: Permanently stuck Starting VM

Post by Bhajan »

Had the exact same issue. Solved by installing older version of VirtualBox.

First I uninstalled my current version. Deleted all vbox folders in the Users(me) directory. This may not have been necessary though...

I created this account just to answer this question so it won't let me post links yet, but the VirtualBox version that worked for me is: 4.3.2 r90405

I got it from filehippo.

Hope this helps.
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: Permanently stuck Starting VM

Post by mpack »

See the "security issues" sticky at the top of this forum.

Locking this duplicate thread.
Locked