Wmiprvse.exe memory leak when a program queries disk or partition storage information in Windows Server 2012

Symptoms

When a program queries disk or partition storage information through the Windows Management Instrumentation (WMI) in Windows Server 2012, a memory leak occurs in the Wmiprvse.exe process. This memory leak condition could cause a loss of WMI functionality.

Note This issue may cause monitoring tools to stop working. For example, System Center Virtual Machine Manager, Failover Cluster Manager, and System Center Operations Manager may stop working.

Cause

This issue is caused by a bug in storagewmi.dll.

Resolution

To resolve this issue, we have released a hotfix for Windows 8 and Windows Server 2012.

Get the hotfix for Windows 8 or Windows Server 2012

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: 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

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.

More Information

File information ERROR: PhantomJS timeout occurred