Symptoms
This issue occurs when you run Windows Management Instrumentation (WMI) queries in a third-party WMI provider in Windows 8 or Windows Server 2012. If the third-party WMI provider has any memory leaks, WMI queries may fail in the WMI provider.
Cause
This issue occurs because memory is not automatically reclaimed by the WMI service host, and a WMI provider that has memory leaks can eventually exhaust the memory available to that WMI service host.
Resolution
Hotfix information
Important Do not install a language pack after you install this hotfix. If you do, the language-specific changes in the hotfix will not be applied, and you will have to reinstall the hotfix. For more information, see Add language packs to Windows.
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.
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 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 website:
http://support.microsoft.com/contactus/?ws=supportNote 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
There is no prerequisite to apply this hotfix.
Registry information
To use the hotfix in this package, you do not have to make any changes to the registry.
Restart requirement
You may have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 8 and Windows Server 2012 file information and notes
Important Windows 8 hotfixes and Windows Server 2012 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8/Windows Server 2012" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
-
The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
Version
Product
Milestone
Service branch
6.2.920 0.16xxx
Windows 8 and Windows Server 2012
RTM
GDR
6.2.920 0.20 xxx
Windows 8 and Windows Server 2012
RTM
LDR
6.2.920 0.21xxx
Windows 8 and Windows Server 2012
RTM
LDR
-
GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
-
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 8
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Wmidcprv.dll |
6.2.9200.16384 |
131,072 |
26-Jul-2012 |
03:20 |
x86 |
|
Wmiprvsd.dll |
6.2.9200.21427 |
614,912 |
14-Mar-2015 |
06:03 |
x86 |
|
Wmiprvse.exe |
6.2.9200.21427 |
375,808 |
14-Mar-2015 |
06:04 |
x86 |
For all supported x64-based versions of Windows 8 and of Windows Server 2012
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Wmidcprv.dll |
6.2.9200.16384 |
183,808 |
26-Jul-2012 |
03:08 |
x64 |
|
Wmiprvsd.dll |
6.2.9200.21427 |
830,464 |
14-Mar-2015 |
06:56 |
x64 |
|
Wmiprvse.exe |
6.2.9200.21427 |
479,232 |
14-Mar-2015 |
06:56 |
x64 |
|
Wmidcprv.dll |
6.2.9200.20623 |
131,072 |
02-Feb-2013 |
07:04 |
x86 |
|
Wmiprvse.exe |
6.2.9200.21427 |
375,808 |
14-Mar-2015 |
06:04 |
x86 |
Additional file information
Additional file information for Windows 8 and for Windows Server 2012
Additional files for all supported x86-based versions of Windows 8
|
File property |
Value |
|---|---|
|
File name |
X86_6d77da458d86367e1a34323a36e21f2e_31bf3856ad364e35_6.2.9200.21427_none_f1d6376b46068471.manifest |
|
File version |
Not applicable |
|
File size |
709 |
|
Date (UTC) |
16-Mar-2015 |
|
Time (UTC) |
20:54 |
|
Platform |
Not applicable |
|
File name |
X86_microsoft-windows-wmi-core-providerhost_31bf3856ad364e35_6.2.9200.21427_none_0ddb30d575b62c52.manifest |
|
File version |
Not applicable |
|
File size |
12,377 |
|
Date (UTC) |
16-Mar-2015 |
|
Time (UTC) |
20:58 |
|
Platform |
Not applicable |
Additional files for all supported x64-based versions of Windows 8 and of Windows Server 2012
|
File property |
Value |
|---|---|
|
File name |
Amd64_7bc0352c4520ba885d21f8c13e83916d_31bf3856ad364e35_6.2.9200.21427_none_b9a24bc2c7cac31a.manifest |
|
File version |
Not applicable |
|
File size |
1,068 |
|
Date (UTC) |
16-Mar-2015 |
|
Time (UTC) |
20:54 |
|
Platform |
Not applicable |
|
File name |
Amd64_fded1aeab88566038e002afff271e8ba_31bf3856ad364e35_6.2.9200.21427_none_006387b4ddbf8dd1.manifest |
|
File version |
Not applicable |
|
File size |
713 |
|
Date (UTC) |
16-Mar-2015 |
|
Time (UTC) |
20:54 |
|
Platform |
Not applicable |
|
File name |
Amd64_microsoft-windows-wmi-core-providerhost_31bf3856ad364e35_6.2.9200.21427_none_69f9cc592e139d88.manifest |
|
File version |
Not applicable |
|
File size |
12,379 |
|
Date (UTC) |
16-Mar-2015 |
|
Time (UTC) |
20:55 |
|
Platform |
Not applicable |
|
File name |
Wow64_microsoft-windows-wmi-core-providerhost_31bf3856ad364e35_6.2.9200.21427_none_744e76ab62745f83.manifest |
|
File version |
Not applicable |
|
File size |
8,210 |
|
Date (UTC) |
16-Mar-2015 |
|
Time (UTC) |
20:55 |
|
Platform |
Not applicable |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
See the terminology that Microsoft uses to describe software updates.
