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.
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”
Although 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.
I’m well aware that there are several methods to achieve the goal, but here is two options I have used.
Download the new version om KMDF 1.11 from http://www.microsoft.com/en-us/download/details.aspx?id=38423
Create a Package that contains the KMDF .msu file.
Add a Run Commandline step to your capture Task Sequence.
Use the following Command line:
wusa kmdf-1.11-Win-6.1-x64.msu /quiet /norestart
Remember to check Package and select the newly created package
Click OK and create a new capture.
If you dont want to recapture you image, you can offline inject the .msu to your WIM.
Open a command prompt as Admin.
First 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:
DISM.exe /Mount-Wim /WimFile:D:\CM\OSD\OSImages\Win7_Ent_SP1_x64_1.0.0.wim /index:1 /MountDir:D:\Mount
Second we need to apply the .msu to the mounted WIM – I’m assuming that the .msu is located in D:\CM:\OSD\KMD 1.1.
dism.exe /Image:D:\Mount /Add-Package /PackagePath:”D:\CM\OSD\KMDF 1.1\kmdf-1.11-Win-6.1-x64.msu”
Now we just need to close and commit the WIM:
Dism.exe /unmount-Wim /MountDir:D:\Mount /commit
Last thing to do, is to update the DPs of the image, and we are ready to continue the deployment.