The result collection of the Win32_LogicalDiskToPartition WMI query may not include some drive letters in Windows Server 2003

Consider the following scenario:

• You have a computer that is running Microsoft Windows Server 2003.
• You have a Windows Management Instrumentation (WMI) script that uses the Win32_LogicalDiskToPartition association class to query for drive information.
• You run the WMI script on the computer.

In this scenario, some drive letters may not be included in the result collection.

This problem occurs when third-party device drivers or some applications open the \\PHYSICALDRIVE drive volumes for exclusive access before the WMI subsystem can open the drive volumes. These applications can be antivirus applications or system management tools. Therefore, the WMI subsystem cannot access the drive volumes. The WMI subsystem does not raise any error when the WMI subsystem cannot access the drive volumes. Instead, the WMI subsystem merely skips the inaccessible drive volumes.

Note \\PHYSICALDRIVE is a placeholder. This placeholder can be \\PHYSICALDRIVE0, or \\PHYSICALDRIVE1, or other values depending on the disk configurations.

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

Windows Server 2003, Itanium-based versions

Windows Server 2003, x64-based versions

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.

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