Sign in with Microsoft
Sign in or create an account.
Hello,
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.

This article describes an issue in which the CPU usage is high in Windows 8.1 or Windows Server 2012 R2. A hotfix is available to resolve this issue. Before you install this hotfix, check out the Prerequisites section.

Symptoms

Consider the following scenario that takes Microsoft Exchange Server 2013 as an example:

  • The Mailbox server role is enabled in Exchange Server 2013.

  • Exchange mailboxes use extended MAPI to communicate with the Exchange Server.

  • The extended MAPI uses Microsoft RPC over HTTP (remote procedure call over HTTP) protocol.

  • Many clients (such as mobile devices) are dropping connections to the Exchange Server.



In this scenario, the CPU usage on the Exchange server may reach 100 percent.

Cause

This issue occurs because Internet Information Services (IIS) changed the method of closing the HTTP connection in Windows 8.1 or Windows Server 2012 R2.

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

To apply this hotfix, you must have update 2919355 installed in Windows 8.1 or Windows Server 2012 R2.

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.1 and Windows Server 2012 R2 file information and notes

Important Windows 8.1 hotfixes and Windows Server 2012 R2 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.1/Windows Server 2012 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separatelyin 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.1

File name

File version

File size

Date

Time

Platform

Hwebcore.dll

8.5.9600.17708

15,360

19-Feb-2015

01:23

x86

Iiscore.dll

8.5.9600.17708

235,008

19-Feb-2015

01:20

x86

W3dt.dll

8.5.9600.17708

100,352

19-Feb-2015

01:22

x86

For all supported x64-based versions of Windows 8.1 and of Windows Server 2012 R2

File name

File version

File size

Date

Time

Platform

Hwebcore.dll

8.5.9600.17708

17,408

19-Feb-2015

01:44

x64

Iiscore.dll

8.5.9600.17708

337,920

19-Feb-2015

01:42

x64

W3dt.dll

8.5.9600.17708

111,104

19-Feb-2015

01:47

x64

Hwebcore.dll

8.5.9600.17708

15,360

19-Feb-2015

01:23

x86

Iiscore.dll

8.5.9600.17708

235,008

19-Feb-2015

01:20

x86

W3dt.dll

8.5.9600.17708

100,352

19-Feb-2015

01:22

x86

Additional file information

Additional file information for Windows 8.1 and for Windows Server 2012 R2

Additional files for all supported x86-based versions of Windows 8.1

File property

Value

File name

X86_4b11afd6ee03a772e783a7c2347162f1_31bf3856ad364e35_6.3.9600.17708_none_1f76dfc714ceeb25.manifest

File version

Not applicable

File size

713

Date (UTC)

19-Feb-2015

Time (UTC)

10:10

Platform

Not applicable

File name

X86_microsoft-windows-i..rewebenginebinaries_31bf3856ad364e35_6.3.9600.17708_none_29fe611741429da1.manifest

File version

Not applicable

File size

6,937

Date (UTC)

19-Feb-2015

Time (UTC)

03:16

Platform

Not applicable

Additional files for all supported x64-based versions of Windows 8.1 and of Windows Server 2012 R2

File property

Value

File name

Amd64_0a8662933f382d509771238341417877_31bf3856ad364e35_6.3.9600.17708_none_3ad1cc83f4fcc937.manifest

File version

Not applicable

File size

717

Date (UTC)

19-Feb-2015

Time (UTC)

10:10

Platform

Not applicable

File name

Amd64_ea6db2aa8a82dc8681c9f59d76516d0a_31bf3856ad364e35_6.3.9600.17708_none_14973a1f6be20b8f.manifest

File version

Not applicable

File size

717

Date (UTC)

19-Feb-2015

Time (UTC)

10:10

Platform

Not applicable

File name

Amd64_microsoft-windows-i..rewebenginebinaries_31bf3856ad364e35_6.3.9600.17708_none_861cfc9af9a00ed7.manifest

File version

Not applicable

File size

6,943

Date (UTC)

19-Feb-2015

Time (UTC)

03:57

Platform

Not applicable

File name

Wow64_microsoft-windows-i..rewebenginebinaries_31bf3856ad364e35_6.3.9600.17708_none_9071a6ed2e00d0d2.manifest

File version

Not applicable

File size

6,062

Date (UTC)

19-Feb-2015

Time (UTC)

03:16

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.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!

×