

The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix. This hotfix might receive additional testing. Apply this hotfix only to systems that are experiencing the problem described in this article. However, this hotfix is intended to correct only the problem that is described in this article. These application vendors use the TDI filter driver or the TDI extension driver (TDX) on a computer that is running Windows 7 or Windows Server 2008 R2.Ī supported hotfix is available from Microsoft. Note This hotfix temporarily resolves this issue for application vendors before they migrate their implementation to Windows Filtering Platform (WFP). To resolve this issue, install this hotfix. Therefore, the application receives an instance of the 10054 error that indicates that a connection is reset when the application receives data from the connection. Instead, the TCP/IP driver sends a notification that the TCP/IP driver is ready to receive data when the incomplete TCP connection is created. This issue occurs because the TCP/IP driver does not close an incomplete TCP connection. WSAECONNRESET (10054) Connection reset by peer.Ī existing connection was forcibly closed by the remote host.
