none
Windows XP Installation freezing at drivers installation...

    Question

  • We builded 2 Windows XP SP2 images and integrated them into SCCM 2007 (syspreped, image imported as .WIM).

     

    Those images have all corporate applications preinstalled, and all Windows updates applied. When we try with a task sequence to deploy them (both have the same problem), everything went fine until SETUPMGR install drivers (Windows XP Installation, Please wait... window, after first reboot).

     

    Even if we wait 24 hours, the PC get stuck at this point... we have to turn it off and back on to have the SETUPMGR resume the installation correctly - and at this point all drivers are installed correctly!!!

     

    We tried this task sequence onto 3 differents type of IBM computers (very old one, old and brand new), and we always get this behavior. Reboot and SETUPMGR finalize the installation correctly... very weird!!!

     

    So, the problem is probably related to our Driver's packages, BUT, when we try to disable them, we get a lot of device yellow flagged (device unknown), BUT SETUPMGR didn't freeze...

     

    What we could do or where we could look during the drivers installation process to find out WHICH one is causing us this situation (or combination), since we don't want to enable/disable every combination possible -- we have at least 1000 drivers imported into SCCM 2007.

     

    Thanks.

     

    Claude Lachapelle

    Systems Administrator, MCSE

    Monday, February 04, 2008 9:45 PM

