You find high CPU usage for the Wmiprvse.exe process on a terminal server that is running Windows Server 2008 when you run the Windows System Resource Manager

Article translations Article translations
Article ID: 970067 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

You use the Windows System Resource Manager to manage the CPU usage and the memory usage on a terminal server that is running Windows Server 2008. In this situation, you find that the CPU usage for the Wmiprvse.exe process is higher than expected.

CAUSE

The Windows System Resource Manager uses Windows Management Instrumentation (WMI) polling queries to check the status for certain key processes, such as the Cluster service. However, these queries consume lots of CPU resources, and the Windows System Resource Manager uses polling intervals of 30 seconds and 60 seconds. As more users log on and as more processes are started, the WMI queries use more and more CPU resources. The query interval that is used when the Accounting feature is enabled can be controlled by a registry value. However, the interval for the Cluster service polling query cannot be adjusted, and this query runs every 60 seconds.

RESOLUTION

You can adjust the interval for the Accounting query by using the
PollingInterval
registry value. After you apply this following hotfix, you can also change the interval for the Cluster service polling query. You can set the polling intervals to anywhere in the range of one time per second to one time per every 86,400 seconds (1 day). A value of greater than 300 (5 minutes) is recommended only for the
ClusterSvcStatusPollInterval
registry value and is recommended only when the computer is not a cluster node.

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 the problem described in this article. 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:
http://support.microsoft.com/contactus/?ws=support
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.


Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

Prerequisites

To apply this hotfix, your computer must run be running one of the following operating systems:
  • Windows Server 2008
  • Windows Server 2008 Service Pack 2 (SP2)
Additionally, your computer must have the Terminal Service role and the Windows System Resource Manager feature installed.

Restart requirement

You must restart the computer after you apply this hotfix.

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

You can use the following registry entry to change the interval between the WMI polling queries that are used by the Accounting feature:
Location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\WSRM\Parameters
Name: PollingInterval
Type: REG_DWORD
Value: Polling query interval in seconds 
The
PollingInterval
registry entry specifies the interval in seconds. The default value is 30 (30 seconds).

