msu to the mounted WIM – I’m assuming that the. msu to your WIM.įirst we need to mount the WIM file – i’m assuming that the WIM is located in D:\CM\OSD\OSImages and that the Mount dir D:\Mount exists:ĭISM.exe /Mount-Wim /WimFile:D:\CM\OSD\OSImages\Win7_Ent_SP1_圆4_1.0.0.wim /index:1 /MountDir:D:\Mount If you dont want to recapture you image, you can offline inject the. Remember to check Package and select the newly created package msu file.Īdd a Run Commandline step to your capture Task Sequence. I’m well aware that there are several methods to achieve the goal, but here is two options I have used.ĭownload the new version om KMDF 1.11 from Ĭreate a Package that contains the KMDF. The problems i have seen is when Windows setup tries to install component, and error message pops up and saying something like “Windows could not configure one or more system components”Īlthough it seems like the same version of KMDF are downloaded and approved in WSUS/SUP, it is not released the same date as the updated version, so that means we have to create a package for it, or offline inject it into our image. If you’re experiencing problems deploying Windows 7 images to newer hardware such as Lenovo T440 or X240, it might be due to the drivers for those models, are requiring a newer version of Kernel Mode Driver-Framework.
