Sysprep does not update the DevicePath value in the registry with information from OemPnpDriversPath in Windows XP Professional (894570)

The information in this article applies to:

Microsoft Windows XP Professional

SYMPTOMS

If you use the Sysprep tool to prepare a computer in Factory mode and you specify a path in the Sysprep.ini file for the OemPnpDriversPath value, and then you change the location of drivers and update the OemPnpDriversPath value in the Sysprep.inf file, your changes are not applied to the DevicePath value in the following registry subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion

CAUSE

This problem occurs because the Sysprep tool does not append to the DevicePath value in the following registry subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion

RESOLUTION

To resolve this problem, delete the DevicePath value from the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion registry subkey. You should do this after you make the changes to the OemPnpDriversPath value in the Sysprep.inf file and before you run the sysprep -reseal command.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

Steps to reproduce the behavior

Run Sysprep on your computer, and then use the OemPnpDriversPath value to specify the location of drivers that have the Sysprep.inf file.
Verify that the DevicePath value of the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion registry subkey is correctly set after the Mini-Setup Wizard runs.
Change the location that is referenced in the OemPnpDriversPath value that is specified in the Sysprep.inf file.
Run Sysprep again.
Examine the DevicePath value of the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion registry subkey. After the Mini-Setup Wizard runs, you will notice that the change was not applied.

Modification Type:	Major	Last Reviewed:	3/10/2005
Keywords:	kbtshoot kbsetup kbprb KB894570 kbAudDeveloper