Known issues in this updateSymptoms
After you apply this update on a Remote Desktop Session (RDS) host, some new users cannot connect to an RDP session. Instead, those users see a black screen, and they are eventually disconnected. This issue occurs at unspecified intervals.
The following events are usually logged when this issue occurs:
|Event Logs||Event Source||ID||Description|
|Microsoft-Windows-TerminalServices-LocalSessionManager/Operational||Microsoft-Windows-TerminalServices-LocalSessionManager||36||An error occurred when transitioning from CsrConnected in response to EvCsrInitialized. (ErrorCode 0x80004005)|
|Application||Microsoft-Windows-Winlogon||4005||The Windows logon process has unexpectedly terminated.|
During virtual channel management, a deadlock condition occurs that prevents the RDS service from accepting new connections.
To fix this issue, install November 2016 Preview of Monthly Quality Rollup for Windows 8.1 and Windows Server 2012 R2 (KB3197875).
Method 1: Windows UpdateThis update is provided as a Recommended update on Windows Update. For more information about how to run Windows Update, see How to get an update through Windows Update.
Method 2: Microsoft Update CatalogTo get the stand-alone package for this update, go to the Microsoft Update Catalog website.
Note You must be running Microsoft Internet Explorer 6 or a later version.
Method 3: Microsoft Download CenterThe following files are available for download from the Microsoft Download Center.
|All supported x86-based versions of Windows 8.1||Download the package now.|
|All supported x64-based versions of Windows 8.1||Download the package now.|
|All supported x64-based versions of Windows Server 2012 R2||Download the package now.|
Update detail information
PrerequisitesTo apply this update, 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.
Restart requirementYou must restart the computer after you apply this update.
Registry informationWarning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
To enable the improved performance for duplicate broadcast data received in LBFO, add the follow registry subkey:
- In Registry Editor, locate and then select the following registry subkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MsLbfoProvider\Parameters\NdisAdapters\<GUID>
- Press and hold (or right-click) <GUID>, select New, and then select DWORD (32-bit) Value.
- Name the new registry entry as DropStandbyReceive.
- Double-click the DropStandbyReceive registry entry.
- In the Edit DWORD Value dialog box, enter 1 in the Value data field, and then select OK.
- Exit Registry Editor.
- Drop packet events are generated when there is a packet drop of the passive NIC.
- After you set the registry subkey, you have to restart the NIC Teaming (LBFO) service by using the following commands.
Note This causes a brief network disruption.sc stop mslbfoprovider
sc start mslbfoprovider
Update replacement informationThis update doesn't replace any previously released update.
Article ID: 3179574 - Last Review: Nov 15, 2016 - Revision: 1