To apply this hotfix, you must be running one of the following: If you do not see your language, it is because a hotfix is not available for that language. The "Hotfix download available" form displays the languages for which the hotfix is available. 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: 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. To resolve this issue in Windows 8.1 or Windows Server 2012 R2, install update rollup 2911106, or install the hotfix that is described in this article.įor more information about how to obtain update rollup 2911101, click the following article number to view the article in the Microsoft Knowledge Base:Ģ911101 Windows RT, Windows 8, and Windows Server 2012 update rollup: January 2014For more information about how to obtain update rollup 2911106, click the following article number to view the article in the Microsoft Knowledge Base:Ģ911106 Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 update rollup: January 2014Ī supported hotfix is available from Microsoft. To resolve this issue in Windows 8 or Windows Server 2012, install update rollup 2911101, or install the hotfix that is described in this article. In this situation, the application does not maintain the remote connection. However, the TCP connection is still "live" from the client side. If the TCP connection uses ephemeral (short-lived) loopback addresses, the connection may be dropped suddenly after 40 to 50 seconds. You run an application that connects remotely by using a TCP connection on a computer that's running Windows 8, Windows 8.1, Windows Server 2012, or Windows Server 2012 R2.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |