Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. The W3wp.exe process has high CPU usage when you run PowerShell commands for Exchange

The W3wp.exe process has high CPU usage when you run PowerShell commands for Exchange

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You are connected to an Exchange server that is based on a server that is running Windows Server 2012.
  • You run PowerShell commands for Exchange.

In this scenario, you may find that the W3wp.exe process has high CPU usage. This causes Exchange failures or significant decrease in performance issues.

↑ Back to the top

Cause

This problem occurs because of a deadlock situation in Web Services for Management (WS-Management).

↑ Back to the top

Resolution

Hotfix information

A supported hotfix is available from Microsoft Support. 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, go to the following Microsoft website:
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.

Prerequisites

There are no prerequisites for installing this hotfix.





Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

↑ Back to the top

File information
The English (United States) 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 and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8" 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.

    VersionProductMilestoneService branch
    6.2.920 0.16 xxxWindows 8 and Windows Server 2012RTMGDR
    6.2.920 0.21 xxxWindows 8 and Windows Server 2012RTMLDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows 8 and Windows Server 2012" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely 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 nameFile versionFile sizeDateTimePlatform
Winrm.cmdNot applicable3502-Jun-201214:34Not applicable
Winrm.vbsNot applicable204,10502-Jun-201214:34Not applicable
Wsmagent.dll6.2.9200.1638424,06426-Jul-201203:20x86
Wsmagent.mofNot applicable82202-Jun-201214:34Not applicable
Wsmagentuninstall.mofNot applicable75402-Jun-201214:34Not applicable
Wsmanconfig_schema.xmlNot applicable4,67502-Jun-201214:34Not applicable
Wsmanhttpconfig.exe6.2.9200.1638430,20826-Jul-201203:21x86
Wsmanmigrationplugin.dll6.2.9200.1638456,83226-Jul-201203:20x86
Wsmauto.dll6.2.9200.16384138,24026-Jul-201203:20x86
Wsmauto.mofNot applicable4,43002-Jun-201214:34Not applicable
Wsmplpxy.dll6.2.9200.1638410,75226-Jul-201203:20x86
Wsmprovhost.exe6.2.9200.1638435,84026-Jul-201203:21x86
Wsmpty.xslNot applicable1,55902-Jun-201214:34Not applicable
Wsmres.dll6.2.9200.1638460,41626-Jul-201202:44x86
Wsmsvc.dll6.2.9200.211782,044,41616-Jul-201422:34x86
Wsmtxt.xslNot applicable2,42602-Jun-201214:34Not applicable
Wsmwmipl.dll6.2.9200.21178227,32816-Jul-201422:34x86
For all supported x64-based versions of Windows 8 and Windows Server 2012
File nameFile versionFile sizeDateTimePlatform
Winrm.cmdNot applicable3502-Jun-201214:34Not applicable
Winrm.vbsNot applicable204,10502-Jun-201214:34Not applicable
Wsmagent.dll6.2.9200.1638429,69626-Jul-201203:08x64
Wsmagent.mofNot applicable82202-Jun-201214:34Not applicable
Wsmagentuninstall.mofNot applicable75402-Jun-201214:34Not applicable
Wsmanconfig_schema.xmlNot applicable4,67502-Jun-201214:34Not applicable
Wsmanhttpconfig.exe6.2.9200.1638428,67226-Jul-201203:08x64
Wsmanmigrationplugin.dll6.2.9200.1638466,56026-Jul-201203:08x64
Wsmauto.dll6.2.9200.16384156,67226-Jul-201203:08x64
Wsmauto.mofNot applicable4,43002-Jun-201214:34Not applicable
Wsmplpxy.dll6.2.9200.1638414,33626-Jul-201203:08x64
Wsmprovhost.exe6.2.9200.1638430,72026-Jul-201203:08x64
Wsmpty.xslNot applicable1,55902-Jun-201214:34Not applicable
Wsmres.dll6.2.9200.1638460,41626-Jul-201202:34x64
Wsmsvc.dll6.2.9200.211782,838,01616-Jul-201422:30x64
Wsmtxt.xslNot applicable2,42602-Jun-201214:34Not applicable
Wsmwmipl.dll6.2.9200.21178309,24816-Jul-201422:30x64
Winrm.cmdNot applicable3502-Jun-201214:34Not applicable
Winrm.vbsNot applicable204,10502-Jun-201214:34Not applicable
Wsmagent.dll6.2.9200.1638424,06426-Jul-201203:20x86
Wsmagent.mofNot applicable82202-Jun-201214:34Not applicable
Wsmagentuninstall.mofNot applicable75402-Jun-201214:34Not applicable
Wsmanconfig_schema.xmlNot applicable4,67502-Jun-201214:34Not applicable
Wsmanhttpconfig.exe6.2.9200.1638430,20826-Jul-201203:21x86
Wsmanmigrationplugin.dll6.2.9200.1638456,83226-Jul-201203:20x86
Wsmauto.dll6.2.9200.16384138,24026-Jul-201203:20x86
Wsmauto.mofNot applicable4,43002-Jun-201214:34Not applicable
Wsmplpxy.dll6.2.9200.1638410,75226-Jul-201203:20x86
Wsmprovhost.exe6.2.9200.1638435,84026-Jul-201203:21x86
Wsmpty.xslNot applicable1,55902-Jun-201214:34Not applicable
Wsmres.dll6.2.9200.1638460,41626-Jul-201202:44x86
Wsmsvc.dll6.2.9200.211782,044,41616-Jul-201422:34x86
Wsmtxt.xslNot applicable2,42602-Jun-201214:34Not applicable
Wsmwmipl.dll6.2.9200.21178227,32816-Jul-201422:34x86

Additional file information for Windows 8 and Windows Server 2012

Additional files for all supported x86-based versions of Windows 8
File nameX86_46db4c051e95a6ff3e06141a3ac6599a_31bf3856ad364e35_6.2.9200.21179_none_07f549bf9ea1a863.manifest
File versionNot applicable
File size720
Date (UTC)23-Jul-2014
Time (UTC)21:17
PlatformNot applicable
File nameX86_microsoft-windows-w..for-management-core_31bf3856ad364e35_6.2.9200.21179_none_c7a9d2ef977fb5ce.manifest
File versionNot applicable
File size195,191
Date (UTC)23-Jul-2014
Time (UTC)21:17
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 8 and Windows Server 2012
File nameAmd64_59a9d5b9c9fc36407add8645968bdf83_31bf3856ad364e35_6.2.9200.21179_none_76f95a9c203aa30d.manifest
File versionNot applicable
File size1,090
Date (UTC)23-Jul-2014
Time (UTC)21:20
PlatformNot applicable
File nameAmd64_microsoft-windows-w..for-management-core_31bf3856ad364e35_6.2.9200.21179_none_23c86e734fdd2704.manifest
File versionNot applicable
File size195,199
Date (UTC)23-Jul-2014
Time (UTC)21:20
PlatformNot applicable
File nameWow64_microsoft-windows-w..for-management-core_31bf3856ad364e35_6.2.9200.21179_none_2e1d18c5843de8ff.manifest
File versionNot applicable
File size191,314
Date (UTC)23-Jul-2014
Time (UTC)21:20
PlatformNot applicable

↑ Back to the top

Status

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

↑ Back to the top

References

Learn about the terminology that Microsoft uses to describe software updates.

↑ Back to the top

Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbexpertiseinter, kbsurveynew, kbbug

↑ Back to the top

Article Info
Article ID : 2985459
Revision : 1
Created on : 1/7/2017
Published on : 9/9/2014
Exists online : False
Views : 224