Hot answers tagged administrator
If you can run Microsoft/SysInternals Process Explorer you can select the process and see all of the DLLs that have been loaded into the process's memory. That could at least give you a starting point to see what different things have been loaded.
This answer might be a bit late - I had the same issue and it turned out to be because I was trying to run a setup as admin from one my regular user account's private folders (my admin user couldn't see it due to the way my system is setup) I found this out by using the runas command (which is a command line tool for running a program as a different user). ...
Open Windows Power shell (open it as an Administrator) and Run below registry settings from Set-ItemProperty -Path "HKLM:\Software\Microsoft\Windows\CurrentVersion\Policies\System" -Name "EnableLUA" -Value "0" or check below guide, http://www.vmwareandme.com/2013/12/guide-windows-81-always-run-given.html
I used the GPEdit snap in, but couldn't find anything weird. But someone reminded me about the RSOP, or Resultant Set of Policies. While reading the Microsoft documentation, I came across the page for the tools, and found the command gpresult. Checking the help, I saw that if you add the /r switch, it gives a report of the policies in effect. I ran that ...
Only top voted, non community-wiki answers of a minimum length are eligible