Access denied installing drivers as Admin
Hello, when I go to install any device driver, I receive an "Access Denied" failure message. I checked the permissions on the source files and the existing files being replaced, and I have full control (logged in as local admin). I then removed it from its OU(<ou#1>) and restarted to see if it was the group policy, and I was able to install the same source driver files. I did a gpresult on <ou#1> and looked through the group policy being applied, but could not find anything related to driver installation. I'll gladly upload/share the group policy to be looked at, but I can't seem to post it with this message. After putting it back in <ou#1>, I found that the driver store files at C:\windows\system32\driverstore\*.dat only had permissions for SYSTEM(but the admin group owned the files). Using SubInAcl, I added full control to these files for the admin group, which then allowed me to install/update drivers. But when I restart the computer, the permissions for those 5 driver store files are reset back to SYSTEM=full control, owner=admin group. How can I stop the permissions from being reset on these 5 files when the system is restarted? *Note that this is in an Enterprise environment
August 14th, 2012 11:39am

Have you install with elevated rights (Run as Administrator)? M.
Free Windows Admin Tool Kit Click here and download it now
August 15th, 2012 12:06pm

yes, I've tried installing drivers as both the local administrator and the domain administrator
August 15th, 2012 12:11pm

Once again. Have you installed with elevated (priviledged) rights?
Free Windows Admin Tool Kit Click here and download it now
August 15th, 2012 1:50pm

as stated before, yes. see picture for proof (and yes I know this isn't a pic of installing drivers, but DISM uses the same 5 driver index files) 
August 15th, 2012 2:06pm

Hi, Based on your screenshots, Im afraid that you did not run command prompt as administrator. Due to User Account Control is enabled, applications and tasks always run in the security context of a non-administrator account, unless an administrator specifically authorizes administrator-level access to the computer. More details in User Account Control Overview for IT Professionals. Therefore, you can do the following: Method 1: Right click applications or command prompt and run them as administrator. Method 2: Turn off User Account Control. However, it is not recommended. More information: User Account Control What is User Account Control? Hope this helps. Jeremy Wu TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
August 15th, 2012 10:44pm

Thanks for the refresher on the basics of Windows, but I am running the command prompt with elevated permissions and Windows UAC is already turned off. (you can see the full psr on my public skydrive) Note the same window title for every command prompt screenshot I've posted, signifying that they've all been "Run as administrator". If you test opening a command prompt as a standard user and as an administrator on your computer, you'll notice that the window title for each prompt is different. You should take a look at this Microsoft Technet topic to get a better understanding of running programs with different permissions than that of the logged in user.
August 16th, 2012 10:00am

I think your reply is unrespectful with Jeremy, that was only trying to help you... Colobora con el foro: Si la respuesta es de utilidad para resolver tu duda/problema, usa la opcin "Marcar como repuesta". Otros usuarios con dudas similares -en un futuro- lo agradecern.
Free Windows Admin Tool Kit Click here and download it now
August 16th, 2012 1:15pm

It wasn't meant to be disrespectful, but rather to clearly demonstrate my point that he was not understanding, so that we could move past this troubleshooting step. Because I have already stated it twice and Jeremy still disbelieved me, I wanted to show without any doubt that I am running command prompt as administrator with elevated privileges.
August 16th, 2012 1:38pm

Hi, Thanks for the reply. The reason I would like you to check this is that I noticed C:\Users\Administrator>. However, a privileged command prompt should be C:\windows\system32>. Anyway, lets try others: 1. Turn on UAC, run as administrator and see how it works. 2. Create a new user administrator account and test the issue again. 3. Run command whoami /all >C:\whoami.txt and let us know the result in C:\whoami.txt. In addition, please let us know the following: 1. Is the user account a domain or a local account? 2. Is it the build-in administrator account or just a user account named as administrator. 3. Does any other computer in the same domain has the same issue? Hope this helps. Jeremy Wu TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
August 17th, 2012 2:33am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics