KACE Product Support Question

K2000 and the new E7440 Ultrabook

10/24/2013 4474 views

Has anyone had any luck successfully deploying a scripted installation to this new model? 

Like all new systems, I downloaded the drivers from the driver feed and recached the drivers. Then rebuilt the KBE. Hooked the computer up and booted it to the network. To my surprise, it would not load the KBE. From some help here on ITninja, I was able to figure out that the network drivers were not properly downloaded into the KBE folder on the K2000. I went to Dell's website and downloaded the WINPE 4.0 drivers and manually inserted them into the KBE folders.

Now the computer boots into the KBE and will load the scripted installation....

My final problem that I'm running into is that once windows gets installed and the system starts the post install tasks, Windows wants to reboot due to system changes... and when it reboots, it interupts installation tasks. 

I am using PO Converter and I've tried to put in a Reboot task but the Windows Reboot prompt still pops up? The E7440 computer is the only system that is having this issue so I'm thinking that something isn't loading correctly with the drivers. 

Has anyone else ran into this yet? Have you been able to fix it?

Answer Summary:
2 Comments   [ + ] Show comments


  • Any luck? I'm having the same issues.
  • Actually yes see my answer below.

Community Chosen Answer


For anyone wondering what the E7420/E7440 issue / fix for this is, here ya go.

The issue arises from the new intel drivers requiring a hot-fix from microsoft. 

"Some of the Windows 7 drivers for the new Dell systems may require an update of the KMDF to version 1.11.  The KMDF is a component of the OS and the update is available from Microsoft at the link below.  The usual treatment is to include the KMDF update into your base image until it is rolled up into a service pack.  Some of you may remember seeing this issue with XP/Vista when Win7 came on the scene.


Symptoms that a KMDF update is needed for a Windows 7 driver:

 1.       Yellow bang in device manager for components that you know you have a driver available

2.       Black screen during OS deployment



So how do you fix this issue? 

First, if you are using the driver feed for either the E7440 or E7420, you will need to connect to your driver share and remove them manually.

- Browse to \\kbox$\drivers_postinstall\dell\windows_7_x64\e7440
- Under chipset, delete the folder called '88VH0_A00-00 A00" (Intel Management Engine)
- Also delete the folder "
08V18_A00-00 A01" (ST Micro Sensor)

Both of these drivers are causing Windows to reboot after deploying the OS when using a scripted installation.
*Note - You do not need to recache your drivers.

Now that you have the drivers removed, the deployment will work fine except those drivers are still missing and need to be installed. For this, we are going to create a post install task for the drivers. Coincidentally, we have noticed that the system DOES NOT require a reboot when installed in this manner. :)

- Goto  http://www.dell.com/support/drivers/us/en/19/driverdetails?driverid=FWRCW and download the exe installer for the Intel driver.
-  Using a zip utility, extract the exe to a folder and rezip it.
- Create a Post install task uploading the zip file and use the following as the command:
start /wait setup.exe -preinst -drvonly -overwrite -s 
What this will do, is install ONLY the drivers silently bypassing any errors by overwriting automatically and installing even if the hardware is not present. **So if you have other models that you are scripting as well, you won't need to keep modifying the deployment.

I put this task towards the end of my deployment and haven't seen any further issues.

For the ST sensor, just do the same thing. We do not include it since our devices are SSD drives and the fall sensor provides no benefit. The system works perfectly fine without the driver installed. 

Kace Tier 3 Support is aware of this issue and will be removing these 2 drivers from the Driver Feed for the E7420 and E7440 models until a permanent solution can be found. 

Answered 11/12/2013 by: RealityHook
Orange Senior Belt

All Answers


Are you imaging this with a dongle?  If so is the dongle drivers in the scripted install also.  If the nic drivers do not load post script then the machine cannot see the k2000 to reattach for post commands.

Answered 10/24/2013 by: SMal.tmcc
Red Belt

  • The nic drivers work find I believe. I had to download the winpe 4.0 drivers from dell. But after that, the computer was able to boot to the kbe and load the post tasks.

    The issue again is that something is causing windows to reboot once the imaging hits the post install stage of deployment. Since this reboot is caused by windows and not part of the po converter, it wrecks the install process and won't recover.

    I'm not sure what is causing this reboot to occur nor know how to remove the drivers that I uploaded. There were a few that were put in the generic kbe folder.
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