ConfigMgr 2007: Dell Latitude E6400 laptop hangs during Windows XP Mini-Setup

Here's an interesting issue that our very own Frank Rojas ran into recently concerning OSD on a Dell Latitude laptop.  I don't think this issue is necessarily isolated to this particular machine but the troubleshooting process would likely be the same.  Hopefully this will help you out if you run into something similar:


Issue: When deploying a Windows XP image to a Dell Latitude E6400 laptop using an SCCM 2007 OSD Task Sequence, the deployment will deploy the image properly, however when the laptop boots into Windows XP Mini-Setup, Mini-Setup eventually freezes and does not proceed.

The SMSTS.log will not show any errors indicating what the problem is. Inspecting the setupapi.log taken from the laptop client PC will show the following lines as the last lines in the log:

#-019 Searching for hardware ID(s): acpipnp0c0a,*pnp0c0a
#-198 Command line processed: C:Windowssystem32services.exe -setup
#I022 Found "ACPIpnp0C0A" in C:Windowsinfbattery.inf; Device: "Microsoft ACPI-Compliant Control Method Battery"; Driver: "Microsoft ACPI-Compliant Control Method Battery"; Provider: "Microsoft"; Mfg: "Microsoft"; Section name: "CmBatt_Inst".
#I023 Actual install section: [CmBatt_Inst]. Rank: 0x00000000. Effective driver date: 07/01/2001.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [CmBatt_Inst] in "c:Windowsinfbattery.inf".
#I320 Class GUID of device remains: {72631E54-78A4-11D0-BCF7-00AA00B7B32A}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#I124 Doing copy-only install of "ACPIPNP0C0A1".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [CmBatt_Inst.Interfaces] from "c:Windowsinfbattery.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "ACPIPNP0C0A1".
#I121 Device install of "ACPIPNP0C0A1" finished successfully.

The problem may also happen when trying to deploy a Windows XP image using other deployment technologies, including Microsoft Business Desktop Deployment (BDD).

Cause: It appears that when Windows XP tries to load the battery drivers for the Dell Latitude E6400 laptop using the battery.inf file from the C:WindowsINF folder, the installation hangs. It is possible that the included battery.inf file of Windows XP is not fully compatible with the battery in the Dell Latitude E6400 laptop.

PLEASE NOTE: It appears that Dell has released a BIOS update that resolves this problem. Updating the BIOS to the latest version will probably resolve the issue, making it unnecessary to follow the below steps.  Please visit Dell's website for more information.

Resolution: There are a few workarounds to the problem:

1) Remove the battery from the laptop during deployment. Doing so will prevent Windows XP Mini-Setup from trying to detect the battery, therefore Mini-Setup will not hang. This solution, however, is not the most ideal.

2) Build the reference image on a Dell Latitude E6400 laptop. By building the reference image on a Dell Latitude E6400 laptop, the battery.inf driver installation no longer causes Windows XP Mini-Setup to hang. However, this solution seems to work only in some situations. In testing,  the reference image built on the laptop fixed the Windows XP Mini-Setup hang issues while installing battery.inf and it also worked on most other model PCs but it did fail on some others. Results may vary depending on your environment and what make/model PCs you have.

3) If using a Task Sequence in either SCCM 2007 OSD, BDD, or MDT to deploy the Windows XP image, you can add tasks into the Task Sequence which forces the battery to be installed while in Windows XP instead of during Windows XP Mini-Setup. The installation of the battery drivers seems to succeed while in Windows XP and only seems to fail while in Windows XP Mini-Setup:

a) Add a "Run Command Line" task that renames the battery.inf in the WindowsINF folder at some point in the Task Sequence while it is still in WinPE, but after it has dropped down the Windows XP WIM image using the "Apply Operating System Image" (SCCM 2007) or "Install Operating System" (BDD/MDT) tasks. For example, the command line for the "Run Command Line" should be:

rename %DeploySystemDrive%WindowsINFbattery.inf battery.inf.tmp

b) Add a "Run Command Line" task at some point in the Task Sequence after it has completed Windows XP Mini-Setup and while it is in Windows XP that renames the file back to battery.inf. The command line for the "Run Command Line" should be:

rename %windir%INFbattery.inf.tmp battery.inf

c) Download the Microsoft DEVCON.exe utility as documented in KB311272 from:

This utility allows the installation of devices from the command line by using the command line:

devcon install INFfile HardwareID

d) In SCCM/MDT/BDD, create a Package/Application that contains the DEVCON.exe program file. For MDT/BDD, set the command line as

copy devcon.exe %windir%system32 /Y

For SCCM 2007, after creating the package, create a program with the command line

copy devcon.exe %windir%system32 /Y

e) Add an "Install Software" task (SCCM 2007) or an "Install Application" (MDT/BDD) task immediately after the "Run Command Line" task from step b that runs the package/program created in step d.

f) Add a "Run Command Line" task in the Task Sequence immediately after the "Install Software"/"Install Application" task from step e which initiates the installation of the battery drivers using devcon.exe while in Windows XP.  For example, to install the battery on the Dell Latitude E6400 laptop, set the command line to:

devcon install "%windir%infbattery.inf" ACPIPNP0C0A1

Once you do this you should be good to go.


Thanks Frank!

J.C. Hornbeck | Manageability Knowledge Engineer

Comments (3)
  1. Anonymous says:

    ConfigMgr 2007: Dell Latitude E6400 laptop hangs during Windows XP Mini-Setup Feed: The Configuration

  2. Anonymous says:

      Here's an interesting issue that our very own Frank Rojas ran into recently concerning OSD

  3. Anonymous says:

    Just an FYI that I posted a note about an OSD related issue we’ve seen when deploying to a certain Dell

Comments are closed.

Skip to main content