This has probably been asked and answered before, but I am having a terrible time trying to put the info all together coherantly.

It has come time to update our Windows KBE's to include drivers for non-Dell supported systems. I understand the process to make new KBE's, but I would like to include the 150+ Windows 7 patches and hot fixes to reduce the amount of time we spend updating a system once we have completed a scripted install. My question is how do I get the Windows updates into the boot environment that makes the KBE? Is there a step-by-step tutorial somewhere?


0 Comments   [ - ] Hide Comments


  • This content is currently hidden from public view.
    Reason: Removed by member request
    For more information, visit our FAQ's.
Please log in to comment

Community Chosen Answer



You can use a tool like RT7Lite to slip patches into a custom source media that would get uploaded and used for Scripted Installs.  This way when you deploy the SI it is up to date!

Answered 07/09/2013 by: andrew_lubchansky
Black Belt

  • Using RT7Lite in conjunction with WindowsUpdatesDownloader is a great way to deploy Scripted Installations with customized, updated Microsoft patches. I wrote a short tutorial on how this is accomplished here: http://blog.kace.com/2013/04/23/k2000-kloser-look-going-offline-for-patching/
Please log in to comment
Answer this question or Comment on this question for clarity



That really doesn't have anything to do with the KBE, only the drivers are relevant to that.  The issue you're facing is exactly why we don't use scripted installs, but rather WIM images that get updated frequently.

Answered 07/09/2013 by: nheyne
Red Belt

  • I agree switch to WIM's, update the master every few weeks (i do mine at least monthly). I have cast 1000's of wim's during the life of my kbox, but only have 29 scripted installs. I sysprep and have all my drivers in the master WIM. The only thing they do after imaging is set the name, description and install AV.
Please log in to comment

It is possible to capture an existing OS to WIM using imagex, then use the updated WIM to replace the install.wim on the install media, recreate the catalog and use that as the basis for your scripted install:


Answered 07/09/2013 by: tshupp
Second Degree Black Belt

Please log in to comment