After you install this hotfix, you can use the following registry entry to change the interval between the WMI polling queries:
Location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\WSRM\Parameters
Name: ClusterSvcStatusPollInterval
Type: REG_DWORD
Value: Polling query interval in seconds
The
ClusterSvcStatusPollInterval
registry entry specifies the interval in seconds. The default value is 300 (5 minutes).

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.
For all supported x86-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirement
Allocationpol.xmlNot Applicable6801-Apr-200919:13Not ApplicableSP1
Allocationpol.xml.bakNot Applicable6801-Apr-200919:13Not ApplicableSP1
Calendar.xmlNot Applicable5901-Apr-200919:13Not ApplicableSP1
Calendar.xml.bakNot Applicable5901-Apr-200919:13Not ApplicableSP1
Conditionalpolicy.xmlNot Applicable3,83801-Apr-200919:13Not ApplicableSP1
Conditionalpolicy.xml.bakNot Applicable3,83801-Apr-200919:13Not ApplicableSP1
Createdb.cmdNot Applicable3,38401-Apr-200919:14Not ApplicableSP1
Createdb.sqlNot Applicable27,80501-Apr-200919:14Not ApplicableSP1
Selectionpol.xmlNot Applicable10201-Apr-200919:13Not ApplicableSP1
Selectionpol.xml.bakNot Applicable10201-Apr-200919:13Not ApplicableSP1
Shrinkdb.cmdNot Applicable2,32101-Apr-200919:14Not ApplicableSP1
Wsrm.exe6.0.6001.22450754,68815-Jun-200912:59x86SP1
Wsrm.mofNot Applicable96701-Apr-200919:13Not ApplicableSP1
Wsrmdat.ldfNot Applicable1,048,57601-Apr-200919:14Not ApplicableSP1
Wsrmdat.mdfNot Applicable2,097,15201-Apr-200919:14Not ApplicableSP1
Wsrmdbmig.exe6.0.6001.22450140,80015-Jun-200912:59x86SP1
Wsrmeventlog.dll6.0.6001.224507,68015-Jun-200912:59x86SP1
Wsrmfeature.cmdNot Applicable72401-Apr-200919:13Not ApplicableSP1
Wsrmperf.xmlNot Applicable7,49601-Apr-200919:13Not ApplicableSP1
Wsrmsign.cerNot Applicable68901-Apr-200919:14Not ApplicableSP1
Wsrmsign.dllNot Applicable11,28001-Apr-200919:14x86SP1
Wsrmsign.sqlNot Applicable9,55901-Apr-200919:14Not ApplicableSP1
Wsrmsmtpcons.mofNot Applicable4,36001-Apr-200919:13Not ApplicableSP1
Allocationpol.xmlNot Applicable6803-Apr-200921:52Not ApplicableSP2
Allocationpol.xml.bakNot Applicable6803-Apr-200921:52Not ApplicableSP2
Calendar.xmlNot Applicable5903-Apr-200921:52Not ApplicableSP2
Calendar.xml.bakNot Applicable5903-Apr-200921:52Not ApplicableSP2
Conditionalpolicy.xmlNot Applicable3,83803-Apr-200921:52Not ApplicableSP2
Conditionalpolicy.xml.bakNot Applicable3,83803-Apr-200921:52Not ApplicableSP2
Createdb.cmdNot Applicable3,38403-Apr-200921:52Not ApplicableSP2
Createdb.sqlNot Applicable27,80503-Apr-200921:52Not ApplicableSP2
Selectionpol.xmlNot Applicable10203-Apr-200921:52Not ApplicableSP2
Selectionpol.xml.bakNot Applicable10203-Apr-200921:52Not ApplicableSP2
Shrinkdb.cmdNot Applicable2,32103-Apr-200921:52Not ApplicableSP2
Wsrm.exe6.0.6002.22152754,68815-Jun-200912:48x86SP2
Wsrm.mofNot Applicable96703-Apr-200921:52Not ApplicableSP2
Wsrmdat.ldfNot Applicable1,048,57603-Apr-200921:52Not ApplicableSP2
Wsrmdat.mdfNot Applicable2,097,15203-Apr-200921:52Not ApplicableSP2
Wsrmdbmig.exe6.0.6002.22152140,80015-Jun-200912:48x86SP2
Wsrmeventlog.dll6.0.6002.221527,68015-Jun-200912:47x86SP2
Wsrmfeature.cmdNot Applicable72403-Apr-200921:52Not ApplicableSP2
Wsrmperf.xmlNot Applicable7,49603-Apr-200921:52Not ApplicableSP2
Wsrmsign.cerNot Applicable68903-Apr-200921:52Not ApplicableSP2
Wsrmsign.dllNot Applicable11,28003-Apr-200921:52x86SP2
Wsrmsign.sqlNot Applicable9,55903-Apr-200921:52Not ApplicableSP2
Wsrmsmtpcons.mofNot Applicable4,36003-Apr-200921:52Not ApplicableSP2
For all supported x64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirement
Allocationpol.xmlNot Applicable6801-Apr-200916:45Not ApplicableSP1
Allocationpol.xml.bakNot Applicable6801-Apr-200916:45Not ApplicableSP1
Calendar.xmlNot Applicable5901-Apr-200916:45Not ApplicableSP1
Calendar.xml.bakNot Applicable5901-Apr-200916:45Not ApplicableSP1
Conditionalpolicy.xmlNot Applicable3,83801-Apr-200916:45Not ApplicableSP1
Conditionalpolicy.xml.bakNot Applicable3,83801-Apr-200916:45Not ApplicableSP1
Createdb.cmdNot Applicable3,38401-Apr-200916:45Not ApplicableSP1
Createdb.sqlNot Applicable27,80501-Apr-200916:45Not ApplicableSP1
Selectionpol.xmlNot Applicable10201-Apr-200916:45Not ApplicableSP1
Selectionpol.xml.bakNot Applicable10201-Apr-200916:45Not ApplicableSP1
Shrinkdb.cmdNot Applicable2,32101-Apr-200916:45Not ApplicableSP1
Wsrm.exe6.0.6001.224501,134,59215-Jun-200913:15x64SP1
Wsrm.mofNot Applicable96701-Apr-200916:45Not ApplicableSP1
Wsrmdat.ldfNot Applicable1,048,57601-Apr-200916:45Not ApplicableSP1
Wsrmdat.mdfNot Applicable2,097,15201-Apr-200916:45Not ApplicableSP1
Wsrmdbmig.exe6.0.6001.22450156,16015-Jun-200913:15x64SP1
Wsrmeventlog.dll6.0.6001.224507,68015-Jun-200913:15x64SP1
Wsrmfeature.cmdNot Applicable72401-Apr-200916:45Not ApplicableSP1
Wsrmperf.xmlNot Applicable7,49601-Apr-200916:45Not ApplicableSP1
Wsrmsign.cerNot Applicable68901-Apr-200916:45Not ApplicableSP1
Wsrmsign.dllNot Applicable11,28001-Apr-200916:45x86SP1
Wsrmsign.sqlNot Applicable9,55901-Apr-200916:45Not ApplicableSP1
Wsrmsmtpcons.mofNot Applicable4,36001-Apr-200916:45Not ApplicableSP1
Allocationpol.xmlNot Applicable6803-Apr-200921:09Not ApplicableSP2
Allocationpol.xml.bakNot Applicable6803-Apr-200921:09Not ApplicableSP2
Calendar.xmlNot Applicable5903-Apr-200921:09Not ApplicableSP2
Calendar.xml.bakNot Applicable5903-Apr-200921:09Not ApplicableSP2
Conditionalpolicy.xmlNot Applicable3,83803-Apr-200921:09Not ApplicableSP2
Conditionalpolicy.xml.bakNot Applicable3,83803-Apr-200921:09Not ApplicableSP2
Createdb.cmdNot Applicable3,38403-Apr-200921:09Not ApplicableSP2
Createdb.sqlNot Applicable27,80503-Apr-200921:09Not ApplicableSP2
Selectionpol.xmlNot Applicable10203-Apr-200921:09Not ApplicableSP2
Selectionpol.xml.bakNot Applicable10203-Apr-200921:09Not ApplicableSP2
Shrinkdb.cmdNot Applicable2,32103-Apr-200921:09Not ApplicableSP2
Wsrm.exe6.0.6002.221521,134,59215-Jun-200913:07x64SP2
Wsrm.mofNot Applicable96703-Apr-200921:09Not ApplicableSP2
Wsrmdat.ldfNot Applicable1,048,57603-Apr-200921:09Not ApplicableSP2
Wsrmdat.mdfNot Applicable2,097,15203-Apr-200921:09Not ApplicableSP2
Wsrmdbmig.exe6.0.6002.22152156,16015-Jun-200913:06x64SP2
Wsrmeventlog.dll6.0.6002.221527,68015-Jun-200913:06x64SP2
Wsrmfeature.cmdNot Applicable72403-Apr-200921:09Not ApplicableSP2
Wsrmperf.xmlNot Applicable7,49603-Apr-200921:09Not ApplicableSP2
Wsrmsign.cerNot Applicable68903-Apr-200921:09Not ApplicableSP2
Wsrmsign.dllNot Applicable11,28003-Apr-200921:09x86SP2
Wsrmsign.sqlNot Applicable9,55903-Apr-200921:09Not ApplicableSP2
Wsrmsmtpcons.mofNot Applicable4,36003-Apr-200921:09Not ApplicableSP2
For all supported Itanium-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirement
Allocationpol.xmlNot Applicable6801-Apr-200916:45Not ApplicableSP1
Allocationpol.xml.bakNot Applicable6801-Apr-200916:45Not ApplicableSP1
Calendar.xmlNot Applicable5901-Apr-200916:45Not ApplicableSP1
Calendar.xml.bakNot Applicable5901-Apr-200916:45Not ApplicableSP1
Conditionalpolicy.xmlNot Applicable3,83801-Apr-200916:45Not ApplicableSP1
Conditionalpolicy.xml.bakNot Applicable3,83801-Apr-200916:45Not ApplicableSP1
Createdb.cmdNot Applicable3,38401-Apr-200916:45Not ApplicableSP1
Createdb.sqlNot Applicable27,80501-Apr-200916:45Not ApplicableSP1
Selectionpol.xmlNot Applicable10201-Apr-200916:45Not ApplicableSP1
Selectionpol.xml.bakNot Applicable10201-Apr-200916:45Not ApplicableSP1
Shrinkdb.cmdNot Applicable2,32101-Apr-200916:45Not ApplicableSP1
Wsrm.exe6.0.6001.224502,075,13615-Jun-200913:05IA-64SP1
Wsrm.mofNot Applicable96701-Apr-200916:45Not ApplicableSP1
Wsrmdbmig.exe6.0.6001.22450350,20815-Jun-200913:04IA-64SP1
Wsrmeventlog.dll6.0.6001.224507,68015-Jun-200913:03IA-64SP1
Wsrmfeature.cmdNot Applicable72401-Apr-200916:45Not ApplicableSP1
Wsrmperf.xmlNot Applicable7,49601-Apr-200916:45Not ApplicableSP1
Wsrmsmtpcons.mofNot Applicable4,36001-Apr-200916:45Not ApplicableSP1
Allocationpol.xmlNot Applicable6803-Apr-200921:10Not ApplicableSP2
Allocationpol.xml.bakNot Applicable6803-Apr-200921:10Not ApplicableSP2
Calendar.xmlNot Applicable5903-Apr-200921:10Not ApplicableSP2
Calendar.xml.bakNot Applicable5903-Apr-200921:10Not ApplicableSP2
Conditionalpolicy.xmlNot Applicable3,83803-Apr-200921:10Not ApplicableSP2
Conditionalpolicy.xml.bakNot Applicable3,83803-Apr-200921:10Not ApplicableSP2
Createdb.cmdNot Applicable3,38403-Apr-200921:10Not ApplicableSP2
Createdb.sqlNot Applicable27,80503-Apr-200921:10Not ApplicableSP2
Selectionpol.xmlNot Applicable10203-Apr-200921:10Not ApplicableSP2
Selectionpol.xml.bakNot Applicable10203-Apr-200921:10Not ApplicableSP2
Shrinkdb.cmdNot Applicable2,32103-Apr-200921:10Not ApplicableSP2
Wsrm.exe6.0.6002.221522,075,13615-Jun-200912:53IA-64SP2
Wsrm.mofNot Applicable96703-Apr-200921:10Not ApplicableSP2
Wsrmdbmig.exe6.0.6002.22152350,20815-Jun-200912:51IA-64SP2
Wsrmeventlog.dll6.0.6002.221527,68015-Jun-200912:51IA-64SP2
Wsrmfeature.cmdNot Applicable72403-Apr-200921:10Not ApplicableSP2
Wsrmperf.xmlNot Applicable7,49603-Apr-200921:10Not ApplicableSP2
Wsrmsmtpcons.mofNot Applicable4,36003-Apr-200921:10Not ApplicableSP2

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

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

Properties

Article ID: 970067 - Last Review: October 7, 2011 - Revision: 2.0
APPLIES TO
  • Windows Server 2008 for Itanium-Based Systems
  • Windows Server 2008 Datacenter
  • Windows Server 2008 Enterprise
  • Windows Server 2008 Standard
Keywords: 
kbautohotfix kbexpertiseadvanced kbfix kbsurveynew kbqfe KB970067

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com