virtualbox.org

Greetings! Whenever I try to open Virtualbox on my non-admin account, I get this message: Any ideas how I can fix this?

Windows 10 Pro N 1803
Latest stable Virtualbox release, installed it literally 20 min ago

Batman8675 wrote:Whenever I try to open Virtualbox on my non-admin account

Does this mean that if you open VirtualBox with an admin account, it works?

It looks like it has not been installed correctly, i.e. for the current user.

You need to use "Run as administrator" from your normal account to run the VirtualBox installer. This is very different from logging in using an "Admin" account and installing for that user account.

Hello!
I've got the same error mesage on my PCs under user unprivileged account. And I've found the reason of this error in incorrect permissions set for COM Object "VirtualBox Application". When I've set the default permissions for access and activation, error message has gone.
I think that the virtualbox windows setup application sets incorrect permissions for COM object. Please help me.
Thank you.

Capricorn404 wrote: I think that the virtualbox windows setup application sets incorrect permissions for COM object. Please help me.

(A) VirtualBox doesn't have a setup application, the apparant application is just a wrapper for MSI, the standard built-in Windows app installer.
(B) Make sure you run the installer for the intended user account, not while logged in as the "Admin" user. With your normal user account, use "Run as administrator" to request temporary elevation of privileges.

I know this is old, but I just ran into this, and it had nothing to do with admin/installation. Instead, in my case the problem was that for some reason I had a vbox process running in the background, and when I tried to launch/open vbox I got this same error. I setup my VMs to start up automatically (just a shortcut in my startup folder), so that's probably why, but this was the first time it happened, and even though my VMs did start up automatically I shut them down, so I would've assumed there was no more vbox process running.

In any case, if anyone runs into this too, check your task manager, and manually kill any vbox process. Good luck.

It's a good observation. Especially if someone is in the habit of auto-starting headless VMs and there being no sign that a VM is running - unless you check the tasklist. I guess the error could be more informative than "access denied" though!

I had the same problem.
The Virtual Box Manager could not write the *.vbox file.
The disk has no empty space. The *.vbox file size is zero and is corrupt.
Copying the *.vbox-prev file to *.vbox fixed this problem.

Greetings, Bernhard

Unless you get "unable to create COM object" then it is not the same problem. Please create your own topic to discuss your problem.