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" (910380)
The information in this article applies to:
- Microsoft Windows Server 2003 SP1
SYMPTOMSConsider 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: The disk management services could not complete
the operation. 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. CAUSEThis 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.RESOLUTIONHotfix informationA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Windows Server 2003 service pack that contains this hotfix. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. PrerequisitesTo 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 requirementYou must restart the computer after you apply this hotfix. Hotfix replacement informationThis 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 |
| Eventcls.dll | 5.2.3790.2564 | 31,232 | 07-Nov-2005 | 17:15 | x86 | SP1 | | Ftdisk.sys | 5.2.3790.2564 | 137,216 | 05-Nov-2005 | 01:52 | x86 | SP1 | | Partmgr.sys | 5.2.3790.2564 | 25,088 | 05-Nov-2005 | 02:16 | x86 | SP1 | | Swprv.dll | 5.2.3790.2564 | 275,968 | 07-Nov-2005 | 17:15 | x86 | SP1 | | Volsnap.sys | 5.2.3790.2564 | 153,088 | 05-Nov-2005 | 01:52 | x86 | SP1 | | Vssadmin.exe | 5.2.3790.2564 | 133,632 | 05-Nov-2005 | 01:52 | x86 | SP1 | | Vssapi.dll | 5.2.3790.2564 | 561,152 | 07-Nov-2005 | 17:15 | x86 | SP1 | | Vssui.dll | 5.2.3790.2564 | 144,384 | 07-Nov-2005 | 17:15 | x86 | SP1 | | Vssvc.exe | 5.2.3790.2564 | 835,584 | 05-Nov-2005 | 01:52 | x86 | SP1 | | Vss_ps.dll | 5.2.3790.2564 | 19,456 | 07-Nov-2005 | 17:15 | x86 | SP1 |
Windows Server 2003, x64-based versions |
| Eventcls.dll | 5.2.3790.2564 | 46,080 | 07-Nov-2005 | 01:46 | x64 | SP1 | Not
Applicable | | Ftdisk.sys | 5.2.3790.2564 | 240,128 | 07-Nov-2005 | 01:46 | x64 | SP1 | Not
Applicable | | Partmgr.sys | 5.2.3790.2564 | 45,056 | 07-Nov-2005 | 01:46 | x64 | SP1 | Not
Applicable | | Volsnap.sys | 5.2.3790.2564 | 288,768 | 07-Nov-2005 | 01:46 | x64 | SP1 | Not
Applicable | | Vssui.dll | 5.2.3790.2564 | 233,472 | 07-Nov-2005 | 01:46 | x64 | SP1 | Not
Applicable | | Vss_ps.dll | 5.2.3790.2564 | 25,600 | 07-Nov-2005 | 01:46 | x64 | SP1 | Not
Applicable | | Swprv.dll | 5.2.3790.2564 | 653,824 | 07-Nov-2005 | 01:46 | x64 | SP1 | Not
Applicable | | Vssadmin.exe | 5.2.3790.2564 | 245,248 | 07-Nov-2005 | 01:46 | x64 | SP1 | Not
Applicable | | Vssapi.dll | 5.2.3790.2564 | 1,320,448 | 07-Nov-2005 | 01:46 | x64 | SP1 | Not
Applicable | | Vssvc.exe | 5.2.3790.2564 | 2,061,312 | 07-Nov-2005 | 01:46 | x64 | SP1 | Not
Applicable | | Wvssapi.dll | 5.2.3790.2564 | 561,152 | 07-Nov-2005 | 01:46 | x86 | SP1 | WOW | | Wvss_ps.dll | 5.2.3790.2564 | 19,456 | 07-Nov-2005 | 01:46 | x86 | SP1 | WOW |
Windows Server 2003 with Service Pack 1, Itanium-based versions |
| Eventcls.dll | 5.2.3790.2564 | 82,432 | 07-Nov-2005 | 01:45 | IA-64 | SP1 | Not
Applicable | | Ftdisk.sys | 5.2.3790.2564 | 498,688 | 07-Nov-2005 | 01:45 | IA-64 | SP1 | Not
Applicable | | Partmgr.sys | 5.2.3790.2564 | 83,456 | 07-Nov-2005 | 01:45 | IA-64 | SP1 | Not
Applicable | | Volsnap.sys | 5.2.3790.2564 | 476,160 | 07-Nov-2005 | 01:45 | IA-64 | SP1 | Not
Applicable | | Vssui.dll | 5.2.3790.2564 | 408,064 | 07-Nov-2005 | 01:45 | IA-64 | SP1 | Not
Applicable | | Vss_ps.dll | 5.2.3790.2564 | 31,232 | 07-Nov-2005 | 01:45 | IA-64 | SP1 | Not
Applicable | | Swprv.dll | 5.2.3790.2564 | 831,488 | 07-Nov-2005 | 01:45 | IA-64 | SP1 | Not
Applicable | | Vssadmin.exe | 5.2.3790.2564 | 314,368 | 07-Nov-2005 | 01:45 | IA-64 | SP1 | Not
Applicable | | Vssapi.dll | 5.2.3790.2564 | 1,642,496 | 07-Nov-2005 | 01:45 | IA-64 | SP1 | Not
Applicable | | Vssvc.exe | 5.2.3790.2564 | 2,588,672 | 07-Nov-2005 | 01:45 | IA-64 | SP1 | Not
Applicable | | Wvssapi.dll | 5.2.3790.2564 | 561,152 | 07-Nov-2005 | 01:45 | x86 | SP1 | WOW | | Wvss_ps.dll | 5.2.3790.2564 | 19,456 | 07-Nov-2005 | 01:45 | x86 | SP1 | WOW |
Hotfix installation instructionsTo 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: - Download the hotfix package for the Windows PE
image.
- Extract the 910380 hotfix package to a folder by using the
/x switch.
- 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:
828217
How to apply the 824146 security patch to your Windows Preinstallation Environment
STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section.
| Modification Type: | Minor | Last Reviewed: | 4/26/2006 |
|---|
| Keywords: | kbHotfixServer kbtshoot kbprb KB910380 kbAudEndUser kbAudKnowledgeWorker |
|---|
|