Article ID: 921909
Article Last Modified on 10/11/2007
APPLIES TO
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition
- Microsoft Windows Server 2003, Web Edition
- Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
- Microsoft Windows Server 2003, Datacenter x64 Edition
- Microsoft Windows Server 2003, Standard x64 Edition
- Microsoft Windows Server 2003, Enterprise 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:
- 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.
CAUSE
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.
RESOLUTION
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:
889100 How to obtain the latest service pack for Windows Server 2003
Hotfix information
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
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Cimwin32.dll | 5.2.3790.2794 | 1,372,672 | 16-Sep-2006 | 11:42 | x86 |
Windows Server 2003, Itanium-based versions
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Cimwin32.dll | 5.2.3790.2794 | 5,041,152 | 15-Sep-2006 | 21:00 | IA-64 |
Windows Server 2003, x64-based versions
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Cimwin32.dll | 5.2.3790.2794 | 2,352,128 | 15-Sep-2006 | 20:58 | x64 |
STATUS
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.
MORE INFORMATION
For more information, 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: kbbug kbfix kbqfe kbpubtypekc kbhotfixserver kbwinserv2003presp2fix kbwinserv2003sp2fix KB921909
