Have you seen this error when trying to deploy a new machine model? “Windows could not configure one or more system components. To install Windows, restart the computer and then restart the installation.” It is most likely due to the fact that the base image is not updated with the latest Kernel Mode Driver a Framework, which currently is 1.11. You can download the hot fix separately here: This patch is also included in the latest Windows Update patches, so if your image is fully updated, you shouldn’t be seeing this issue. As far as I know there are three different solutions for this issue: 1. Update the base image with the hotfix.
Install the newest updates on the base image. The hotfix is included in the Windows Update patches. Inject the hotfix offline.
I have not tried this myself, but here is a blog post on how to do it. Hey Daniel, thanks a lot. This saved me hours. In SCCM2012R2 it’s a one click thing to update the image with hotfixes and patches. @wasif: I did it in our old 2007R2 environment some years ago. I used DISM to mount the wim and then inject the updates. It’s like: DISM /Mount-Wim /WimFile:C: whereveryourwimfileis.wim /index:1 /Mountdir:C: Temp Mount then inject the updates/patches/whatever DISM /image:C: Temp Mount /Add-Package /Packagepath:C: whereveryourpatchesare then save it and unmount it DISM /Unmount-Wim /Mountdir:C: temp mount /commit DISM /Cleanup-Wim Then you have to redistribute the wim and hope that it works.
Contents. Relationship to WDM In general, KMDF supports drivers that were written for the, and it runs on WDM. WDM is the driver model used since the advent of Windows 98, whereas KMDF is the driver framework Microsoft advocates and uses for Windows 2000 and beyond.
In general, since more features like and are handled by the framework, a KMDF driver is less complicated and has less code than an equivalent WDM driver. KMDF is object-based and built on top of WDM. It provides an object-based perspective to WDM, following the architectural mandate of its superset, WDF. The functionality is contained in different types of objects. KMDF implementation consists of:.
and. I/O queues. (DMA). (WMI).
See also. (WDF). (UMDF) Notes.
In a recent by fellow Rockstar, he announced that many of the new Dell models (this is likely true with other vendors as well) require drives based on the updated Kernel Mode Driver Framework (1.11 at the time of this writing) in order to function properly. With this new driver framework, Microsoft of course provides a that can be installed or injected into your Windows 7 image. Now here is the “gotcha”, in order for this to work for OS Deployments, you have 2 options:. Build a brand new WIM file and inject the hotfix (using MDT or DISM). Then import that WIM into SCCM for deployment, test, retest, retest, deploy to production.
Package it up and inject it offline during your existing deployments. I don’t know about you but I prefer #2 and will inject the hotfix during my next image build. So lets go over the steps on just HOW to inject this hotfix (or any really) in an offline way using your existing OSD Task Sequence. First things first! Get the one appropriate for your architecture. Extracting the Files Ok, so you’ve downloaded the necessary files, placed them into a folder labeled “Windows 7 KMDF 1.11” or something like that. Next we need to extract the CAB file out of the.MSU since that is what DISM will use later on.
I prefer to use a tool like 7zip to do this. Just right-click, extract and voila! Your folder should now look something like this: Package the Files Now I’m not going to go into details here, I assume that you already know how to create an SCCM package so copy your files, create your package (no program needed) and distribute the content to your DP(s). Task Sequence Ok, now the “dirty” work. Setting up your Task Sequence to inject the update offline. The first thing you’ll want to do is check your Format and Partition step.
Specifically, we are looking for (or need to set) a variable used to store the “real” drive letter for our OS partition. As you can see from the below screenshot, I’m using “ OSDisk” as the Task Sequence variable. Next we need a new Run Command Line Step to create a Scratch directory used by DISM. I create this because I actually inject quite a few items offline (depending on the scenario) and ensures that DISM has enough space to work with. This step goes anywhere AFTER the OS WIM is dropped onto the system but BEFORE the Setup Windows and ConfigMgr step runs. I have mine after the Apply Windows Settings step. After the Scratch directory has been created (this gets removed as part of a Post-OSD cleanup script) we add yet another Run Command Line Step to actually inject the update.
Here we are using DISM.EXE to inject the.CAB file we extracted earlier. Pay special attention to where%OSDisk% is referenced. You may need to change this to whatever variable you are referencing in your Format and Partition Step. If you are having trouble reading that command, here it is (watch for word wrap!): cmd.exe /c X: windows system32 dism.exe /ScratchDir:%OSDisk% Scratch /Image:%OSDisk% /Add-Package /PackagePath:%SMSTSMDataPath% Packages EB20019E Windows6.1-KB2685811-x64.cab And there you have it. Once these steps apply your driver framework should be updated. As Windows 7 first boots into the OS and begins to process the drivers you injected, it will be working with the updated framework and your system (and deployment tech) should be happy.
I ran into the same issue today since my Task Sequence was advertised to run from the DP directly so the package was never downloaded and I was not able to use the%SMSTSMDataPath% variable. Instead I found another variable available in SCCM 2007 that pointed to the DP location on the network directly so my PackagePath section looks like: /PackagePath:%SMSTSEB20019E%Windows6.1-KB2685811-x64.cab. Replace the “EB20019E” portion with your actual package ID. The variable should reference the network DP location like the following “ SERVERNAME SHARENAME EB20019E ” and includes the trailing backslash so you don’t need it in the command line. The package still needs to be referenced in the Command Line step or the variable won’t be active during deployment.
Thanks for the post, very helpful. However, I am getting the following issue when trying to update my Deployment Share in MDT2013 with the package: Deployment Image Servicing and Management tool Version: 6.3.9600.16384 Image Version: 6.3.9600.16384 Processing 1 of 1 – Adding package PackageforKB268581131bf3856ad364e35amd646.1.1.11 Error: 0x800f081e The specified package is not applicable to this image. The DISM log file can be found at C: Windows Logs DISM dism.log Exit code = - Do you know how I could resolve this? I believe the issue is that the Windows OS version I am deploying (6.1.7601) does not match the OS version of the hotfix (6.1.1.11). Is there a different version of the hotfix I should be downloading, or a possible work around to get the deployment share updated with the package properly?
I’ve followed the Dell site here to your page. For me, the problem is that the brand new laptop (E7400) requiring this hotfix doesn’t even allow it to launch the network driver correctly in WinPE, therefore it doesn’t get an IP address and fails to load the build process. How would injecting a hotfix into the image help with that, when it won’t even get as far as loading the image? I’m interested to know more as we’re trying to image laptops straight out of the box, it looks like we’d have to try and allow windows to load and then install the update before imaging. Here is a suggestion Instead of%SMSTSMDataPath% you may need to use C: SMSTaskSequence in your path as%SMSTSMDataPath% will evaluate to various places under WinPE depending on how many partitions/drives you have when you partition your HDD – i.e.
I believe it will always evaluate to the largest drive. So, if you have a single partition, then it will be C: SMSTaskSequence, but if you have two partitions or a, second drive, that is larger then it will evaluate to D: SMSTaskSequence, etc. I have seen some KB articles stating that for this reason, using%SMSTSMDataPath% in a Task Sequence should be avoided. This may be what is causing some of the failures others are experiencing.
It was not working for me until I made this adjustment in my TS. HI I have used the same command line, cmd.exe /c X: windows system32 dism.exe /ScratchDir:%OSPART% Scratch /Image:%OSPART% /Add-Package /PackagePath:%SMSTSMDataPath% Packages PR100152 Windows6.1-KB2685811-x64.cab Where OSPART is my task sequence variable in Format and Partition Disk. But I’m getting the below error, Unable to access the image. I tried it w/o the path in front of DISM. I get the following TS error: COM SMSPKGH$ CH2000E0 with default account Connection request for “.COM SMSPKGH$ CH2000E0” No credentials available for connecting to “.COM SMSPKGH$ CH2000E0”.
See whether the share has already been connected. Connecting to “.COM SMSPKGH$ CH2000E0” Successfully connected to “.COM SMSPKGH$ CH2000E0” Resolved source to ‘.COM SMSPKGH$ CH2000E0’ Command line for extension.exe is “%1”%.Set command line: Run command line Working dir ‘.COM SMSPKGH$ CH2000E0’ Executing command line: Run command line Process completed with exit code 3 Error: 3 The system cannot find the path specified.
![]()
Command line returned3 Entering ReleaseSource for.COM SMSPKGH$ CH2000E0reference count 1 for the source.COM SMSPKGH$ CH2000E0 before releasing Released the resolved source.COM SMSPKGH$ CH2000E0 I tried moving this step after the step that add’s the computer to the domain, but it still does not worked. I also tried anabling the “Allow this package to be transferred via multicast (WinPE only)” package property and that didn’t work either. There are no entries in the DISM.log with today’s date. It’s not getting that far. I’ve confirmed the share exists and the full path to the file is correct.
So the “dp0” part seems to be working. It’s just that the task cannot access the share. I’m trying to deploy this.msu file in an image capture TS. It’s been packaged for use in SCCM, and is being called in the TS via the Install Software object. When the SCCM Program properties does not specify wusa.exe (wusa.exe kmdf-1.11-Win-6.1-x86.msu /quiet /norestart) in the command line, the installer fails with an unknown error reported. When the wusa.exe does preceed the package name, the installer runs without error, returns win32 exit code 0, and the image build and capture proceed as expected. However, when that.wim file is deployed to a machine via an SCCM TS, the KMDF 1.11 is not shown in the Add/Remove Programs Show Windows Updates section.
Then, when the package (kmdf-1.11-Win-6.1-x86.msu) is run on that very same machine through double clicking in a Windows Explorer session, the package executes and actually installs the KDMF. Any thoughts? This is what I get upon doing what is described in the article. Note the “UNC PATHS ARE NOT SUPPORTED.
DEFAULTING TO WINDOWS DIRECTORY” smsts.log: CMD.EXE was started with the above path as the current directory. InstallSoftware 12:12:33 p.m. 1844 (0x0734) UNC paths are not supported. Very grateful for the information I incorporated it faultlessly into our main W7 task sequence, but it didn’t work when running from stand alone USB sticks, despite ticking the ‘package’ box and browsing to the KB2685811 package. I was thinking of adding another command line after the one you suggested if exist e: sms pkg b010055b windows6.1-KB2685811-x86.cab cmd.exe /c X: windows system32 dism.exe /ScratchDir:%OSDisk% Scratch /Image:%OSDisk% /Add-Package /PackagePath:e: sms pkg B010055B Windows6.1-KB2685811-x86.cab but wondered if there was perhaps a more eloquent way of doing this. Thanks in advance James. I am trying to get this to work, but running into a few issues.
I am hoping you can help! The original command you wrote won’t work for a TS that is running directly from the DP.
Since it doesn’t copy the package locally, it is unable to find the package. I figured I could work around this by using the%SMSTS variable and running from the DP directly, but that also fails because I get “UNC paths are not supported. Defaulting to Windows directory” This is the one that fails: cmd.exe /c X: windows system32 dism.exe /ScratchDir:%OSDisk% Scratch /Image:%OSDisk% /Add-Package /PackagePath:%SMSTSPKG00001%Windows6.1-KB2685811-x86.cab Is there a way to get this to work while running from the DP? I tried creating a program instead, but obviously that can only run after the SCCM client is installed. Hi @ everyone!
I’ve tried this nice tutorial and it works great for me with this command line for network install: cmd.exe /c X: windows system32 dism.exe /ScratchDir:%SYSTEM% Scratch /Image:%SYSTEM% /Add-Package /PackagePath:%SMSTSMDataPath% Packages PAT0005C Windows6.1-KB2685811-x86.cab but now the problem if i create a ts MEDIA standalone it everytime brings the same error, that the file can not be found. C:= system x:= boot and variable d: or e: (if i’ve a cd rom) = usb-stick. If i set up over media it wont copy the package to%SYSTEM% SMSTaskSequence Packages PAT0005C and so i’ve created a mkdir and an xcopy bevore dism starts. But then dism have not enough privilleges to inject the cab file!!?? If i mount the wim file directly with dism and try to inject the cab file i’ll get the error 2 that i’ve not enough rights to access the image folder or image’s windows folder!? Can anybody please help me to create a task sequence for both DP and standalone images?! We have some Dell E6440 laptops and I’m kinda lost on what I need to do as far as getting this hotfix to upload to our DP/TS.
Free Download Kernel Mode Driver Framework 1.11
I’ve downloaded the fix on our SCCM server and I’ve made a package for it but when I try to run the command, cmd.exe /c X: windows system32 dism.exe /ScratchDir:%SYSTEM% Scratch /Image:%SYSTEM% /Add-Package /PackagePath:%SMSTSMDataPath% Packages PAT0005C Windows6.1-KB2685811-x86.cab I’m lost as to what variables am I to change on our side. If someone could break this down line by line it would be greatly appreciated. Thanks, Andre. Hoping this is still being monitored, but judging from a lack of answers lately, I’m not so sure.
I’m confused as to how the Task Sequence is to know to download the package when it’s not referenced anywhere in the TS itself (unless I’ve missed that step somewhere). From what I can tell, we create to Run Command Line tasks, 1 to create the scratch directory and the 2nd to install the Hotfix. While the command line references the package location as a switch, the TS itself never references it and therefore never downloads it, causing that package location switch to simply fail out. Again, maybe I’ve just missed something obvious and I’m hoping that it can be pointed out. As it stands now, I’ve done what’s stated and it fails saying it cannot file the file location. I open up SMSTaskSequence and the package for the hotfix is not there. I am one of those people who have both the KMDF and UMDF updates integrated into my WIM for some time now, but now that we are deploying newer Dell models like E5x40s, E6x40s and the M6800 I have seeing this issue intermittently.
Maybe 10-15% of deployments to these machines fail where device drivers are being installed while the rest of the deployments go fine. I have tried generating a new WIM file and that did not help. I have verified both my original WIM and new WIM have the updates integrated by checking with DISM. I even made a WIM without the updates and integrated in the method Dustin shows and still had failures happen. It seems for most people this solves the issue, but for me it has not resolved it and I am unsure of where to go from here. Has anyone else experienced this and found a reason or resolution or any ideas to try? We are in the process of migrating from zenworks to SCCM.
Our working TS will image some of our Optiplex 7010’s However the newer half of 7010’s andOptiplex 7020 always fail to join the domain during the TS. After all this reading I have tried to inject the KMDF into our INstall.wim. Same issue, will not join domain.
Kernel-mode Driver Framework Version 1.11 Free Download
I am now trying to add this cab file to our boot.wim but cant get it to inject without errors. Would love some help. Have tried working with microsoft but the person helping me is clueless about this issue.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |