Are you struggling with above error:
And you want to know how to solve this error;then
you are at right place. After reading this article you
will be able to solve this error.
To solve this error we need to inject NIC drivers to the
Boot.wim File.
How to Inject NIC/LAN/ETHERNET drivers to Boot.wim
Create a new folder in your C: dive called Tempwim
copy boot.wim file to your C:\tempwim\
image:-
in C:\tempwim folder create 2 more folders named Mount & drivers
copy your NIC/LAN/ETHERNET drivers to drivers folder
but make sure that files are extracted & must contain .inf file
now run Command prompt as Administrator
type the following command one by one :
dism /mount-wim /wimfile:C:\tempwim\boot.wim /index:2 /mountdir:C:\tempwim\mount
the above command will mount Boot.wim file to
C:\tempwim\mount folder
now type the following command
dism /image:"C:\tempwim\mount" /add-driver /driver:"C:\tempwim\drivers\driver.inf"
this command injects drivers to Boot.Wim file
be sure to replace the word "driver.inf" with the name
of your NIC drivers .inf file
Now type the last command
Dism /unmount-wim /Mountdir:C:\Tempwim\mount /commit
You have successfully injected drivers to Boot.wim file
Now just replace your current Windows deployment boot image
with the new which we have modified.
checkout
checkout
Note:- if still getting the same error then just replace the first
command with
dism /mount-wim /wimfile:C:\tempwim\boot.wim /index:1 /mountdir:C:\tempwim\mount
& remaining commands will be same..
command with
dism /mount-wim /wimfile:C:\tempwim\boot.wim /index:1 /mountdir:C:\tempwim\mount
& remaining commands will be same..
That's it....
Work Smarter...
Thank you for share this knowledge this is very useful for this type of technical problem solve....
ReplyDeleteDid not work for me
ReplyDeleteDidn't work for me either. Did you ever find a solution?
DeleteDidn't work for me either. Did you ever find a solution?
DeleteI have just followed all the process but still the same initial issue…
ReplyDeleteWorked for me! After struggling through various sets of instructions, this simplified all the steps AND worked first try. Thanks so much.
ReplyDeletedid not work!!
ReplyDeletewhere do you find the folder nic\lan\ehternet?
ReplyDeletethey all are same i.e. is NIC or LAN or Ethernet
Deleteits worked fine thanks...
DeleteShaikh it worked perfect but..
ReplyDeleteI injected the network driver for the specific hardware pc to the boot image and it worked.
Once I tried another type of hardware pc I got the error again. Now my question is, can I inject the different network driver to the same boot image and each time it will know which one to push out or do I have to create different boot images for each specific hardware pc with different network drivers each?
You can add any driver to the boot, the hardware will detect and select the right one for each netwotk card.
DeleteWorks perfect bro. Thanks
ReplyDeleteThank you a lot!!!! 1 Week trying to fix my boot image, in my case the trick was change "/index:1" to "/index:2" and it works perfect!!!
ReplyDeleteOnce again tank you!
Great stuff, this worked first time! much appreciated!
ReplyDeleteThanks,
ReplyDeleteits worked fine
Works like a charm !!!
ReplyDeleteDear Shaikh.
ReplyDeleteFabulous, Excellent solution.
Many Thanks
It didn't work for me. dism is not recognized as an internal or external command.
ReplyDeleteHOW CAAAAAN IIIIII THAAAAAANNNNNNKKKKK YOOOOOUUUUUUU
ReplyDeleteI Have tears in my eyes
I tried to solve this issue in many many ways without success.
Thank you you gave me hope
thank youg GOOGLE to lead me to this solution
have a great life sir
This comment has been removed by a blog administrator.
ReplyDelete