E_NOINTERFACE (0x80004002)

[Kubetts]

Just installed v4.3.2 and same problem... VB is very close to be sent to WC...

If you feel that VMWare etc would be a better choice for you then by all means you should go there.

I use VB from many years, it si better than VmWare, but I can't believe isn't impossible to solve this problem

[Giangi]

...it's what I think me too, but it's really frustating that NOBODY has a clue on it!
The logs are actually useless since the messages reported are present on the v4.2.16 too, only the last statement about the COM interface is different...
I have traced vboxsvc with Sysinternal's Process Monitos, I have seen the classes it query, I have removed VB and manually deleted these registry entries then with ccleaner I have removed other pieces left; I have reinstalled it but, hey, NO WAY.
With my current account I cannot run any version above 4.2.16!
When using a different one there is no problem: I have moved the xml config from the "not working" account over the "working" one and the VMs are there and available! I have done the contrary but the xml config from the "working" account is "not working" on mine.
So it CAN NOT be a problem into the xml config file, it MUST be somewhere on the background process...

...and, last but not least, I cannot re-use my old nickname after I have changed my email address and no one can give me an answer on both the topic I have wrote and the PMs I have sent... To file a new bug on the tracker I would have to use a new nickname but I would prefere keep using mine...

[Giangi]

I am really happy (sigh ) to know that more and more users are facing this specific error...
viewtopic.php?f=6&t=58222
Maybe the two topics should be merged?

[Kubetts]

Maybe I solved the problem:

Login like other user, installed VirtualBox 4.3.2 Oracle VM VirtualBox Extension Pack, logoff and login with my account, start virtualbox in compatibility mode (Vista SP2). For me works

[Oldster]

This is the same problem that I noted with VB 4.2.18 on a windows 7 32bit machine. As far as I know there is no solution yet. The only thing I was able to do was to revert to version 4.2.16 which works OK for me!

[socratis]

With my current account I cannot run any version above 4.2.16! When using a different one there is no problem.

Then why on earth do you believe it's a problem with VBox and not your account? Start checking file permissions, registry permissions and/or other things that differentiate the two accounts.

[Giangi]

Because I'm not alone, because v4.2.18 works, because I have already checked the most obvious places but I do not know the SIDS used for Classes, COM and other hided places! Because on my laptops I keep UAC off and I'm member of the local Administrators group so I do have access to everthing that has not be specifically denied access to my account!
Is it enough?

[socratis]

Is it enough?

No. Try one more thing. In the instructions by mpack it said "Run as administrator" it did not say "Be an administrator". So, right-click on the installer and choose "Run as administrator". There are differences in the two methods of installation. And please don't use red-bold. It hurts my eyes

[Giangi]

As far as I know when UAC is turned off the "Run as Adminstrator" is not needed. When looking into my groups I do have the SID "S-1-16-12288" for the Mandatory Label\High Mandatory Level:

Code: Select all

Nome gruppo                                      Tipo                 SID          
================================================ ==================== =============
Everyone                                         Gruppo conosciuto    S-1-1-0      
BUILTIN\Administrators                           Alias                S-1-5-32-544 
BUILTIN\Users                                    Alias                S-1-5-32-545 
NT AUTHORITY\INTERACTIVE                         Gruppo conosciuto    S-1-5-4      
ACCESSO CONSOLE                                  Gruppo conosciuto    S-1-2-1      
NT AUTHORITY\Authenticated Users                 Gruppo conosciuto    S-1-5-11     
NT AUTHORITY\Questa organizzazione               Gruppo conosciuto    S-1-5-15     
LOCALE                                           Gruppo conosciuto    S-1-2-0      
Etichetta obbligatoria\Livello obbligatorio alto Etichetta            S-1-16-12288

That is the output of whoami /groups from a Command Prompt executed without selecting "Run as Admin" (which is something I never do on my own computers) but it's still referenced in the title as "administrator: " because UAC is turned off. In this scenario there is no need to do "Run as administrator" because that is automatically done by the system
http://technet.microsoft.com/en-us/libr ... S.10).aspx
http://technet.microsoft.com/en-us/libr ... ptBehavior

greenshot_2013-11-05_14-29-36.png (6.83 KiB) Viewed 9288 times

Name translated: User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode
Settings translated: Elevate without prompting

...but even I have re-done the upgrade using the option "Run as administrator", because right now I do not remember if I did try in the past or not...
Guess what? It still doesn't work...

But me too I have configured it to run in Vista SP2 compatibility mode and it works!!!! But that is a workaround and not a solution!!!

My two cents: the UAC manifest configured into the setup are not correct. I am here to do more testing if anyone can give me an executable with very verbose dubug output so to figure out where it stops!!

[Martin]

Are you sure that there are no additional group policies coming with your domain user account?

[Giangi]

Sure because its me that create the group policies for the domain...
And anyway why v4.2.16 works? There must be something different starting with 4.2.18...

[Oldster]

From my point of view, I seem to have a solution to the problem. I've run the installation with "administrator permissions", and in "compatibility mode for Vista SP2". Then I run the program, itself with these same Compatibility options. This has appeared to work for me on my Windows 7 32bit machine!!!

[AllenL]

From my point of view, I seem to have a solution to the problem. I've run the installation with "administrator permissions", and in "compatibility mode for Vista SP2". Then I run the program, itself with these same Compatibility options. This has appeared to work for me on my Windows 7 32bit machine!!!

I think this only affects 32-bit machines. My 64-bit machines did not seem to exhibit this issue.

Early on, I thought when you guys were implying "Run as Admin" you were referring to the installation of the app of which I did but still, error. But then I tried running the app as Admin, and it did work! Quite a hassle though compared to just double clicking the mouse on the icon. You'd have to remember that this is an app that needs to be started differently.

Then I tried the settings of Oldster above and it does work for me as well. Good!

[Giangi]

Here the official bugtracker ticket for anyone willing to update it and/or to be notified on update!
https://www.virtualbox.org/ticket/12087

[Giangi]

On the bugtracker there is the solution: here you are my comments with the steps I have followed!
https://www.virtualbox.org/ticket/12087#comment:41