Knowledge Base

You may receive a "Windows could not start due to an error while booting the RAMDISK" error when you try to start a Windows Server 2003-based computer into the Deployment Agent

Article ID: 899343

Article Last Modified on 3/28/2007

APPLIES TO

Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
Microsoft Windows Server 2003, Standard Edition (32-bit x86)
Microsoft Windows Server 2003, Web Edition

SYMPTOMS

You try to start a Microsoft Windows Server 2003-based computer into the Deployment Agent by using the Windows Server 2003 Automated Deployment Services (ADS). In this scenario, you may receive the following error message on the destination computer:

Windows could not start due to an error while booting the RAMDISK. Windows failed to build a bootable RAMDISK image. System will reboot in 5 seconds

CAUSE

This problem may occur if the computer is using more than 32 PCI devices.

RESOLUTION

To resolve this problem, install this hotfix on the ADS server that is running the Deployment Agent Builder service.

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

Prerequisites

Windows Server 2003 Service Pack 1 (SP1)

Restart requirement

You must 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 tool in Control Panel.

   Date         Time   Version            Size    File name
   --------------------------------------------------------------
   12-May-2005  03:23  5.2.3790.2443     325,120  Osloader.ntd

Hotfix installation instructions

To install the hotfix, follow these steps:

Double-click the hotfix installer package.

The Osloader.ntd file is extracted to a temporary folder in the root folder of %systemdrive%. For example, the Osloader.ntd file is extracted to a folder location that is similar to the following:

c:\7d3c7dedd1efd4be3c41b1b4a180\Osloader.ntd

Note The name of the temporary folder may vary.
In Windows Explorer, locate the following folder:

%systemdrive%\Program Files\Microsoft ADS\tftproot\nbs\boot\x86

Note The %systemdrive% environmental variable specifies the drive letter of the drive that contains Windows. By default, this is drive C.
In the x86 folder, rename the Ntldr file to Ntldrold.
Copy the Osloader.ntd file from the temporary folder to the %systemdrive%\Program Files\Microsoft ADS\tftproot\nbs\boot\x86 folder.
Rename the Osloader.ntd file to Ntldr.
Restart the ADS services.

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.

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

Keywords: kbwinserv2003sp2fix kberrmsg kbqfe kbhotfixserver KB899343

Microsoft KB Archive/899343

Contents