Error message when you run Diskpart.exe in Windows PE on a Windows Server 2003-based RIS server: "The disk management services could not complete the operation"

Consider the following scenario:

• On a Microsoft Windows Server 2003-based Remote Installation Server (RIS) server, you have Microsoft Windows Preinstallation Environment (Windows PE) installed.
• The RIS server is running on a hardware redundant array of independent disks (RAID) set that includes raw disks.
• Windows PE is based on Windows Server 2003 with Service Pack 1 (SP1).
• In Windows PE, you start the Diskpart.exe command-line tool. Then, you run the following commands, in the order in which they are listed:
  select disk 0
  clean
  create partition primary

In this scenario, Diskpart.exe may not be able to create a partition, and you may receive the following error message after about three minutes: When you quit Diskpart.exe and then repeat this scenario, you receive the same error message.

In this scenario, Windows PE starts correctly. After the problem occurs, if you restart the system in Windows PE and run Diskpart.exe again, Diskpart.exe finishes successfully.

This problem occurs because no device objects are associated with the Volsnap.sys driver when Windows PE starts from a RIS server on a system that includes raw disks. The input and output (I/O) manager tries to unload the Volsnap.sys driver, but this action is unsuccessful because of an outstanding reference to the driver object. When Diskpart.exe creates a volume, the system searches the driver list but cannot find the Volsnap.sys driver. Then, the system tries to load the Volsnap.sys driver, but this action fails because the Volsnap.sys driver is still on the loaded modules list.

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.

Prerequisites

To apply this hotfix, you must have Windows Server 2003 Service Pack 1 installed.

Note x64-based versions of Windows Server 2003 already contain the fixes and features in Windows Server 2003 SP1. You do not have to install Windows Server SP1 on x64-based versions of Windows Server 2003.

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 item in Control Panel.

Windows Server 2003 with Service Pack 1, 32-bit versions

Windows Server 2003, x64-based versions

Windows Server 2003 with Service Pack 1, Itanium-based versions

Hotfix installation instructions

To apply this hotfix, use one of the following methods.

Method 1: Use the /integrate switch to apply the hotfix to a flat folder

Create a Windows Server 2003 Service Pack 1 flat folder, and then use the /integrate switch to apply the hotfix to the flat folder. After the hotfix has been integrated, re-create the Windows PE image. Then, use the flat folder as the source.

Method 2: Manually extract the files from the hotfix package

Manually extract the files from the hotfix package, and then copy the files to the appropriate directories on the RIS server. To do this, follow these steps:

1. Download the hotfix package for the Windows PE image.
2. Extract the 910380 hotfix package to a folder by using the /x switch.
3. Copy the files from the folder to Windows PE on the RIS server.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

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