Answers

  • This is definately related to Windows Plug and Play and Video drivers.  I have this issue today in my current SMS 2003/OSD implementation.  I have only seen this so far with Intel based on board video. 

     

    How I corrected this was to leave the drivers out of the driver set and instead packaged the drivers into an unattended install. 

    To make a much more complicated story short I have a script plugged into my process that determines the model of the PC and attempts to execute a model specific script if exists.  I basically created a custom exe using the same name as the model.

    In my Lab'd SCCM I have a Package called ModSpec.  The source directory looks something like this:

    Latitude D630\Latitude D630.exe

    Optiplex 755\Optiplex 755.exe

    etc..

     

    Then I have a Post Install phase task that executes "%Model%\%Model%.exe"  (Make sure to "continue on error" in case you dont have a model specific script for a particular model.

     

    The %Model%.exe is then used to copy the "packaged" video drivers down to the machine and insert a line into another script that will run sduring the State Restore phase to execute the video driver package.

     

    Hope this helps..There is a lot more to it obviously but hopefully this sparks some thought on how to get around it.

    Tuesday, February 05, 2008 4:50 PM
  • Problem fixed! I Finally got it to work #1... with the Intel drivers (do not use OEM drivers, in our case IBM).

     

    Now everything is running fine.

     

    Hope that will work for you too.

     

    Thanks.

     

    Claude Lachapelle

    Systems Administrator, MCSE

    Thursday, February 07, 2008 2:43 PM
  •  

    Maybe this can help you?

    http://support.microsoft.com/kb/883667/en-us

     

    Friday, March 07, 2008 9:09 AM

All replies

  • Hi Claude,

    Windows XP logs all driver installations to %windir%\setupact.log and %windir%\setuperr.log.  Hopefully there is a message in one of these logs that explains what is going wrong.  Please let us know what you find.

    Thanks,

    -- Brett

    Monday, February 04, 2008 9:59 PM
  • setuperr.log is empty.

     

    setupact.log do not contain anything meaningfull for the actual problem, everything seem to be fine, and no time are logged into this file.

     

    BUT, I find out into setupapi.log probably something that could help.. since each driver installation is logged with time, I found where the PC is rebooted the second time, because the time changed (timezone = -1 hour) and we could trace where it freeze last time:

     


    [2008/02/05 10:12:51 728.3 Driver Install]
    #-019 Searching for hardware ID(s): pci\ven_8086&dev_27d8&subsys_02f91014&rev_01,pci\ven_8086&dev_27d8&subsys_02f91014,pci\ven_8086&dev_27d8&cc_040300,pci\ven_8086&dev_27d8&cc_0403
    #-018 Searching for compatible ID(s): pci\ven_8086&dev_27d8&rev_01,pci\ven_8086&dev_27d8,pci\ven_8086&cc_040300,pci\ven_8086&cc_0403,pci\ven_8086,pci\cc_040300,pci\cc_0403
    #-198 Command line processed: C:\windows\system32\services.exe
    #I022 Found "PCI\CC_0403" in C:\drivers\7\hdaudbus.inf; Device: "Microsoft UAA Bus Driver for High Definition Audio"; Driver: "Microsoft UAA Bus Driver for High Definition Audio"; Provider: "Microsoft"; Mfg: "Microsoft"; Section name: "HDAudio_Device".
    #I087 Driver node not trusted, rank changed from 0x00002006 to 0x0000a006.
    #I023 Actual install section: [HDAudio_Device.NT]. Rank: 0x0000a006. Effective driver date: 03/05/2004.
    #-166 Device install function: DIF_SELECTBESTCOMPATDRV.
    #I063 Selected driver installs from section [HDAudio_Device] in "c:\drivers\7\hdaudbus.inf".
    #I320 Class GUID of device remains: {4D36E97D-E325-11CE-BFC1-08002BE10318}.
    #I060 Set selected driver.
    #I058 Selected best compatible driver.
    #-166 Device install function: DIF_INSTALLDEVICEFILES.
    #I124 Doing copy-only install of "PCI\VEN_8086&DEV_27D8&SUBSYS_02F91014&REV_01\3&61AAA01&0&D8".
    #-011 Installing section [HDAudio_Device.NT] from "c:\drivers\7\hdaudbus.inf".
    #E358 An unsigned or incorrectly signed file "c:\drivers\7\hdaudbus.inf" for driver "Microsoft UAA Bus Driver for High Definition Audio" blocked (server install). Error 0xe000022f: The third-party INF does not contain digital signature information.
    #E122 Device install failed. Error 0xe000022f: The third-party INF does not contain digital signature information.
    #E157 Default installer failed. Error 0xe000022f: The third-party INF does not contain digital signature information.

     

    >>>> COMPUTER REBOOTED <<<<

     

    [2008/02/05 09:13:59 1496.2]
    #-199 Executing "C:\windows\system32\rundll32.exe" with command line: rundll32.exe newdev.dll,ClientSideInstall \\.\pipe\PNP_Device_Install_Pipe_0.{EC2D90DB-D68F-4E52-81D9-61FAB154C232}
    #I060 Set selected driver.
    #-019 Searching for hardware ID(s): pci\ven_8086&dev_27d8&subsys_02f91014&rev_01,pci\ven_8086&dev_27d8&subsys_02f91014,pci\ven_8086&dev_27d8&cc_040300,pci\ven_8086&dev_27d8&cc_0403
    #-018 Searching for compatible ID(s): pci\ven_8086&dev_27d8&rev_01,pci\ven_8086&dev_27d8,pci\ven_8086&cc_040300,pci\ven_8086&cc_0403,pci\ven_8086,pci\cc_040300,pci\cc_0403
    #I022 Found "PCI\CC_0403" in C:\drivers\7\hdaudbus.inf; Device: "Microsoft UAA Bus Driver for High Definition Audio"; Driver: "Microsoft UAA Bus Driver for High Definition Audio"; Provider: "Microsoft"; Mfg: "Microsoft"; Section name: "HDAudio_Device".
    #I087 Driver node not trusted, rank changed from 0x00002006 to 0x0000a006.
    #I023 Actual install section: [HDAudio_Device.NT]. Rank: 0x0000a006. Effective driver date: 03/05/2004.
    #-166 Device install function: DIF_SELECTBESTCOMPATDRV.
    #I063 Selected driver installs from section [HDAudio_Device] in "c:\drivers\7\hdaudbus.inf".
    #I320 Class GUID of device remains: {4D36E97D-E325-11CE-BFC1-08002BE10318}.
    #I060 Set selected driver.
    #I058 Selected best compatible driver.

     

    I will try to disable this driver only and re-do a re-deployement...

     

    Thanks.

     

    Claude Lachapelle

    Systems Administrator, MCSE

    Tuesday, February 05, 2008 2:28 PM
  • On another computer, we get:

     

    [2008/02/05 10:52:37 496.598]
    #-198 Command line processed: C:\windows\system32\services.exe -setup
    #I060 Set selected driver.
    #-019 Searching for hardware ID(s): monitor\del4023
    #-018 Searching for compatible ID(s): *pnp09ff
    #I393 Modified INF cache "C:\windows\inf\INFCACHE.1".
    #I022 Found "*PNP09FF" in C:\windows\inf\monitor.inf; Device: "Plug and Play Monitor"; Driver: "Plug and Play Monitor"; Provider: "Microsoft"; Mfg: "(Standard monitor types)"; Section name: "VESADDC.Install".
    #I023 Actual install section: [VESADDC.Install]. Rank: 0x00002000. Effective driver date: 06/06/2001.
    #-166 Device install function: DIF_SELECTBESTCOMPATDRV.
    #I063 Selected driver installs from section [VESADDC.Install] in "c:\windows\inf\monitor.inf".
    #I320 Class GUID of device remains: {4D36E96E-E325-11CE-BFC1-08002BE10318}.
    #I060 Set selected driver.
    #I058 Selected best compatible driver.

     

    >>>> COMPUTER REBOOTED <<<<

     

    [2008/02/05 10:56:55 684.3 Driver Install]
    #-019 Searching for hardware ID(s): monitor\del4023
    #-018 Searching for compatible ID(s): *pnp09ff
    #-198 Command line processed: C:\windows\system32\services.exe -setup
    #I022 Found "*PNP09FF" in C:\windows\inf\monitor.inf; Device: "Plug and Play Monitor"; Driver: "Plug and Play Monitor"; Provider: "Microsoft"; Mfg: "(Standard monitor types)"; Section name: "VESADDC.Install".
    #I023 Actual install section: [VESADDC.Install]. Rank: 0x00002000. Effective driver date: 06/06/2001.
    #-166 Device install function: DIF_SELECTBESTCOMPATDRV.
    #I063 Selected driver installs from section [VESADDC.Install] in "c:\windows\inf\monitor.inf".
    #I320 Class GUID of device remains: {4D36E96E-E325-11CE-BFC1-08002BE10318}.
    #I060 Set selected driver.
    #I058 Selected best compatible driver.
    #-166 Device install function: DIF_INSTALLDEVICEFILES.
    #I124 Doing copy-only install of "DISPLAY\DEL4023\4&33EBE6EA&0&80861100&00&02".
    #-166 Device install function: DIF_REGISTER_COINSTALLERS.
    #I056 Coinstallers registered.
    #-166 Device install function: DIF_INSTALLINTERFACES.
    #-011 Installing section [VESADDC.Install.Interfaces] from "c:\windows\inf\monitor.inf".
    #I054 Interfaces installed.
    #-166 Device install function: DIF_INSTALLDEVICE.
    #I123 Doing full install of "DISPLAY\DEL4023\4&33EBE6EA&0&80861100&00&02".
    #I121 Device install of "DISPLAY\DEL4023\4&33EBE6EA&0&80861100&00&02" finished successfully.

     

    It seem that is not always related to the same drivers...

     

    Still searching...

     

    Claude Lachapelle

    Systems Administrator, MCSE

    Tuesday, February 05, 2008 3:22 PM
  • This is definately related to Windows Plug and Play and Video drivers.  I have this issue today in my current SMS 2003/OSD implementation.  I have only seen this so far with Intel based on board video. 

     

    How I corrected this was to leave the drivers out of the driver set and instead packaged the drivers into an unattended install. 

    To make a much more complicated story short I have a script plugged into my process that determines the model of the PC and attempts to execute a model specific script if exists.  I basically created a custom exe using the same name as the model.

    In my Lab'd SCCM I have a Package called ModSpec.  The source directory looks something like this:

    Latitude D630\Latitude D630.exe

    Optiplex 755\Optiplex 755.exe

    etc..

     

    Then I have a Post Install phase task that executes "%Model%\%Model%.exe"  (Make sure to "continue on error" in case you dont have a model specific script for a particular model.

     

    The %Model%.exe is then used to copy the "packaged" video drivers down to the machine and insert a line into another script that will run sduring the State Restore phase to execute the video driver package.

     

    Hope this helps..There is a lot more to it obviously but hopefully this sparks some thought on how to get around it.

    Tuesday, February 05, 2008 4:50 PM
  • Another computer (third one):

     

    [2008/02/05 12:40:10 496.598]
    #-198 Command line processed: C:\windows\system32\services.exe -setup
    #I060 Set selected driver.
    #-019 Searching for hardware ID(s): monitor\del4023
    #-018 Searching for compatible ID(s): *pnp09ff
    #I393 Modified INF cache "C:\windows\inf\INFCACHE.1".
    #I022 Found "*PNP09FF" in C:\windows\inf\monitor.inf; Device: "Plug and Play Monitor"; Driver: "Plug and Play Monitor"; Provider: "Microsoft"; Mfg: "(Standard monitor types)"; Section name: "VESADDC.Install".
    #I023 Actual install section: [VESADDC.Install]. Rank: 0x00002000. Effective driver date: 06/06/2001.
    #-166 Device install function: DIF_SELECTBESTCOMPATDRV.
    #I063 Selected driver installs from section [VESADDC.Install] in "c:\windows\inf\monitor.inf".
    #I320 Class GUID of device remains: {4D36E96E-E325-11CE-BFC1-08002BE10318}.
    #I060 Set selected driver.
    #I058 Selected best compatible driver.

     

    >>>> COMPUTER REBOOTED <<<<

     

    [2008/02/05 14:33:45 684.3 Driver Install]
    #-019 Searching for hardware ID(s): monitor\del4023
    #-018 Searching for compatible ID(s): *pnp09ff
    #-198 Command line processed: C:\windows\system32\services.exe -setup
    #I022 Found "*PNP09FF" in C:\windows\inf\monitor.inf; Device: "Plug and Play Monitor"; Driver: "Plug and Play Monitor"; Provider: "Microsoft"; Mfg: "(Standard monitor types)"; Section name: "VESADDC.Install".
    #I023 Actual install section: [VESADDC.Install]. Rank: 0x00002000. Effective driver date: 06/06/2001.
    #-166 Device install function: DIF_SELECTBESTCOMPATDRV.
    #I063 Selected driver installs from section [VESADDC.Install] in "c:\windows\inf\monitor.inf".
    #I320 Class GUID of device remains: {4D36E96E-E325-11CE-BFC1-08002BE10318}.
    #I060 Set selected driver.
    #I058 Selected best compatible driver.
    #-166 Device install function: DIF_INSTALLDEVICEFILES.
    #I124 Doing copy-only install of "DISPLAY\DEL4023\4&33EBE6EA&0&80861100&00&02".
    #-166 Device install function: DIF_REGISTER_COINSTALLERS.
    #I056 Coinstallers registered.
    #-166 Device install function: DIF_INSTALLINTERFACES.
    #-011 Installing section [VESADDC.Install.Interfaces] from "c:\windows\inf\monitor.inf".
    #I054 Interfaces installed.
    #-166 Device install function: DIF_INSTALLDEVICE.
    #I123 Doing full install of "DISPLAY\DEL4023\4&33EBE6EA&0&80861100&00&02".
    #I121 Device install of "DISPLAY\DEL4023\4&33EBE6EA&0&80861100&00&02" finished successfully.

     

    All those computers have Intel onboard video cards... and we have EXACTLY the same problem with the other Windows XP image which is in French... incredible but true.

     

    We will have to find out a solution! This is not acceptable...

     

    Thanks.

     

    Claude Lachapelle

    Systems Administrator, MCSE

    Tuesday, February 05, 2008 6:54 PM
  • Did you see my post above? 

    Tuesday, February 05, 2008 7:42 PM
  • Yes, and this is the same issue... thanks for the proposed workaround, I'm currently working on a permanent solution (like finding a working video driver).

     

    I marked your post as the answer... thanks again.

     

    Claude Lachapelle

    Systems Administrator, MCSE

    Tuesday, February 05, 2008 7:53 PM
  •  

    Thanks,

    If you find another workaround please be sure to post back here.  I would love to hear it!

    Tuesday, February 05, 2008 8:35 PM
  • Problem fixed! I Finally got it to work #1... with the Intel drivers (do not use OEM drivers, in our case IBM).

     

    Now everything is running fine.

     

    Hope that will work for you too.

     

    Thanks.

     

    Claude Lachapelle

    Systems Administrator, MCSE

    Thursday, February 07, 2008 2:43 PM
  • Oups... this is not working FOR ALL computers... but at least we got it to work for some with the Intel drivers. For the others, we will instruct people to hard reboot PCs when they are freezing...

     

    Claude Lachapelle

    Systems Administrator, MCSE

    Thursday, February 07, 2008 3:13 PM
  •  

    Maybe this can help you?

    http://support.microsoft.com/kb/883667/en-us

     

    Friday, March 07, 2008 9:09 AM
  • Thanks, this is probably the permanent solution! Beautiful!

     

    Claude Lachapelle

    Systems Administrator, MCSE

     

    Friday, March 07, 2008 3:11 PM