[UNRESOLVED-CLOSED] How to Update Drivers in an Image After Sysprep? RRS feed

  • Question

  • We recently received new hardware a few months shy of our Windows 7 upgrade from Windows XP SP3.  This new hardware is different enough that our existing WinPE/BartPE boot CD's wouldn't work which required us to create new CD's with updated drivers.  (This is not a big deal and isn't the source of our problem.)

    The problem though is this:
    Even though we can image (ghost) the new machines with our Windows XP SP3 image, the image itself still needs to be updated with the drivers.  As it stands, after imaging, Windows attempts to boot up and bluescreens.  Presumably this happens because it lacks the storage controller drivers.

    How can I manually update drivers of an already sysprepped image?

    Can I drop the INF's and SYS files in some folder that Windows will recognize & pull drivers from?

    What recourse do I have?

    • Edited by JuliusPIV Thursday, March 31, 2011 3:18 PM
    Thursday, January 20, 2011 2:59 PM

All replies

  • The easy fix would be to try setting them to compability mode in BIOS, if this is a temporary solution.

    The other option is to add the new SATA storage drivers to the image, and then insert the new hardware ID:s to sysprep.inf
    See Johans guide: http://www.deployvista.com/Blog/tabid/70/EntryID/18/Default.aspx


    Thursday, January 20, 2011 4:00 PM
  • Thanks for the response

    I gave it a look over and tried my hand at it this morning without much luck.  I assume I'm doing something wrong but I'm not certain.  I had another engineer, one with far more experience than I, take a look at the site and his initial response was that it might be for a RIS install, which is slightly different than what we're doing.

    Unless someone has better suggestions, I only see 3 options at this point:

    1. Reverse-engineer the way sysprep currently does it.  Look for a device ID of a driver we have and see what exactly the sysprep process does to it. (Although, what worries me is that if it was easy, there wouldn't be a convoluted way in sysprep to manuall add mass storage drivers.)
    2. Stand up another vanilla Win XP machine, add the drivers to it then run 'sysprep -factory' & see if I can update our existing image with the files sysprep produces.
    3. Start from scratch.

    Again, many thanks.

    Friday, January 21, 2011 2:32 PM
  • Did you tried to update the drivers manualy after sysprem from computer managment??? All of the drivers can be  manualy updated from this console to the lastest updates.
    Thursday, March 17, 2011 1:03 PM
  • Good afternoon Vladimir and thanks for the reply.

    Unfortunately once these machines are ghosted (meaning the image has been 'downloaded' onto the harddrive) the system boots up and immediately bluescreens.  There's no way to get into Windows to update any drivers.

    My guess is that there's no way to do this and since its now a moot point, this thread can be closed.

    Thursday, March 31, 2011 3:18 PM