In one of my MDT projects I recently struggled with a new issue.
as we all know, we should handle with care when importing drivers, usually I prefer installing a new machine with my deployment, install the missing drivers, and then copy the delta from the “%windir%\system32\DriverStore\FileRepository” folder by using the last modified view.
well, I work for this specific organization for 2-3 years and never had any issue when importing drivers.
as time goes by, new hardware came up, this time Lenovo T440\X240, after importing the drivers with every way known to human kind, I got bumped with failure after windows should boot to complete deployment of programs:
“Windows Could not configure one or more system components. to install windows, restart the computer and then restart the installation”
When this kind of message appear, we don’t have much to do but investigating the Setupact.log and Setuperr.log that located in %windir%\Panther.
so I’ve walked again into WinPE, and checked the errors:
I’ve Bingged for:
CBS Startup: POQ has not been processed yet, aborting startup processing. Startup processing will be attempted again. [HRESULT = 0x80004004 – E_ABORT]
and checked the KB in the first result: http://support.microsoft.com/kb/2494168/en
after reading, I understood that I need to inject the KMDF (Kernel-Mode Driver Framework) and UMDF (User Mode Driver Framework) newer version into my Windows Image (wim file)
also download the newset UMDF from KB: https://support.microsoft.com/en-us/kb/2685813
unfortunately, when trying achieving score that by mounting the image, using Dism add-package and unmounting (+Commit) I moved forward a little bit but still got stuck – my MDT deployment did pass that annoying screen but Windows booted like after sysprep asking me to accepting the EULA. – BUMMER.
before going into re-image with my Capture task sequence and installing the package I tried one last thing,
I’ve imported to the packages node in my MDT console the update and verified that I am using “Inject Packages” in my task sequence and it is targeted to the Selection Profile which holds the new KMDF Update.
started new deployment on T440 and X240 with fingered crossed and…. superb, it worked!
if you are using MDT client task sequence out of the box, you already have the “Inject Package” step and you should just import the update to the console.
Agile IT Solutions
System Center Cloud and Datacenter Management MVP