Article ID: 941773
Article Last Modified on 11/6/2007
APPLIES TO
- Microsoft Windows Server 2003 Service Pack 2, when used with:
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Web Edition
- Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
- Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
- Microsoft Windows Server 2003, Standard x64 Edition
- Microsoft Windows Server 2003, Enterprise x64 Edition
- Microsoft Windows Server 2003, Datacenter x64 Edition
- Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
- Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
SYMPTOMS
Consider the following scenario.
- A DVD-ROM drive or a CD-ROM drive is installed on a Windows Server 2003 Service Pack 2-based computer.
- A physical disk hosts multiple volumes.
- You use the scripting function of the Diskpart.exe tool to modify volume attributes based on a script.
In this scenario, the Diskpart.exe tool may return error code 4.
CAUSE
Multiple instances of the Diskpart.exe tool may return different volume numbers. Therefore, the script may try to access the volume by using an incorrect volume number. If the script tries to change the attributes on a volume that does not support the scripted action, the script does not run correctly. For example, the script cannot modify the volume attributes on a CD-ROM drive.
RESOLUTION
Hotfix information
A supported hotfix is now 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 Windows Server 2003 service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:
Prerequisites
To apply this hotfix, you must have Windows Server 2003 Service Pack 2 installed on the computer.
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 2, x86-based versions
| File name | File version | File size | Date | Time | Platform | SP requirement |
|---|---|---|---|---|---|---|
| Vds.exe | 5.2.3790.4172 | 358,912 | 18-Oct-2007 | 14:11 | x86 | SP2 |
| Vdsbas.dll | 5.2.3790.4172 | 147,968 | 18-Oct-2007 | 18:52 | x86 | SP2 |
| Vdsdyndr.dll | 5.2.3790.4172 | 326,656 | 18-Oct-2007 | 18:52 | x86 | SP2 |
| Vdshba_i.mof | Not applicable | 13,965 | 07-Dec-2006 | 21:57 | Not applicable | SP2 |
| Vdshba_u.mof | Not applicable | 343 | 07-Dec-2006 | 21:57 | Not applicable | SP2 |
| Vdsldr.exe | 5.2.3790.4172 | 19,456 | 18-Oct-2007 | 14:11 | x86 | SP2 |
| Vdsutil.dll | 5.2.3790.4172 | 61,952 | 18-Oct-2007 | 18:52 | x86 | SP2 |
| Vds_ps.dll | 5.2.3790.4172 | 30,720 | 18-Oct-2007 | 18:52 | x86 | SP2 |
Windows Server 2003 with Service Pack 2, Itanium-based versions
| File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
|---|---|---|---|---|---|---|---|
| Vds.exe | 5.2.3790.4172 | 1,170,944 | 18-Oct-2007 | 18:47 | IA-64 | SP2 | Not applicable |
| Vdsbas.dll | 5.2.3790.4172 | 504,320 | 18-Oct-2007 | 18:47 | IA-64 | SP2 | Not applicable |
| Vdsdyndr.dll | 5.2.3790.4172 | 768,512 | 18-Oct-2007 | 18:47 | IA-64 | SP2 | Not applicable |
| Vdshba_i.mof | Not applicable | 13,965 | 18-Oct-2007 | 18:47 | Not applicable | SP2 | Not applicable |
| Vdshba_u.mof | Not applicable | 343 | 18-Oct-2007 | 18:47 | Not applicable | SP2 | Not applicable |
| Vdsldr.exe | 5.2.3790.4172 | 63,488 | 18-Oct-2007 | 18:47 | IA-64 | SP2 | Not applicable |
| Vdsutil.dll | 5.2.3790.4172 | 173,568 | 18-Oct-2007 | 18:47 | IA-64 | SP2 | Not applicable |
| Vds_ps.dll | 5.2.3790.4172 | 45,568 | 18-Oct-2007 | 18:47 | IA-64 | SP2 | Not applicable |
| Wvds_ps.dll | 5.2.3790.4172 | 30,720 | 18-Oct-2007 | 18:47 | x86 | SP2 | WOW |
Windows Server 2003 with Service Pack 2, x64-based versions
| File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
|---|---|---|---|---|---|---|---|
| Vds.exe | 5.2.3790.4172 | 622,592 | 18-Oct-2007 | 18:47 | x64 | SP2 | Not applicable |
| Vdsbas.dll | 5.2.3790.4172 | 264,192 | 18-Oct-2007 | 18:47 | x64 | SP2 | Not applicable |
| Vdsdyndr.dll | 5.2.3790.4172 | 456,704 | 18-Oct-2007 | 18:47 | x64 | SP2 | Not applicable |
| Vdshba_i.mof | Not applicable | 13,965 | 18-Oct-2007 | 18:47 | Not applicable | SP2 | Not applicable |
| Vdshba_u.mof | Not applicable | 343 | 18-Oct-2007 | 18:47 | Not applicable | SP2 | Not applicable |
| Vdsldr.exe | 5.2.3790.4172 | 29,696 | 18-Oct-2007 | 18:47 | x64 | SP2 | Not applicable |
| Vdsutil.dll | 5.2.3790.4172 | 94,720 | 18-Oct-2007 | 18:47 | x64 | SP2 | Not applicable |
| Vds_ps.dll | 5.2.3790.4172 | 41,472 | 18-Oct-2007 | 18:47 | x64 | SP2 | Not applicable |
| Wvds_ps.dll | 5.2.3790.4172 | 30,720 | 18-Oct-2007 | 18:47 | x86 | SP2 | WOW |
WORKAROUND
To work around this problem, use one of the following methods.
Method 1
Keep the Virtual Disk service running. To do this, open the Disk Management Microsoft Management Console (MMC) snap-in. Or, run the Diskpart.exe tool in the background.
Method 2
Remove the DVD-ROM drive or the CD-ROM drive from the computer if you do not require it.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
Sample Diskpart.exe outputs
The following are sample outputs of the Diskpart.exe tool when this problem occurs.
Output 1
Microsoft DiskPart version 5.2.3790.3959 Copyright (C) 1999-2001 Microsoft Corporation. On computer: <computer name> Disk 0 is now the selected disk. Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- Volume 0 C NTFS Partition 18 GB Healthy System Volume 1 D TestOS NTFS Partition 38 GB Healthy Volume 2 E NTFS Partition 10 GB Healthy Volume 3 F FAT Partition 502 MB Healthy Volume 4 G FAT32 Partition 502 MB Healthy Volume 5 H NTFS Partition 502 MB Healthy Volume 6 I NTFS Partition 502 MB Healthy Volume 7 J CD_ROM CDFS DVD-ROM 378 MB Healthy
Output 2
Microsoft DiskPart version 5.2.3790.3959 Copyright (C) 1999-2001 Microsoft Corporation. On computer: <computer name> Disk 0 is now the selected disk. Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- Volume 0 J CD_ROM CDFS DVD-ROM 378 MB Healthy Volume 1 C NTFS Partition 18 GB Healthy System Volume 2 D TestOS NTFS Partition 38 GB Healthy Volume 3 E NTFS Partition 10 GB Healthy Volume 4 F FAT Partition 502 MB Healthy Volume 5 G FAT32 Partition 502 MB Healthy Volume 6 H NTFS Partition 502 MB Healthy Volume 7 I NTFS Partition 502 MB Healthy
Note In these samples, the CD-ROM drive is randomly returned at the beginning of the list or at the end of the list.
Scripting of the Diskpart.exe tool
The Diskpart.exe tool supports scripted operations. To start a Diskpart script, use the following command:
diskpart /s ScriptFile
You can script the Diskpart.exe tool in Windows XP environments, in Windows 2000 environments, in Remote Installation Services (RIS) unattended install environments, and in the Windows Preinstall Environment (PE) for OEMs. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
300415 A description of the Diskpart command-line utility
REFERENCES
For more information about software update terminology, 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: kbexpertiseinter kbwinserv2003postsp2fix kbbug kbfix kbhotfixserver kbqfe kbpubtypekc KB941773
