This is very odd since in the stepįormat and Partition Disk Drives I use a variable called OSDisk then on theĪpply Operating System Image step I use "logical drive letter stored in a variable = OSDisk" I accessed my failed machine via the PE boot process. This was done via Task Sequence \ Create New MDT Task Sequence.
My Unattended.xlm was created when I created a new Settings Package for the
Update for Kernel-Mode Driver Framework version 1.11 for Windows 7 for 圆4-based.This is turning out to be an interesting problem :-)
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. This update is only for Windows 7 x86 or 圆4. If the update is installed, Kernel-Mode Driver Framework v1.11 (KB2685811) is in the list of.
It will scan your Windows 7 first then download and install 64 bit HP official.
#KERNEL MODE DRIVER FRAMEWORK 1.11 OFFLINE INSTALLER 64 BIT# KMDF driver packages that are built by using Windows Driver Kit for Windows 8 can automatically redistribute and install version 1.11 of the files. 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. During driver package installation, the package checks the computer to determine what version of KMDF is currently installed, and then the package updates the files to 1.11 if they are an older version. The Kernel-Mode Driver Framework (KMDF) version 1. 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. msu file.Īdd a Run Commandline step to your capture Task Sequence.
Wusa kmdf-1.11-Win-6.1-圆4.msu /quiet /norestart KMDF supports kernel-mode drivers that are written specifically to use it. Remember to check Package and select the newly created package #KERNEL MODE DRIVER FRAMEWORK 1.11 OFFLINE INSTALLER INSTALL# If you dont want to recapture you image, you can offline inject 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 Once uninstall you the graphics drivers in the Device Manager restart the computer. Step 2: Visit the manufacturers website and download the latest drivers for.
#KERNEL MODE DRIVER FRAMEWORK 1.11 OFFLINE INSTALLER DRIVERS# msu to the mounted WIM – I’m assuming that the. msu is located in D:\CM:\OSD\KMD 1.1.ĭism.exe /Image:D:\Mount /Add-Package /PackagePath:”D:\CM\OSD\KMDF 1.1\kmdf-1.11-Win-6.1-圆4.msu” You need the updated Kernel Mode Driver Framework (KMDF) 1.11 included in your base image. Now we just need to close and commit the WIM:ĭism.exe /unmount-Wim /MountDir:D:\Mount /commit Reasons for failure: Windows 7 Operating system comes with KMDF 1.9 (Kernel Mode driver framework) as part of the image.