virtualbox.org

I install VB 4.1.8. Install goes fine. I go to run it and it nothing happens. I see I get a VirtualBox.exe process running but that's it. VB never opens. No errors in event log. I uninstalled and reinstalled and it just doesn't do anything. Everything else on this system is perfect, no other issues to speak of. If I open VB again, I simply get another VirtualBox.exe process, with no app.

I also have VMware workstation 8.1 on this box. Not sure if there is a conflict with that. VMware workstation 8.1 works perfectly on this box with all my VMs. Was really just trying VB to see about 3D capabilities with nix VMs. I can't even get it to run however. Getting rid of Workstation 8.1 is not an option. If they can't live together then I'll have to drop VB.

Any ideas on this?

Offhand guess, there's a conflict with the VMware. I (and many others) are running Virtualbox on Windows 7 64bit. I know from reading the forums that more than one virtualizer on a host system can cause conflicts.

Were this my PC, I would try a fresh install of Win7 on another hard drive, don't activate it (it can be used for a few days unactivated to try it out), install Virtualbox and see how things go. I could test without toasting my working system.

I've had the exact same symptoms

I recently migrated to a new machine SandyBridge core i7 win7 64bit using z68 chipset mobo
Install of virtualbox works fine but I cant load either the virtual box gui or use any functions in the VboxManager command line.
Virtualbox.exe just hangs until I kill it

If I turn off virtualization in the bios then virtualbox works fine but I need hardware virtualization for my 64bit guests

I've tried with versions 4.1.8, 4.1.6, 4.0.16

(edit: stupid auto spellcheck)

As Scottgus says, these problems may be caused by a confict with another VM manager (something else wants that VT-x feature). It may also be caused by an improper install, or installing without full admin rights etc.

mpack wrote:As Scottgus says, these problems may be caused by a confict with another VM manager (something else wants that VT-x feature). It may also be caused by an improper install, or installing without full admin rights etc.

No other VM software installed.
I've reinstalled many many times all as admin user with full admin rights.

My answer remains as above. I can only point in a direction, but I cannot be there to do the diagnosis for you. Unless all other Win7x64 host users start complaining about the same problem, then the evidence appears to indicate something unusual about your installation.

I'd like to hear if anyone else is running sandybridge z68 chipset with no issues

Do you have installed the so called "XP Mode"? This also conflicts with VirtualBox.
One time I also had to update the Visual C++ 2005 Redistributable to a newer version, to get VirtualBox working. But this may be automatically done by running Windows Update.

scp wrote:Do you have installed the so called "XP Mode"? This also conflicts with VirtualBox.

No

scp wrote:One time I also had to update the Visual C++ 2005 Redistributable to a newer version, to get VirtualBox working. But this may be automatically done by running Windows Update.

yes

Hi!

My system: Windows 7 64 bit, Intel i7, 8 GB RAM

I had the same problem and worked some hours on it, uninstall, reinstall, repair, ... nothing changed. The two VB-Processes started (VBoxSVC.exe used 13% of CPU), but no GUI opened.

Finally a strange reason seemed to be responsible for this problem. During my works, I had plugged on via USB one Canon printer and one Logitech speaker. Just removed both and after killing VB-processes and restart of VB it started in normal manner.
After trying plug in printer only, or speakers only, the result was that the speakers interfered starting of VB, and only if they were already plugged in when windows was started. If plugged in later no problem occured. Besides, as soon as speakers are removed, VB was started once successfully, and speakers were plugged in afterwards, VB could be started without any problem!!

Maybe this can help .. it was very surprising and unbelievable .. but true

Good luck!

Thank you for the idea, you saved my day. I had the same problem (GUI won't start). Unplugging all USB devices also fixed it for me. I have many USB things attached through a hub, I did not try to find which devices causes the problem. I just unplug the HUB, run VB (GUI starts OK now), plug the hub back - and all devices seem to be working normally.