Normal vs. Headless

[darrenkdean]

Good Afternoon,

I have VirtualBox 5.1.4 running on a Ubuntu 16.04 64-bit host. I have a Windows 10 Enterprise 64-bit VM running as a guest. VirtualBox works perfectly when running in Normal mode. No crashes, freezes, & calling remote apps into Ubuntu from the Windows 10 Enterprise guest O/S works flawlessly. The challenge that I'm running into is that when I launch the Windows 10 VM in headless mode, the VM shows aborted when I try to launch a remote app. Additionally, if I don't try to launch a remote app, but rather click Show in virtual box it will bring up & show me the Windows login screen. That being said, the moment I click inside of the VM to login, the VM aborts.

I'm relatively new to VirtualBox & don't know where to begin. Any guidance or suggestions would be greatly appreciated!

SC1.png (79.96 KiB) Viewed 2544 times

SC2.png (62.46 KiB) Viewed 2544 times

Best-

Darren

[JSA]

Good Afternoon,

the VM shows aborted when I try to launch a remote app. Additionally, if I don't try to launch a remote app, but rather click Show in virtual box it will bring up & show me the Windows login screen. That being said, the moment I click inside of the VM to login, the VM aborts.
Darren

By remote app, do you mean you were trying to launch an application in the windows 7 machine via RDC? Or something else?

If you launch it in the manager, and select detachable does it work differently?

[CheeseBoy]

Hi Darren,

I stumbled upon your post because I have exactly the same problem.
I run a Windows 10 guest on Ubuntu 16.04 (Gnome in my case), and it it fails to produce a display if I start it with the headless argument.
Clicking "Show" in the GUI makes it crash.

After poking around I found I had to disable the 3D acceleration when I need to access it through RDP from another machine:

Code: Select all

vboxmanage modifyvm "Win 10" --accelerate3d off && vboxmanage startvm "Win 10" --type headless

I thought I should share.

Kind regards,

/Nik