virtualbox.org

When I launch VirtualBox 2.0 under XP SP3 I get no UI appearing at all.

According to Task Manager, VBoxSvc.exe is running, as is a copy of VirtualBox.exe for each launch attempt. However VBox does not show as an Application and no window appears

What might I look at to try and diagnose the cause, please?

thanks, martin

I'm getting this problem too. I'm running Windows Vista Ultimate x64. Running version 1.6.6 had no problem, until I installed 2.0.0, and now, when launching Virtualbox, I get no UI screen. In Task Manager, it says that VBoxSVC is running, as well as Virtualbox, but the actual program is not open (there's no window!).

Eventually, after a few minutes, the Virtualbox screen will then pop open.

I thought maybe it was because my guest OSes, so I removed EVERYTHING, uninstalled Virtualbox, cleared the registry and hard drive of everything Virtualbox, and reinstalled. Same behavior.

What could be causing this?

Do you have a taskbar entry when you start the VM? If so, then it's a Windows bug that displays the window outside the visible area. This happens with all sorts of programs. You can get the window back if you maximize it, or right click on the taskbar entry and select move and use the arrow keys to get it back on screen.

Sasquatch wrote:Do you have a taskbar entry when you start the VM? If so, then it's a Windows bug that displays the window outside the visible area. This happens with all sorts of programs. You can get the window back if you maximize it, or right click on the taskbar entry and select move and use the arrow keys to get it back on screen.

No task bar entry. Nothing listed under Applications in Task Manager. VirtualBox.exe process remains for hours under Processes in TMgr.

Any log files I can inspect? Nothing in event logs.

thanks, martin

Hmm, log files are in the machine folder under Logs. The VB process should close after you close the VM and have the GUI closed too. This is really strange.

Sasquatch wrote:Hmm, log files are in the machine folder under Logs. The VB process should close after you close the VM and have the GUI closed too. This is really strange.

Where should this Machines folder be, please? Bear in mind I haven't seen the GUI at all yet.

Nothing of note in registery either.

I can find a VirtualBox.xml, just reads:

Code: Select all

<?xml version="1.0" encoding="UTF-8" ?>
<!-- Sun xVM VirtualBox Global Configuration -->
<VirtualBox xmlns="http://www.innotek.de/VirtualBox-settings" version="1.3-windows">
  <Global>
    <MachineRegistry/>
    <DiskRegistry/>
    <USBDeviceFilters/>
    <SystemProperties/>
  </Global>
</VirtualBox>

thanks, martin

By default, all machines are saved in your user profile folder under the hidden folder Application Data. If you changed this location in the General Program settings when you start VirtualBox (the GUI, with a listing of your VMs), then you have to go to that location.

Sasquatch wrote:By default, all machines are saved in your user profile folder under the hidden folder Application Data. If you changed this location in the General Program settings when you start VirtualBox (the GUI, with a listing of your VMs), then you have to go to that location.

There are no files relating to VirtualBox under Application Data (current user or All Users). As mentioned, I've not yet seen the GUI so could not of moved it.

Open to any and all suggestions at this point

thanks, martin

Fully remove VB, clear your appdata and program files folder, reboot and reinstall. If that doesn't work, stick to 1.6.6 maintenance release instead.

Sasquatch wrote:Fully remove VB, clear your appdata and program files folder, reboot and reinstall. If that doesn't work, stick to 1.6.6 maintenance release instead.

Did all that, 1.6.6 also hangs

Is there no log file to view? Debug switch?

thanks, martin

No event logs? What does Taskmanager say about running processes and CPU usage when you start VB?

Sasquatch wrote:No event logs? What does Taskmanager say about running processes and CPU usage when you start VB?

Appreciate your help with this. Back with VB2.0.

System Event log tells me that VB Service and VB USB Monitor Driver both started up fine. No error messages (for VB or anything else) when I launch VB.

In Task Manager, neither VB.exe or VB service are chewing up CPU. VB using 6.6MB, service 8MB. System idle (and otherwise fine and stable).

I've re-registered the service just in case.

Checking VBox.exe with Process Explorer (http://technet.microsoft.com/en-us/sysi ... 96653.aspx) shows 4 threads running initially. After approx 1 minute a thread with the following start address exits:

ole32.dll!StringFromGUID2+0x629

cheers, martin

I just tried it right now again. I get logs and everything in my .virtualbox file folder located in my user profile folder, no problem. But when I open Virtualbox, VBoxSVC.exe shows in Task Manager as well as Virtualbox.exe, but the actual program windows doesn't open till about 30 seconds to a minute later.

I don't know what's causing it.

I am having the same issue actually except my VirtualBox application will eventually open up. It usually takes 3-5 minutes and it only will display after I try to open up the application a second time.

As you are mentioning, I will see as many VirtualBox.exe entries in my Task Manager as I clicked to open. I don't recall having this issue before 2.0.0. I run Vista Ultimate 32-bit as my host OS.

Exactly what I was trying to describe. Eventually, Virtualbox will open, but it takes a long time.

virtualbox.org

Launches but no window visible

Launches but no window visible