"STATUS_CONNECTION_RESET" error when an application reads a file in Windows Server 2012 R2 or Windows Server 2012

Прилага се за: Windows Server 2012 R2 DatacenterWindows Server 2012 R2 StandardWindows Server 2012 R2 Essentials

This article describes an issue that occurs on Windows Server 2012 R2-based or Windows Server 2012-based failover clusters. A hotfix is available to resolve this issue. The hotfix has a prerequisite.


Consider the following scenario:
  • You have two failover clusters that communicate across Ethernet gateways.
  • An application in the first cluster tries to read a file from the second cluster through Server Message Block (SMB) Multichannel.
  • There is continuous packet loss or connection disconnect issue between the endpoints due to too much network traffic.
In this scenario, the read request freezes on the node of the first cluster and any attempts to call the CancelSynchronousIO function also freezes. Additionally, you receive a "STATUS_CONNECTION_RESET" error message repeatedly until the computer crashes.


This issue occurs because SMB Redirector keeps retry indefinitely if the network disconnect error for Multichannel occurs until it hits the retry limit of 65,535, and then the computer crashes. SMB Redirector should eventually time out such request instead of retrying indefinitely.


To resolve this issue, we have released a hotfix. Even though this issue has been observed only in Windows Server 2012 R2 or Windows Server 2012, the hotfix also applies to Windows 8.1, Windows RT 8.1, and Windows 8.

Important If you install a language pack after you install this hotfix, you must reinstall this hotfix. Therefore, we recommend that you install any language packs that you need before you install this hotfix. For more information, see Add language packs to Windows.

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


To apply this hotfix, you must have April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) installed in Windows 8.1 or Windows Server 2012 R2.

There is no prerequisite for Windows 8 or Windows Server 2012 to install this update.

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.


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


See the terminology that Microsoft uses to describe software updates.