Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Setup may stop responding during a RIS installation at the "Preparing Network Settings" page


View products that this article applies to.

Symptoms

During a Remote Installation Services (RIS) installation operation, Setup may stop responding at the Preparing Network Settings page.

↑ Back to the top


Cause

This problem may occur if the following conditions are true:
  • You use the Microsoft Windows Preinstallation Environment (Windows PE).
  • You use the CENATEK RAMDisk tool.
In this scenario, the network adapter may remain active when the computer starts Windows PE. When the Plug and Play (PnP) manager tries to assign the interrupt request level (IRQL) resource to the network adapter, the adapter generates an unexpected interrupt.

↑ Back to the top


Resolution

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
889100 How to obtain the latest service pack for 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.After you download the hotfix described here, follow these steps to resolve this problem:
  1. Double-click the hotfix file to extract the Setupldr.exe file.
  2. Save the file to a familiar location or to a temporary folder.
  3. Locate and right-click the Ntldr file in the \REMINST\Setup\Lang\Images\ImageName\i386\templates folder.
  4. Rename the Ntldr file to ntldr.old.
  5. Copy the Setupldr.exe file to the \REMINST\Setup\Lang\Images\ImageName\i386\templatesfolder.
  6. Right-click Setupldr.exe, click Rename, type ntldr, and then click OK.

Prerequisites

No prerequisites are required.

Restart requirement

You do not have to 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 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, 64-bit versions
File nameFile versionFile sizeDateTimePlatform
Setupldr.efi5.2.3790.2667904,70424-Mar-200602:44Not applicable
Windows Server 2003, 32-bit versions
File nameFile versionFile sizeDateTimePlatform
Setupldr.exe5.2.3790.2667279,04024-Mar-200602:43x86

↑ Back to the top


Status

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 Windows Server 2003 Service Pack 2.

↑ Back to the top


More information

For more 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

↑ Back to the top


Keywords: kbautohotfix, kbwinserv2003sp2fix, kbqfe, kbHotfixServer, kbwinserv2003presp2fix, kbbug, kbfix, KB916710

↑ Back to the top

Article Info
Article ID : 916710
Revision : 3
Created on : 10/9/2011
Published on : 10/9/2011
Exists online : False
Views : 415