Volume GUIDs become invalid in Windows Server 2003 when the disk layout changes outside the context of the Virtual Disk Service and of the APIs

Consider the following scenario. In Windows Server 2003, you use a custom application that uses the Virtual Disk Service (VDS). The application changes the volume globally unique identifiers (GUIDs) outside the context of the VDS and of the APIs. The volume GUIDs are stored in the VDS cache. In this scenario, the GUIDs become invalid.

When this problem occurs, you may receive an error message that resembles the following, depending on the application that is being used:

This problem occurs because of a bug in the VDS. This problem occurs when the VDS is not involved in a disk layout change or when the VDS is not notified of a disk layout change. When this problem occurs, even the Reenumerate() method and the Refresh() method do not update the cache correctly. Therefore, a call to the IVdsDisk::GetProperties() method returns the previous disk GUID, and this GUID is no longer valid. If the VDS is restarted, the volume information is updated correctly. However, if you stop the VDS while the service is in this state, the service may crash.

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, 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 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. To create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" section and the online request forms display 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, the computer must be running one of the following operating systems:

�	A 32-bit version of Windows Server 2003 with Service Pack 1 (SP1) or with Service Pack 2 (SP2)
�	An Itanium-based version of Windows Server 2003 with SP1 or with SP2
�	An x64-based version of Windows Server 2003

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

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, x86-based versions

File name	File version	File size	Date	Time	Platform	SP requirement	Service branch
Vds.exe	5.2.3790.2976	358,912	17-Jul-2007	11:01	x86	SP1	SP1QFE
Vdsbas.dll	5.2.3790.2976	147,968	18-Jul-2007	05:59	x86	SP1	SP1QFE
Vdsdyndr.dll	5.2.3790.2976	326,144	18-Jul-2007	06:46	x86	SP1	SP1QFE
Vdshba_i.mof	Not Applicable	13,967	23-Feb-2007	09:12	Not Applicable	SP1	SP1QFE
Vdshba_u.mof	Not Applicable	345	23-Feb-2007	09:12	Not Applicable	SP1	SP1QFE
Vdsldr.exe	5.2.3790.2976	19,456	17-Jul-2007	11:01	x86	SP1	SP1QFE
Vdsutil.dll	5.2.3790.2976	61,952	18-Jul-2007	05:59	x86	SP1	SP1QFE
Vds_ps.dll	5.2.3790.2976	30,720	18-Jul-2007	05:59	x86	SP1	SP1QFE
Vds.exe	5.2.3790.4119	358,912	17-Jul-2007	13:02	x86	SP2	SP2QFE
Vdsbas.dll	5.2.3790.4119	147,968	18-Jul-2007	06:20	x86	SP2	SP2QFE
Vdsdyndr.dll	5.2.3790.4119	326,656	18-Jul-2007	06:20	x86	SP2	SP2QFE
Vdshba_i.mof	Not Applicable	13,965	07-Dec-2006	21:57	Not Applicable	SP2	SP2QFE
Vdshba_u.mof	Not Applicable	343	07-Dec-2006	21:57	Not Applicable	SP2	SP2QFE
Vdsldr.exe	5.2.3790.4119	19,456	17-Jul-2007	13:02	x86	SP2	SP2QFE
Vdsutil.dll	5.2.3790.4119	61,952	18-Jul-2007	06:20	x86	SP2	SP2QFE
Vds_ps.dll	5.2.3790.4119	30,720	18-Jul-2007	06:20	x86	SP2	SP2QFE

Windows Server 2003, x64-based versions

