DISM driver injection
Hello getting error 2 when trying to inject network drivers into a mounted boot.wim image. It says it cannot find a file, error 0x80070002. I have googled it, and read the log but cant make heads or tails of it other than i dont know why it is trying to access d:\
Trimmed down logfile (level1)
2012-09-27 11:39:45, Error DISM DISM Driver Manager: PID=2904 Failed to install the driver package 'C:\Drivers\E1c62x64.INF'. - CDmiDriverStore::Import(hr:0x80070002)
2012-09-27 11:39:45, Error DISM DISM Driver Manager: PID=2904 Failed to install the driver package 'C:\Drivers\E1c62x64.INF'. - CDriverPackage::InternalInstall(hr:0x80070002)
2012-09-27 11:39:45, Error DISM DISM Driver Manager: PID=2904 d:\w7rtm\base\ntsetup\opktools\dism\providers\dmiprovider\dll\driverpackage.cpp:433 - CDriverPackage::Install(hr:0x80070002)
2012-09-27 11:39:46, Error DISM DISM Driver Manager: PID=2904 Failed to install the driver package 'C:\Drivers\ixe62x64.inf'. - CDmiDriverStore::Import(hr:0x80070002)
2012-09-27 11:39:46, Error DISM DISM Driver Manager: PID=2904 Failed to install the driver package 'C:\Drivers\ixe62x64.inf'. - CDriverPackage::InternalInstall(hr:0x80070002)
2012-09-27 11:39:46, Error DISM DISM Driver Manager: PID=2904 d:\w7rtm\base\ntsetup\opktools\dism\providers\dmiprovider\dll\driverpackage.cpp:433 - CDriverPackage::Install(hr:0x80070002)
2012-09-27 11:39:46, Error DISM DISM Driver Manager: PID=2904 Failed to install the driver package 'C:\Drivers\ixn62x64.inf'. - CDmiDriverStore::Import(hr:0x80070002)
2012-09-27 11:39:46, Error DISM DISM Driver Manager: PID=2904 Failed to install the driver package 'C:\Drivers\ixn62x64.inf'. - CDriverPackage::InternalInstall(hr:0x80070002)
2012-09-27 11:39:46, Error DISM DISM Driver Manager: PID=2904 d:\w7rtm\base\ntsetup\opktools\dism\providers\dmiprovider\dll\driverpackage.cpp:433 - CDriverPackage::Install(hr:0x80070002)
2012-09-27 11:39:46, Error DISM DISM Driver Manager: PID=2904 Failed to install the driver package 'C:\Drivers\ixt62x64.inf'. - CDmiDriverStore::Import(hr:0x80070002)
2012-09-27 11:39:46, Error DISM DISM Driver Manager: PID=2904 Failed to install the driver package 'C:\Drivers\ixt62x64.inf'. - CDriverPackage::InternalInstall(hr:0x80070002)
2012-09-27 11:39:46, Error DISM DISM Driver Manager: PID=2904 d:\w7rtm\base\ntsetup\opktools\dism\providers\dmiprovider\dll\driverpackage.cpp:433 - CDriverPackage::Install(hr:0x80070002)
2012-09-27 11:39:46, Error DISM DISM Driver Manager: PID=2904 d:\w7rtm\base\ntsetup\opktools\dism\providers\dmiprovider\dll\drivermanager.cpp:1063 - CDriverManager::Internal_DoAddDriverPackage(hr:0x80070002)
2012-09-27 11:39:46, Error DISM DISM Driver Manager: PID=2904 d:\w7rtm\base\ntsetup\opktools\dism\providers\dmiprovider\dll\drivermanager.cpp:519 - CDriverManager::ExecuteCmdLine(hr:0x80070002)
Thanks any help greatly appreciated i am soooo close!
Answers (2)
drive archive missing some files
Ok I just ran the first driver you need added without problems
I am using WAIK 3.0
http://www.microsoft.com/en-us/download/details.aspx?id=5188
copied the winpe.wim from C:\Program Files\Windows AIK\Tools\PETools\ia64
Comments:
-
do you have all the files needed in the driver directory and decompressed - SMal.tmcc 12 years ago
-
Hi there SMal.tmcc...
I finally got it to work. Thanks to you... your screen capture of the drive archive showed me that I was missing files. I feel really stupid about it!! Thank you for your patience and support. I was feeling like i would never figure this out. I have learned a lot. Again thanks to people like you who go out of their way to help, that this community will thrive!
Thanks very much.
Advkace - advkace 12 years ago -
Usually when you get stuck, another set of eyes is the quickest solution. - SMal.tmcc 12 years ago
-
DOH! I did the exact same thing, I only grabbed the files with the same name as the INF, didn't realize there were other files the driver needed! Ironically I ran into this with the EXACT same driver! - Arcuss88 9 years ago
if this is a syspreped wim file you can also extract the drivers and place them in a folder under windows\inf
Comments:
-
Hi there yes i saw the page when googling that your first link points to "You then need to take these drivers and make them apart of your OS Deployment - Driver Injection process in order to complete the process" That part is blushed over the rest of the answered question dosent apply to my situation. Thank you though! - advkace 12 years ago
-
sighh... your second link is interesting but seems like it may be an interesting process to test if i had the time. Would completely change the way i do things. I just need to inject these network drivers to this winpe.wim image like yesterday. Thank you for your replies however. i do appreciate it. - advkace 12 years ago
-
if you have the win mounted r/w just make a subdir under windows\inf copy the files into there and commit those changes and dismount - SMal.tmcc 12 years ago
-
hi i copied the 3 network drivers into "c:\windows\inf\network drivers"
commited the image and unmounted.
created and burned the iso
booted into winpe env.
i could not get a ipconfig.
I could not get an ip address. the networkdriver.inf being in a subdirectory cause this?
Thanks!
advkace - advkace 12 years ago
-
since they are network drivers you can always copy them as a mid level task to windows\inf\somedirectory and when it finishes it will find them when coming out of sysprep
place them on the k2000 in petemp or on a network share and then
md c:\windows\inf\mydrivers
xcopy y:\driverstocopy c:\windows\inf\mydrivers /q /y - SMal.tmcc 12 years ago-
the placement only works for a sysprep'd wim file not a winpe wim. - SMal.tmcc 12 years ago
-
I may be on the wrong track, I was thinking you are trying to add the drivers to a wim image to deploy with the kace 2000, you are talking your winpe boot environment.
Is this for a kace 2000 boot or some other?
If for a Kace 2000 boot let me know and I can point you how to update your boot environement on the kbox. If it is for some other
http://technet.microsoft.com/en-us/library/cc749350(v=ws.10).aspx - SMal.tmcc 12 years ago -
Hello SMal.tmcc,
Thanks for your help. We use a k1000, what i am using is a winpe boot environment. I will check your link. thanks
edit.. peimg is not supported with win7 so i am back to my DISM woes and error messages. - advkace 12 years ago -
A 1000 to image not a 2000? interesting
http://social.technet.microsoft.com/Forums/en-CA/w7itproinstall/thread/e26aac83-6c81-4e63-9ef8-6a3b725b6813
http://technet.microsoft.com/en-us/library/dd799289(v=ws.10).aspx - SMal.tmcc 12 years ago -
No we have a k1000 but I am not using it for imaging.. there is no kbox used for imaging at my workplace.. sorry for the confusion. I appreciate your links but i am aware of the commands and the syntax required. Hence the DISM log files above. What i am looking for is some clarification as to why i am getting these errors. I have tried recursive and single INF injection i ALWAYS get these errors. Infact i havn't been able to inject any network drivers into this image. I can however put other INF in... but alas i NEED the network drivers above.
Any help with the above error msg's please anyone??? - advkace 12 years ago -
Are you trying this on a 64bit machine and have the 64bit waik and winpe.wim? - SMal.tmcc 12 years ago
-
yes 64bit ... i beleive so on the waik discs it has x86 ia64 and amd64 directories that i can install on the technician machine. On my machine i cant mount it freezes at 3-5 percent. It does mount (sort of) but i need to reboot. On a virtual machine with a clean install (win7 ent 64)it mounts but i cant inject drivers its the farthest i can get. It gives the error log above. - advkace 12 years ago
-
see new answer, so I could attach pics. - SMal.tmcc 12 years ago
