Driver Signing Does Not Work When the Out-Of-Box Experience Process Initiates a Factory Mode Process (313208)

SYMPTOMS

During multiple Factory mode startups, some network adapter drivers may appear to be unsigned. After you run Sysprep.exe and the computer restarts, some network adapters may appear as unknown devices. During hardware detection, you may receive a warning that the driver for the network device is unsigned, and the Setupapi.log file may contain an entry that indicates that the network adapter is being removed immediately after Sysprep.exe runs. For example, you may see an entry that is similar to the following entry:

--setupapi.log---
...
[2001/10/23 16:23:14 1028.25]
#-198 Command line processed: C:\sysprep\sysprep.exe -quiet -reboot -reseal
#-166 Device install function: DIF_REMOVE.
#I289 Removing device
"PCI\VEN_8086&DEV_1031&SUBSYS_02091014&REV_41\4&1472819D&0&40F0".
#I048 Device removed.

CAUSE

The problem can occur during the second stage of the factory process where OEMAuditBoot=1 is set in the Oobeinfo.ini file. Under this condition, the Out-Of-Box Experience (OOBE) process must return to Factory mode rather than running OOBE. There is a race condition that can arise where two instances of Services.exe that are initiated by Factory.exe and Msoobe.exe can run and contend for the same resources. This can result in the Setup routine not being able to recognize the proper location of the signed network adapter drivers.

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

322389 How to Obtain the Latest Windows XP Service Pack

The English version of this fix should have the following file attributes or later:

   Date         Time   Version      Size     File name
   ------------------------------------------------------
   17-Nov-2001  14:49  5.1.3590.0   585,568  Msobmain.dll

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows XP Service Pack 1.