You Cannot Use the Same WinPE Image for Both Uniprocessor and Multiprocessor-Based Computers

You may not be able to use a single WinPE image to deploy the Windows Preinstallation Environment (WinPE) to uniprocessor and multiprocessor-based computers from a Remote Installation Services (RIS) server. You may have to create separate WinPE images.

This problem occurs because WinPE cannot detect the multiprocessor platform. As a result, you cannot use the same WinPE image for both uniprocessor and multiprocessor-based computers. You must use separate images.

Windows XP

Service pack information

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

Hotfix information

Prerequisites

No prerequisites are required.

Restart requirement

You do not have to restart the 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 file attributes) 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 item in Control Panel.

Windows Server 2003

Hotfix information

A supported hotfix is 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 software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

No prerequisites are required.

Restart requirement

You do not restart the 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 file attributes) 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 item in Control Panel.

To install this hotfix when the path of your WinPE image on the RIS server is \\RISServer1\Reminst\Setup\English\Images\WinPEx86Boot\I386, follow these steps:

1. Extract the hotfix to a temporary location, and then copy the Extra.inf file to the I386 folder.
2. Copy the KB814199.CAT file to the I386 folder.
3. Copy the Setupldr.bin file to the I386 folder.
4. Copy the IP\Layout.inf file to the I386\inf folder.
5. Copy the Setupldr.exe file to the I386\templates folder, and then rename it ntldr. Back up the existing Ntldr file.
6. Copy the I386\ntoskrnl.exe file to the I386\system32 folder.
7. Copy the I386\ntkrnlmp.exe file to the I386\system32 folder.
8. At a command prompt, type the following commands, and then press ENTER:
   Net stop binlsvc
   Net start binlsvc

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft Windows XP Service Pack 2.