Ticket #16003 (new defect)

Opened 12 months ago

Last modified 12 months ago

Remove the "Start after installation" option from Windows installer

Reported by: socratis Owned by:
Priority: major Component: installer
Version: VirtualBox 5.1.6 Keywords: installer, user context, Run as Administrator
Cc: Guest type: other
Host type: Windows


It is becoming increasingly clearer that with Windows installers you have to install VirtualBox with the "Run as Administrator" option after right-clicking on the installer. It is the only way to make sure that the drivers are installed as they should and are not rejected (silently sometimes) by Windows and UAC.

The problem is that if a simple user uses that tool, at the end of the installation when the installer offers to launch VirtualBox, then VirtualBox runs under the context not of the user that did the installation, but under the Administrator context. So if a user starts immediately to use VirtualBox and creates a new VM, that VM won't be there next time the user re-launches VirtualBox. It's going to be in the Administrator's account!

Solution: remove the "Start after installation" option at the end of the installation. The installer finishes and the user launches VirtualBox under their own user context, as they would do it normally every other day.

PS. It doesn't have to be a simple user, driver installation fails sometimes even with an administrator user, so the "Run as Administrator" is becoming mandatory. Simply in that case the issue does not manifest itself.

Change History

comment:1 Changed 12 months ago by frank

I never understood why "Run as Administrator" is really required, at least here it is not. I guess it depends on installed 3rd-party software...

comment:2 Changed 12 months ago by socratis

I don't know if it is 3rd-party software or not. It may be group policy AFAIAK, or something else. It actually became a problem after Windows 7 I believe, where "Driver Signature Enforcement" was getting more and more in the way of installing programs, especially kernel drivers. There was a discussion in the forums, where we came to the consensus that the only "sensible" way these days would be to direct users to install VirtualBox using the "Run as Administrator". No more headaches; *a lot* of issues resolved.

Actually, among the snippets that I have handy, to reply to the forums, I have one that goes:

  • Make sure you allow VBox to install the filter driver on the host - which includes making sure your host doesn't silently reject non-MS drivers (Google for Driver Signature Enforcement).

That alone, took care of lots of complaints about Host-Only and Bridged adapters not getting installed, USB filters not working, etc. I'll try to locate the discussion, although it's been several months that we've had it. Maybe more than 6 to 9 months old...

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use