This is because the definition of this flag doesn't include these applications and services. About this updateĪpplications and services that are written by using WinHTTP for Secure Sockets Layer (SSL) connections that use the WINHTTP_OPTION_SECURE_PROTOCOLS flag can't use TLS 1.1 or TLS 1.2 protocols. This update provides support for Transport Layer Security (TLS) 1.1 and TLS 1.2 in Windows Server 2012, Windows 7 Service Pack 1 (SP1), and Windows Server 2008 R2 SP1. Interestingly, when TLS 1.0 is enabled on the gateway, Windowsħ clients will negotiate TLS 1.0 while connecting to the Gateway, then use TLS 1.2 for the 'final' connection to the target.Windows Server 2012 Datacenter Windows Server 2012 Standard Windows Server 2012 Essentials Windows Server 2012 Foundation Windows Server 2008 R2 Service Pack 1 Windows Server 2008 R2 Datacenter Windows Server 2008 R2 Enterprise Windows Server 2008 R2 Standard Windows Server 2008 R2 Foundation Windows Server 2008 R2 for Itanium-Based Systems Windows 7 Service Pack 1 Windows 7 Ultimate Windows 7 Enterprise Windows 7 Professional Windows 7 Home Premium Windows 7 Home Basic Windows 7 Starter More. Despair as the Gateway refuses to negotiate TLS 1.2, attempts to use 1.0, then fails to connect.įrom SCHANNEL logs, making a direct rdp connection from the patched Windows 7 client to a target seems to allow TLS 1.2 negotiation, but going through the Gateway forces TLS 1.0 negotiation. Attempt to use the Gateway from the Win7 computerĥ. On a Windows 7 computer, enable TLS 1.2 for RDP by installing KB3080079Ĥ. We have installed the update on the Windows 7 clients,, however this is still not working.ģ.

Windows 8 and 10 PCs can still connect to the remote desktop server through the remoteĭesktop gateway, however Windows 7 clients just won't connect anymore. We have remote desktop gateway installed on a Windows 2012 R2 server and disabled TLS 1.0.

We have a requirement to disable TLS 1.0 to meet PCI compliance.

Test tls 1.2 windows 7