Some applications that require that VDS calls be completed quickly may be severely affected by this 45-second delay. To enable compatibility with these applications, a hotfix is available to circumvent this delay. This hotfix introduces a registry entry. By modifying this registry entry, you can enable or disable the delay.
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 (SP1) or Windows Server 2003 Service Pack 2 (SP2) installed.
Restart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other previously released hotfixes.
Registry information
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756�
How to back up and restore the registry in Windows
To enable this hotfix, follow these steps:
- Click Start, click Run, type regedit, and then click OK.
- Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VDS
- On the Edit menu, point to New, and then click DWORD value.
- Type DisableReenumDelay as the new entry name.
- Right-click DisableReenumDelay, and then click Modify.
- In the Value data box, type 1, and then click OK.
- Exit Registry Editor.
The value of the registry entry is read when the service is loaded. Therefore, you must restart the VDS service to make the value active.
To disable this hotfix, set the value of the DisableReenumDelay registry entry to zero (0).
You cannot disable this delay on a per-application basis. You can disable this delay only on a per-system basis. By changing this value, disk changes may not be found by the
Reenumerate calls. Therefore, the applications that rely on VDS notifications to find new disks may not receive these notifications. Some applications may not work correctly if they do not receive notifications of disk arrivals or of disk removals. Therefore, make sure that you modify this registry entry.
If an application can recognize which disks are supposed to be available, the application may be able to work around these lost notifications by verifying whether a disk is detected. For example, when an application masks or unmasks a Logical Unit Number (LUN), the application may recognize which disks should be available. Therefore, we recommend that you use this hotfix only when the following conditions are true:
- The applications that use VDS can work around the lost notifications.
- No other applications use VDS to find disk arrivals and disk removals.
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 SP1, x86-based versions
Collapse this tableExpand this table
File name | File version | File size | Date | Time | Platform | SP requirement |
---|
Vds.exe | 5.2.3790.3094 | 359,424 | 21-Feb-2008 | 09:31 | x86 | SP1 |
Vdsbas.dll | 5.2.3790.3094 | 147,968 | 26-Feb-2008 | 15:27 | x86 | SP1 |
Vdsdyndr.dll | 5.2.3790.3094 | 326,144 | 26-Feb-2008 | 15:27 | x86 | SP1 |
Vdshba_i.mof | Not Applicable | 13,967 | 09-Dec-2007 | 17:34 | Not Applicable | SP1 |
Vdshba_u.mof | Not Applicable | 345 | 09-Dec-2007 | 17:34 | Not Applicable | SP1 |
Vdsldr.exe | 5.2.3790.3094 | 19,456 | 21-Feb-2008 | 09:31 | x86 | SP1 |
Vdsutil.dll | 5.2.3790.3094 | 62,976 | 26-Feb-2008 | 15:27 | x86 | SP1 |
Vds_ps.dll | 5.2.3790.3094 | 30,720 | 26-Feb-2008 | 15:27 | x86 | SP1 |
Windows Server 2003 with SP2, x86-based versions
Collapse this tableExpand this table
File name | File version | File size | Date | Time | Platform | SP requirement |
---|
Vds.exe | 5.2.3790.4242 | 359,424 | 22-Feb-2008 | 11:53 | x86 | SP2 |
Vdsbas.dll | 5.2.3790.4242 | 147,968 | 26-Feb-2008 | 13:28 | x86 | SP2 |
Vdsdyndr.dll | 5.2.3790.4242 | 326,656 | 26-Feb-2008 | 15:08 | x86 | SP2 |
Vdsldr.exe | 5.2.3790.4242 | 19,456 | 22-Feb-2008 | 11:52 | x86 | SP2 |
Vdsutil.dll | 5.2.3790.4242 | 62,976 | 26-Feb-2008 | 15:08 | x86 | SP2 |
Vds_ps.dll | 5.2.3790.4242 | 30,720 | 26-Feb-2008 | 15:08 | x86 | SP2 |
Windows Server 2003 with SP1, IA-64-based versions
Collapse this tableExpand this table
File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
---|
Vds.exe | 5.2.3790.3094 | 1,172,480 | 26-Feb-2008 | 13:22 | IA-64 | SP1 | Not Applicable |
Vdsbas.dll | 5.2.3790.3094 | 503,808 | 26-Feb-2008 | 13:22 | IA-64 | SP1 | Not Applicable |
Vdsdyndr.dll | 5.2.3790.3094 | 766,976 | 26-Feb-2008 | 13:22 | IA-64 | SP1 | Not Applicable |
Vdshba_i.mof | Not Applicable | 13,967 | 26-Feb-2008 | 13:22 | Not Applicable | SP1 | Not Applicable |
Vdshba_u.mof | Not Applicable | 345 | 26-Feb-2008 | 13:22 | Not Applicable | SP1 | Not Applicable |
Vdsldr.exe | 5.2.3790.3094 | 63,488 | 26-Feb-2008 | 13:22 | IA-64 | SP1 | Not Applicable |
Vdsutil.dll | 5.2.3790.3094 | 175,104 | 26-Feb-2008 | 13:22 | IA-64 | SP1 | Not Applicable |
Vds_ps.dll | 5.2.3790.3094 | 45,568 | 26-Feb-2008 | 13:22 | IA-64 | SP1 | Not Applicable |
Wvds_ps.dll | 5.2.3790.3094 | 30,720 | 26-Feb-2008 | 13:22 | x86 | SP1 | WOW |
Windows Server 2003 with SP2, IA-64-based versions
Collapse this tableExpand this table
File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
---|
Vds.exe | 5.2.3790.4242 | 1,172,480 | 26-Feb-2008 | 13:26 | IA-64 | SP2 | Not Applicable |
Vdsbas.dll | 5.2.3790.4242 | 504,320 | 26-Feb-2008 | 13:26 | IA-64 | SP2 | Not Applicable |
Vdsdyndr.dll | 5.2.3790.4242 | 768,512 | 26-Feb-2008 | 13:26 | IA-64 | SP2 | Not Applicable |
Vdsldr.exe | 5.2.3790.4242 | 63,488 | 26-Feb-2008 | 13:26 | IA-64 | SP2 | Not Applicable |
Vdsutil.dll | 5.2.3790.4242 | 175,104 | 26-Feb-2008 | 13:26 | IA-64 | SP2 | Not Applicable |
Vds_ps.dll | 5.2.3790.4242 | 45,568 | 26-Feb-2008 | 13:26 | IA-64 | SP2 | Not Applicable |
Wvds_ps.dll | 5.2.3790.4242 | 30,720 | 26-Feb-2008 | 13:26 | x86 | SP2 | WOW |
Windows Server 2003, x64-based versions
Collapse this tableExpand this table
File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
---|
Vds.exe | 5.2.3790.3094 | 623,616 | 26-Feb-2008 | 13:23 | x64 | SP1 | Not Applicable |
Vdsbas.dll | 5.2.3790.3094 | 263,680 | 26-Feb-2008 | 13:23 | x64 | SP1 | Not Applicable |
Vdsdyndr.dll | 5.2.3790.3094 | 456,192 | 26-Feb-2008 | 13:23 | x64 | SP1 | Not Applicable |
Vdshba_i.mof | Not Applicable | 13,967 | 26-Feb-2008 | 13:23 | Not Applicable | SP1 | Not Applicable |
Vdshba_u.mof | Not Applicable | 345 | 26-Feb-2008 | 13:23 | Not Applicable | SP1 | Not Applicable |
Vdsldr.exe | 5.2.3790.3094 | 29,696 | 26-Feb-2008 | 13:23 | x64 | SP1 | Not Applicable |
Vdsutil.dll | 5.2.3790.3094 | 95,232 | 26-Feb-2008 | 13:23 | x64 | SP1 | Not Applicable |
Vds_ps.dll | 5.2.3790.3094 | 41,472 | 26-Feb-2008 | 13:23 | x64 | SP1 | Not Applicable |
Wvds_ps.dll | 5.2.3790.3094 | 30,720 | 26-Feb-2008 | 13:23 | x86 | SP1 | WOW |
Windows Server 2003 with SP2, x64-based versions
Collapse this tableExpand this table
File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
---|
Vds.exe | 5.2.3790.4242 | 623,616 | 26-Feb-2008 | 13:29 | x64 | SP2 | Not Applicable |
Vdsbas.dll | 5.2.3790.4242 | 264,192 | 26-Feb-2008 | 13:29 | x64 | SP2 | Not Applicable |
Vdsdyndr.dll | 5.2.3790.4242 | 456,704 | 26-Feb-2008 | 13:29 | x64 | SP2 | Not Applicable |
Vdsldr.exe | 5.2.3790.4242 | 29,696 | 26-Feb-2008 | 13:29 | x64 | SP2 | Not Applicable |
Vdsutil.dll | 5.2.3790.4242 | 95,232 | 26-Feb-2008 | 13:29 | x64 | SP2 | Not Applicable |
Vds_ps.dll | 5.2.3790.4242 | 41,472 | 26-Feb-2008 | 13:29 | x64 | SP2 | Not Applicable |
Wvds_ps.dll | 5.2.3790.4242 | 30,720 | 26-Feb-2008 | 13:29 | x86 | SP2 | WOW |