[Invalid] An issue I have while attempting to run Settings, and things as admin.

[HeardVenus]

Hello!
I've been having an issue today. I never used VBox in a couple of months because I switched to VMware. However I'm coming back, and I'm having an annoying error while trying to Run apps as admin, and running settings. I get an error saying "This file does not have a program associated with it for performing this action. Please install a program or, if one is already installed, create an association in the Default Programs control panel.". I tried to google it, did all the "fixes", none worked, I then loaded my snapshot to go back. I had this issue when I was trying to edit the registry. I edited the names of the Disk drives, Display adapters, and DVD/CD-ROM drive. I also got the error when I tried going to "Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall", and added a DWORD named "SystemComponent", and changed the value to 1; to hide the GA in the uninstall list, the second time, I just deleted the folder containing GA in the uninstall registry. The reason why it is bugging me is because I did this before, and it worked. I never had problems. This is my 3rd time installing windows on the VM (yes i forgot to make a backup of the registry). Should I downgrade to the 5.X.X versions? Or do you guys have any ideas? (sorry if I'm being an idiot here). Thanks!

[mpack]

Why do you need to run apps as admin?

And what "apps" anyway?

[HeardVenus]

By that I mean cmd in admin, any program, I can't run any program as admin. The reason being, I need to install programs on it. Thus I need admin perms

[socratis]

The only time you need admin access for VirtualBox is during installation, and that's because it needs write access to the %PROGRAMS% and %SYSTEM%. After that...

Running VirtualBox as an admin is strongly discouraged!

[HeardVenus]

No, thats not what I mean. I mean running progams inside the VM as admin, gives me the error, sorry for the misunderstanding

[socratis]

Then it's purely a guest problem, absolutely nothing to do with VirtualBox. If that's what you meant all along, the question is [Invalid] and I'm going to mark it as such...

Plus, not in "Windows Hosts", you don't have an issue with your host, that threw us off as well...
Please chose the section more wisely in the future...