- Recommended hotfixes and updates for Remote Desktop Services in Windows Server 2012 R2
- Summary
- Prerequisites
- Updates and hotfixes for Remote Desktop Connection Brokers
- Updates and hotfixes for Remote Desktop Gateway
- Updates and hotfixes for Remote Desktop Licensing
- Updates and hotfixes for Remote Desktop Session Hosts
- Updates and hotfixes for Remote Desktop Virtualization Hosts
- Updates and hotfixes for Remote Desktop Web Access
- Remote Desktop clients (mstsc.exe)
- List of currently available hotfixes for Distributed File System (DFS) technologies in Windows Server 2012 and Windows Server 2012 R2
- Summary
- Windows Server 2012 R2
- Windows Server 2012
- More information
- Recommended hotfixes and updates for Windows Server 2012 R2-based failover clusters
- Summary
- Any Windows Server 2012 R2 cluster
- Windows Server 2012 R2 Hyper-V clusters
- References
Recommended hotfixes and updates for Remote Desktop Services in Windows Server 2012 R2
This article describes the hotfixes and updates that are currently available for Remote Desktop Services in Microsoft Windows Server 2012 R2.
Original product version: В Windows Server 2012 R2
Original KB number: В 3147099
Summary
This article describes the currently available fixes that are highly recommended for Remote Desktop Services in Windows Server 2012 R2 environments. These fixes have prerequisites for all Remote Desktop Services roles, and they apply to the following areas for Remote Desktop Services 2012 R2:
- Remote Desktop Connection Brokers
- Remote Desktop Gateway
- Remote Desktop Licensing
- Remote Desktop Session Hosts
- Remote Desktop Virtualization Hosts
- Remote Desktop Web Access
Additional Remote Desktop client information is introduced:
- RDP 8.1 updates for Windows 7
- RDP 8.1 and 8.0 new features
We recommend that you install these fixes to ensure the highest level of reliability.
Prerequisites
Before you install the hotfix for any Remote Desktop Services role, you must have the following updates installed.
Date the update was added | Related Knowledge Base article | Title | Component | Why we recommend this update |
---|---|---|---|---|
Ongoing | Any remaining Windows updates | N/A | Multiple | The most recent Windows updates and fixes outside of normal security updates, in addition to the rollup packages that are listed in this table. |
December 2014 | 3013769 | December 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 | Multiple | An update rollup package that resolves issues and includes performance and reliability improvements. Available from Windows Update and for individual download from the Microsoft Download Center. To apply this update, you must first install the update 2919355 on Windows Server 2012 R2. |
November 2014 | 3000850 | November 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 | Multiple | A cumulative update that includes the security updates and non-security updates (including for Remote Desktop Services) that were released between April 2014 and November 2014. Available from Windows Update and for individual download from the Microsoft Download Center. To apply this update, you must first install the update 2919355 on Windows Server 2012 R2. |
Updates and hotfixes for Remote Desktop Connection Brokers
See the prerequisites table before you install any update or hotfix for this server role.
Date the update was added | Related Knowledge Base article | Title | Component | Why we recommend this update |
---|---|---|---|---|
November 2015 | 3091411 | User connection fails when many connections are made to Windows Server 2012 R2-based RD Connection Broker | Multiple | This rollup contains the following improvements:
|
December 2014 | 3020474 | Communication issues occur when Remote Desktop Connection Broker connects to SQL Server in Windows Server 2012 R2 | script | If you are using RD Connection Broker High Availability, make sure that you watch for the security events that are described in the Knowledge Base article that indicate communication issues between the RD Connection Brokers and SQL Server. You have to enable auditing for failure events by using the script auditpol /set /subcategory:»Filtering Platform Connection» /success:disable /failure:enable |
This script unblocks only UDP port 1434 from a Windows level. If you have a network device that also blocks this port, you must unblock at this level, too.
Updates and hotfixes for Remote Desktop Gateway
See the prerequisites table before you install any update or hotfix for this server role.
Date the update was added | Related Knowledge Base article | Title | Component | Why we recommend this update |
---|---|---|---|---|
March 2016 | 3123913 | Remote Desktop Gateway server crashes during certain user disconnect scenarios in Windows Server 2012 R2 | aaedge.dll | Latest version of Aaedge.dll that resolves several issues in which the RD Gateway service crashes and causes user disconnections. Also includes 3042843. |
Updates and hotfixes for Remote Desktop Licensing
See the prerequisites table before you install any update or hotfix for this server role.
Date the update was added | Related Knowledge Base article | Title | Component | Why we recommend this update |
---|---|---|---|---|
March 2016 | 3108326 | Licensing servers become deadlocked under high load in Windows Server 2012 R2 | lserver.dll | Latest version of Lserver.dll that resolves an issue in which multiple RD Licensing servers crash or restart on high load. Any RDSH that is configured in Per-Device mode would refuse all connections requests while their LS is in this state. Also includes 3092695 and 3084952. |
January 2015 | 3013108 | RDS License Manager shows no issued free or temporary client access licenses in Windows Server 2012 R2 | licmgr.exe | Latest version of Licmgr.exe that fixes an issue in which the RDS License Manager shows no issued free or temporary client access licenses in Windows Server 2012 R2. |
Updates and hotfixes for Remote Desktop Session Hosts
See the prerequisites table before you install any update or hotfix for this server role.
Date the update was added | Related Knowledge Base article | Title | Component | Why we recommend this update |
---|---|---|---|---|
April 2016 | 3146978 | RDS redirected resources showing degraded performance in Windows 8.1 or Windows Server 2012 R2 | Multiple | This update resolves slow RDP performance issues when you use redirected resources (drives, printers, and ports). |
December 2015 | 3127673 | Stop error 0x000000C2 or 0x0000003B when you’re running Remote Desktop Services in Windows Server 2012 R2 | win32k.sys & dxgkrnl.sys | This article describes a hotfix package that fixes a problem that causes Windows Server 2012 R2 to crash when you’re running Microsoft Remote Desktop Services (RDS). |
October 2015 | 3103000 | RemoteApp windows disappear and screen flickers when you switch between windows in Windows 8.1 or Windows Server 2012 R2 | rdpshell.exe | This update contains the latest RemoteApp server side components (mainly Rdpinit.exe/Rdpshell.exe) and includes all other RemoteApp section fixes that are listed in 2933664. |
There may also be fixes on the client side for RemoteApp. These fixes are listed again in 2933664 in the Remote Desktop Client section.
Updates and hotfixes for Remote Desktop Virtualization Hosts
See the prerequisites table before you install any update or hotfix for this server role.
Date the update was added | Related Knowledge Base article | Title | Component | Why we recommend this update |
---|---|---|---|---|
November 2015 | 3092688 | UPD profiles corrupted when a network connectivity issue occurs in Windows Server 2012 R2 | sessenv.dll | Latest version of Sessenv.dll. This update resolves an issue in which UPDs become corrupted when network connectivity issue occurs. |
If the VDI guest VMs are running Windows 8.1, you must also install this within the guest virtual machines.
Updates and hotfixes for Remote Desktop Web Access
See the prerequisites table before you install any update or hotfix for this server role.
Date the update was added | Related Knowledge Base article | Title | Component | Why we recommend this update |
---|---|---|---|---|
November 2015 | 3069129 | Blank page is displayed when you try to access RemoteApps on a Windows-based RD Web Access server | Multiple | Resolves an issue in which the RD Web Access server displays a blank web page if the number of published RemoteApps is greater than 999. Also includes the update 2957984. |
Remote Desktop clients (mstsc.exe)
RDP 8.1 updates for Windows 7
These fixes update the Remote Desktop Services server-side roles and components that are built around Remote Desktop Protocol (RDP) 8.1. However, although updates are performed on the server-side infrastructure, the Remote Desktop Clients are often left untouched. This can cause performance and reliability issues. By default, older clients such as Windows 7 Service Pack 1 (SP1) are restricted to RDP 7.1 and do not provide the new features and improvements that are available in RDP 8.1. Therefore, we have released the RDP 8.1 client for Windows 7 to provide significant performance and reliability improvements when these clients are connected to RDS 2012 R2 environments. To enable RDP 8.1 on Windows 7, follow these steps:
Verify which version of RDP you’re using. To do this, start the Remote Desktop Connection client program (mstsc.exe), click the small Remote Desktop icon in the top-left corner of the application dialog box, and then select About. Verify that the About message indicates Remote Desktop Protocol 8.1 supported.
If the About message indicates Remote Desktop Protocol 7.1 supported, install the following updates for RDP 8.1:
2574819: An update is available that adds support for DTLS in Windows 7 SP1 and Windows Server 2008 R2 SP1
2857650: Update that improves the RemoteApp and Desktop Connections features is available for Windows 7
2830477: Update for RemoteApp and Desktop Connections feature is available for Windows
2913751: Smart card redirection in remote sessions fails in a Windows 7 SP1-based RDP 8.1 client
2923545: Update for RDP 8.1 is available for Windows 7 SP1.31255
3125574: Convenience rollup update for Windows 7 SP1 and Windows Server 2008 R2 SP1
Install any outstanding Windows Updates.
RDP 8.1 and RDP 8.0 new features
For a list of features that were introduced in RDP 8.0, see Remote Desktop clients.
List of currently available hotfixes for Distributed File System (DFS) technologies in Windows Server 2012 and Windows Server 2012 R2
This article lists the hotfixes that are currently available for users who have installed Distributed File System (DFS) technologies on a Windows Server 2012-based computer or a Windows Server 2012 R2-based computer.
Original product version: В Windows Server 2012 R2
Original KB number: В 2951262
Summary
This Microsoft Knowledge Base articles that are listed in this article describe the available fixes. If you have installed DFS technologies on a Windows Server 2012-based computer or a Windows Server 2012 R2-based computer, we recommend that you review and install the hotfixes that are described in More information.
Note. The two technologies in DFS are DFS Namespaces (DFS-N) and DFS Replication (DFS-R).
A servicing approach of installing the monthly rollups provides customers with a consistent model for staying current and secure. You may substitute a more recent monthly rollup for an older monthly rollup. The remainder of the updates in this list are still required because some components in those updates were released prior to October 2016 and aren’t included in a more recent monthly rollup. For more information about this servicing approach, see Simplified servicing for Windows 7 and Windows 8.1: the latest improvements.
Windows Server 2012 R2
You can get the latest fixes for these DFS components by installing the following updates:
Windows Server 2012
You can get the latest fixes for these DFS components by installing the following updates:
More information
Some of the following tables contain blank cells to accommodate information that will be supplied later.
Recommended hotfixes and updates for Windows Server 2012 R2-based failover clusters
This article describes the hotfixes that are currently available for Windows Server 2012 R2-based failover clusters and are highly recommended to be installed on each server of a failover cluster.
Original product version: В Windows Server 2012 R2
Original KB number: В 2920151
Summary
Failover Cluster Management enables multiple servers to provide a high availability of server roles. Failover Cluster Management is frequently used for file services, virtual machines, database applications, and mail applications.
The process for installing service packs and hotfixes for Windows Server 2012 R2 differs from the process for earlier versions of Windows Server. In Windows Server 2012 R2, you can use the Cluster-Aware Updating (CAU) feature. CAU automates the software-updating process on clustered servers and maintains availability. For more information, see Cluster-Aware Updating Overview.
The following Microsoft Knowledge Base articles describe the currently available fixes that are highly recommended to be installed on all failover clusters. Most of the updates apply to computers that are running Windows Server 2012 R2. Some updates, such as KB 976424, may be required on computers that are running Windows Server 2008 R2 or Windows Server 2008 if those operating systems are present in the environment.
These updates are considered to be important installations to ensure the highest level of reliability.
Any Windows Server 2012 R2 cluster
You may substitute a newer monthly rollup in place of KB 4282815. The remainder of the updates in this list are still needed as some components in those updates released before September 2016 and are not included in the newer monthly rollup.
Date that update was added | Related Knowledge Base article | Title | Component | Why we recommend this update |
---|---|---|---|---|
June 14, 2018 | 4284815 | June 12, 2018-KB4284815 (Monthly Rollup) | Multiple | This security update rollup includes improvements and fixes that were released after September 2016. Available from Windows Update or for individual download from Microsoft Update Catalog and Microsoft Download Center. To apply this update, you must first install update 2919355 on Windows Server 2012 R2. |
June 21, 2017 | 3137728 | VSS restore fails when you use ResyncLuns VSS API in Windows Server 2012 R2-based failover cluster | Vssvc | Includes the fix from 3123538. Available from Windows Update or for individual download from Microsoft Update Catalog and Microsoft Download Center. To apply this update, you must first install update 2919355 on Windows Server 2012 R2. |
August 22, 2016 | 3179574 | August 2016 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 | Multiple | This rollup includes a fix that addresses an issue with cluster services that may stop working when network loss logging occurs when a network connection is down and virtual machines are configured with one possible owner. Available from Windows Update or for individual download from Microsoft Update Catalog. To apply this update, you must first install the update 2919355 on Windows Server 2012 R2. |
July 21, 2016 | 3172614 | July 2016 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 | Multiple | This rollup includes improvements and fixes from June 2016 update rollup KB 3161606 and May 2016 update rollup KB 3156418 including an update (3153887) that increases the default values of SameSubnetThreshold, CrossSubnetThreshold, and RouteHistoryLength to be more tolerant of brief transient network issues. Available on Windows update or for individual download from Microsoft Update Catalog. To apply this update, you must first install the update 2919355 on Windows Server 2012 R2. |
October 28, 2015 | 3091057 | Cluster validation fails in the Validate Simultaneous Failover test in a Windows Server 2012 R2-based failover cluster | Cprepsrv | Changes some timing of the Validate Simultaneous failover test to more accurately verify the storage compatibility with the failover cluster. Available for individual download. |
December 18, 2014 | 3013769 | December 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 | Multiple | An update rollup package that resolves issues and includes performance and reliability improvements. Available from Windows Update and for individual download from Download Center. To apply this update, you must first install the update 2919355 on Windows Server 2012 R2. |
November 18, 2014 | 3000850 | November 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 | Multiple | A cumulative update that includes the security updates and nonsecurity updates including Failover Clustering updates that were released between April 2014 and November 2014. Available from Windows Update and for individual download from Download Center. To apply this update, you must first install the update 2919355 on Windows Server 2012 R2. |
April 8, 2014 | 2919355 | Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 Update April, 2014 | Multiple | A cumulative update that includes the security updates and nonsecurity updates including Failover Clustering updates that were released before March 2014. Available from Windows Update and for individual download from Download Center. |
December 18, 2013 | 976424 | Error code when the kpasswd protocol fails after you perform an authoritative restore: «KDC_ERROR_S_PRINCIPAL_UNKNOWN» | KDCSVC | Enables you to add a Windows Server 2012 failover cluster. Install on every domain controller that is running Windows Server 2008 Service Pack 2 (SP2) or Windows Server 2008 R2. Otherwise, Create Cluster may fail when you try to set the password for the cluster computer object, and you receive a CreateClusterNameCOIfNotExists (6783): Unable to set password on error message. This hotfix is included in Windows Server 2008 R2 Service Pack 1 (SP1). |
Windows Server 2012 R2 Hyper-V clusters
In addition to the updates listed above, the following Microsoft Knowledge Base articles describe currently available fixes that are highly recommended to be installed on Hyper-V failover clusters. These updates target reliability improvements when backing up virtual machines on Hyper-V failover clusters.
Date that update was added | Related Knowledge Base article | Title | Component | Why we recommend this update |
---|---|---|---|---|
June 21, 2017 | 3145384 | MinDiffAreaFileSize registry value limit is increased from 3 GB to 50 GB in Windows 8.1 or Windows Server 2012 R2 | Volsnap.sys | Describes an update that increases the MinDiffAreaFileSize registry key value limit from 3 GB to 50 GB in Windows 8.1 and Windows Server 2012 R2. Before you install this update, see the «Prerequisites» section. Includes the fix from 3060678. Available from Windows Update or for individual download from Microsoft Update Catalog. To apply this update, you must first install the update 2919355 on Windows Server 2012 R2. |
September 15, 2015 | 3063283 | Update to improve the backup of Hyper-V Integrated components in Hyper-V Server 2012 R2 | Hyper-V Integration Services | Increases the time-out to detect the volumes to shadow copy when the Guest OS has multiple volumes. Available for individual download. To apply this update, you must first install the update 2919355 on Windows Server 2012 R2. |
References
For more information about the recommended hotfixes and updates for Windows Server 2012-based Hyper-V servers and Windows Server 2012-based Failover Clusters, see: