Article ID: 838457
Article Last Modified on 7/24/2007
APPLIES TO
- Microsoft Windows Server 2003, Web Edition
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise x64 Edition
SYMPTOMS
When you run the Microsoft Windows Server 2003 Setup program after you copy an image to a new destination computer, you may receive a Stop 0x7B error.
CAUSE
This problem may occur after the mass storage drivers are updated to newer versions on an image that was created by using the System Preparation tool (Sysprep) -pnp switch. The mass storage drivers are located in the OemDriversPath as specified in the Sysprep.inf file.
The problem occurs because the -pnp switch only updates a temporary branch in the registry that Sysprep creates to mimic the devices that are installed. The -pnp switch does not update the actual devices in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI registry subkey. For example, when the –pnp switch is used with Sysprep, the LowerFilter registry entry that is associated with the older driver is not removed. Therefore, when you run the Setup program after you copy the image to the new destination computer, the Setup program tries to load the drivers that are defined in the LowerFilter registry entry, although the new drivers do not support this functionality. Therefore, you receive a Stop 0x7B error.
RESOLUTION
Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:
Prerequisites
No prerequisites are required.
Restart requirement
You must apply this hotfix before you run Sysprep. You must restart your computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
File information
The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Windows Server 2003, 32-bit editions
Date Time Version Size File name -------------------------------------------------------------- 13-Apr-2004 17:35 5.2.3790.162 1,012,736 Syssetup.dll
Windows Server 2003, 64-Bit Enterprise Edition
Date Time Version Size File name -------------------------------------------------------------- 13-Apr-2004 17:26 5.2.3790.162 1,835,520 Syssetup.dll
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Keywords: kbbug kbfix kbwinserv2003presp1fix kbqfe kbhotfixserver KB838457
