You cannot access a device with an LUN that was assigned in the current Windows Preinstallation Environment session

When you run a utility such as the Diskpart command-line utility in the Microsoft Windows Preinstallation Environment (Windows PE), you cannot access a device with a logical unit number (LUN) that was assigned in the current Windows PE session. You experience this symptom even if you use Device Console (DevCon) to scan for any newly assigned LUNs.

Notes

• This problem only occurs when you are running a version of Windows PE that was built by using Windows Server 2003 SP1.
• This problem only occurs in the current Windows PE session. After you restart the computer, you can access a device with a newly assigned LUN.
• This problem does not occur if you are using a "dumb" SCSI drive or an integrated drive electronics (IDE) drive.

The following symptoms occur even if you use an IDE drive:

• The activity light flashes on storage devices. For example, the activity light flahses on the hard disk drive or on the CD or DVD drive.
• If you eject the CD or DVD tray after you create the new LUN is created, you receive the following error message:
  There is no disk in drive. Please insert a disk into drive X:.

To resolve this problem, replace the Setupdd.sys file on the Windows PE startup disk with the version of Setupdd.sys that is included in this hotfix.

When you start the computer by using the updated Windows PE disk, you can run the Devcon rescan command to scan for any newly assigned LUNs. You can then run a utility such as the Diskpart command-line utility to configure any devices with newly assigned LUNs.

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:

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.

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, 32-bit versions

Windows Server 2003, 64-bit Itanium-based versions

Windows Server 2003, 64-bit x64-based versions

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.

The following file is available for download from the Microsoft Download Center:
Download the Devcon package now.

Technical support for x64-based versions of Microsoft Windows

Your hardware manufacturer provides technical support and assistance for x64-based versions of Windows. Your hardware manufacturer provides support because an x64-based version of Windows was included with your hardware. Your hardware manufacturer might have customized the installation of Windows with unique components. Unique components might include specific device drivers or might include optional settings to maximize the performance of the hardware. Microsoft will provide reasonable-effort assistance if you need technical help with your x64-based version of Windows. However, you might have to contact your manufacturer directly. Your manufacturer is best qualified to support the software that your manufacturer installed on the hardware.

For product information about Microsoft Windows XP Professional x64 Edition, visit the following Microsoft Web site: For product information about x64-based versions of Microsoft Windows Server 2003, visit the following Microsoft Web site: For more information, click the following article number to view the article in the Microsoft Knowledge Base: