Introduction

Have you seen this error when trying to deploy a new machine model? It’s related to Kernel Mode Driver Framework 1.11 and KB 2685811.

“Windows could not configure one or more system components. To install Windows, restart the computer and then restart the installation.”

kb 2685811

In this blog post, I cover what the Kernel-Mode Driver Framework is, how to download version 1.11, and how to add it to your image.

What is the Microsoft Kernel-Mode Driver Framework?

The Kernel-Mode Driver Framework is a driver framework that Microsoft provides to developers for them to create and update kernel-mode drivers. It is one framework provided in the Windows Driver Frameworks.

This driver framework is provided for Microsoft Windows 2000 and later operating systems.

As of this writing (18th of December 2019), the latest version is 1.27.

Download Microsoft Kernel-Mode Framework 1.11 (KB 2685811)

The error described in the introduction is most likely because the base image is not updated with the latest Kernel Mode Driver Framework, with a version of 1.11 at the time of this writing.

You can download the KB2685811 separately here:
http://support.microsoft.com/kb/2685811

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.

How to add Microsoft Kernel-Mode Framework 1.11 (KB 2685811) to your image

As far as I know, there are three different solutions to this issue:

1. Update the base image with the hotfix.
2. Install the newest updates on the base image. The hotfix is included in the Windows Update patches.
3. Inject the hotfix offline. I have not tried this myself, but here is a blog post on how to do it:
http://deploymentramblings.wordpress.com/2013/10/24/osd-injecting-the-windows-7-kernel-mode-driver-framework-kmdf/

Related posts

3 COMMENTS

  1. Dear
    I am facing the kernel mode 1.11 problem.Can you plese guide me
    how to Update the base image with the hotfix.
    SCCM 2007 R3
    step by step

  2. 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. It’s a pain! 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

    • Hi Markus,

      Offline servicing of patches is however not something I would recommend as there are some issues, i.e getting corrup WIMs. My recommendation would always be to rebuild your image with MDT 🙂

LEAVE A REPLY

Please enter your comment!
Please enter your name here