Jump to content

Recommended Posts

Posted (edited)

Good Morning,

 

I have mounted an image and wish to inject a tgraphics driver into the image.

 

Everytime i try cand run the comman below, it comes up with 'Error 5 - Access Denied' any ideas?

 

dism /image:"C:\Temp\Mount" /add-driver /driver:"C:\Temp\Drivers\graphics\Graphics\ics64.inf"

 

I used this command to mount:

 

Dism.exe /mount-wim /wimfile:C:\temp\CUSTOMBOOT.wim /index:1 /mountdir:C:\temp\mount

 

 

I am an administrator with full admin rights.

Edited by Darylrese
Posted (edited)

As stupid as it sounds are you running UAC and not elevating cmd before running the commands?

 

Edit - Also did you check the zone isn't blocking it on the actual driver file?

 

Steve

Edited by Steve21
Posted

I have indeed turned UAC off and i am elevating the deployment tools command prompt

 

I cant seem to be able to delete the mounted wim either, lots of access denied errors...

Posted

Only two other times I've seen it is when the drivers are blocked from another zone (When you right click on the driver inf and go to properties, it gives unblock option etc?) but that wouldn't affect the other one.

 

Or when an AV is blocking the registry calls, which sometimes happens, especially mcafee!

 

Only other things that spring to mind would be trying it to another non-C drive folder just incase you have weird permissions etc.

 

Steve

Posted

All sorted, folders were owned by 'TrustedSoftware' user, took ownership and replacing child permissions and it successfully injected.

 

I just hope that wont screw up folder permissions on the image itself once deployed

Posted

Ok so once the image was deployed, all the permissions were screwed up on the windows folder and i couldnt install anything.

 

Any ideas how to inject the drivers without having the ownership of files and folders?

Posted

Is this for WDS/MDT? In which case it would be easier to just add them to the WDS server (assuming 2008 R2 or later).

 

I see it's call customboot, is this a boot image or a deployment image? Some drivers are not valid for injection into a boot image (like graphics ones iirc).

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...