File name	File version	File size	Date	Time	Platform	SP requirement	Service branch
Vds.exe	5.2.3790.2976	622,080	18-Jul-2007	06:48	x64	SP1	SP1QFE
Vdsbas.dll	5.2.3790.2976	263,680	18-Jul-2007	06:48	x64	SP	SP1QFE
Vdsdyndr.dll	5.2.3790.2976	456,192	18-Jul-2007	06:48	x64	SP	SP1QFE
Vdshba_i.mof	Not Applicable	13,967	18-Jul-2007	06:48	Not Applicable	SP	SP1QFE
Vdshba_u.mof	Not Applicable	345	18-Jul-2007	06:48	Not Applicable	SP	SP1QFE
Vdsldr.exe	5.2.3790.2976	29,696	18-Jul-2007	06:48	x64	SP	SP1QFE
Vdsutil.dll	5.2.3790.2976	94,720	18-Jul-2007	06:48	x64	SP	SP1QFE
Vds_ps.dll	5.2.3790.2976	41,472	18-Jul-2007	06:48	x64	SP	SP1QFE
Wvds_ps.dll	5.2.3790.2976	30,720	18-Jul-2007	06:48	x86	SP1	SP1QFE\WOW
Vds.exe	5.2.3790.4119	622,080	18-Jul-2007	06:59	x64	SP2	SP2QFE
Vdsbas.dll	5.2.3790.4119	263,680	18-Jul-2007	06:59	x64	SP	SP2QFE
Vdsdyndr.dll	5.2.3790.4119	456,704	18-Jul-2007	06:59	x64	SP	SP2QFE
Vdshba_i.mof	Not Applicable	13,965	18-Jul-2007	06:59	Not Applicable	SP	SP2QFE
Vdshba_u.mof	Not Applicable	343	18-Jul-2007	06:59	Not Applicable	SP	SP2QFE
Vdsldr.exe	5.2.3790.4119	29,696	18-Jul-2007	06:59	x64	SP	SP2QFE
Vdsutil.dll	5.2.3790.4119	94,720	18-Jul-2007	06:59	x64	SP	SP2QFE
Vds_ps.dll	5.2.3790.4119	41,472	18-Jul-2007	06:59	x64	SP	SP2QFE
Wvds_ps.dll	5.2.3790.4119	30,720	18-Jul-2007	06:59	x86	SP2	SP2QFE\WOW

Windows Server 2003, Itanium-based versions

File name	File version	File size	Date	Time	Platform	SP requirement	Service branch
Vds.exe	5.2.3790.2976	1,170,944	18-Jul-2007	06:48	IA-64	SP1	SP1QFE
Vdsbas.dll	5.2.3790.2976	503,808	18-Jul-2007	06:48	IA-64	SP	SP1QFE
Vdsdyndr.dll	5.2.3790.2976	766,976	18-Jul-2007	06:48	IA-64	SP	SP1QFE
Vdshba_i.mof	Not Applicable	13,967	18-Jul-2007	06:48	Not Applicable	SP	SP1QFE
Vdshba_u.mof	Not Applicable	345	18-Jul-2007	06:48	Not Applicable	SP	SP1QFE
Vdsldr.exe	5.2.3790.2976	63,488	18-Jul-2007	06:48	IA-64	SP	SP1QFE
Vdsutil.dll	5.2.3790.2976	173,568	18-Jul-2007	06:48	IA-64	SP	SP1QFE
Vds_ps.dll	5.2.3790.2976	45,568	18-Jul-2007	06:48	IA-64	SP	SP1QFE
Wvds_ps.dll	5.2.3790.2976	30,720	18-Jul-2007	06:48	x86	SP1	SP1QFE\WOW
Vds.exe	5.2.3790.4119	1,170,944	18-Jul-2007	06:59	IA-64	SP2	SP2QFE
Vdsbas.dll	5.2.3790.4119	503,808	18-Jul-2007	06:59	IA-64	SP	SP2QFE
Vdsdyndr.dll	5.2.3790.4119	768,512	18-Jul-2007	06:59	IA-64	SP	SP2QFE
Vdshba_i.mof	Not Applicable	13,965	18-Jul-2007	06:59	Not Applicable	SP	SP2QFE
Vdshba_u.mof	Not Applicable	343	18-Jul-2007	06:59	Not Applicable	SP	SP2QFE
Vdsldr.exe	5.2.3790.4119	63,488	18-Jul-2007	06:59	IA-64	SP	SP2QFE
Vdsutil.dll	5.2.3790.4119	173,568	18-Jul-2007	06:59	IA-64	SP	SP2QFE
Vds_ps.dll	5.2.3790.4119	45,568	18-Jul-2007	06:59	IA-64	SP	SP2QFE
Wvds_ps.dll	5.2.3790.4119	30,720	18-Jul-2007	06:59	x86	SP2	SP2QFE\WOW

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base: For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Technical support for x64-based versions of Microsoft Windows

If your hardware came with a Microsoft Windows x64 edition already installed, your hardware manufacturer provides technical support and assistance for the Windows x64 edition. In this case, your hardware manufacturer provides support because a Windows x64 edition was included with your hardware. Your hardware manufacturer might have customized the Windows x64 edition installation by using 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 a Windows x64 edition. 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. If you purchased a Windows x64 edition such as a Microsoft Windows Server 2003 x64 edition separately, contact Microsoft for technical support.

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: