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.
Applications 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 is because the definition of this flag doesn’t include these applications and services.
This update adds support for DefaultSecureProtocols registry entry that allows the system administrator to specify which SSL protocols should be used when the WINHTTP_OPTION_SECURE_PROTOCOLS flag is used.
This can allow certain applications that were built to use the WinHTTP default flag to be able to leverage the newer TLS 1.2 or TLS 1.1 protocols natively without any need for updates to the application.
This is the case for some Microsoft Office applications when they open documents from a SharePoint library or a Web Folder, IP-HTTPS tunnels for DirectAccess connectivity, and other applications by using technologies such as WebClient by using WebDav, WinRM, and others.
This update requires that the Secure Channel (Schannel) component in Windows 7 be configured to support TLS 1.1 and 1.2. As these protocol versions are not enabled by default in Windows 7, you must configure the registry settings to ensure Office applications can successfully use TLS 1.1 and 1.2.
This update will not change the behavior of applications that are manually setting the secure protocols instead of passing the default flag.
Important If you install a language pack after you install this update, you must reinstall this update. Therefore, we recommend that you install any language packs that you need before you install this update. For more information, see Add language packs to Windows.
This 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.
To get the stand-alone package for this update, go to the Microsoft Update Catalog website.
To apply this update, you must install Service Pack 1 for Windows 7 or Windows Server 2008 R2.
There’s no prerequisite to apply this update in Windows Server 2012.
To apply this update, the DefaultSecureProtocols registry subkey must be added.Note To do this, you can add the registry subkey manually or install the “Easy fix” to populate the registry subkey.
You may have to restart the computer after you apply this update.
This update doesn’t replace a previously released update.
Payment Card Industry (PCI) requires TLS 1.1 or TLS 1.2 for compliance.
For more information about the WINHTTP_OPTION_SECURE_PROTOCOLS flag, see Option Flags.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, see How to back up and restore the registry in Windows.
When an application specifies WINHTTP_OPTION_SECURE_PROTOCOLS, the system will check for the DefaultSecureProtocols registry entry and if present override the default protocols specified by WINHTTP_OPTION_SECURE_PROTOCOLS with the protocols specified in the registry entry. If the registry entry is not present, WinHTTP will use the existing operating system defaults for Win WINHTTP_OPTION_SECURE_PROTOCOLS HTTP. These WinHTTP defaults follow the existing precedence rules and are overruled by SCHANNEL disabled protocols and protocols set per application by WinHttpSetOption.
Note The hotfix installer doesn’t add the DefaultSecureProtocols value. The administrator must manually add the entry after determining the override protocols. Or, you can install the “Easy fix” to add the entry automatically.
The DefaultSecureProtocols registry entry can be added in the following path:
On x64-based computers, DefaultSecureProtocols must also be added to the Wow6432Node path:
The registry value is a DWORD bitmap. The value to use is determined by adding the values corresponding to the protocols desired.
The administrator wants to override the default values for WINHTTP_OPTION_SECURE_PROTOCOLS to specify TLS 1.1 and TLS 1.2.
Take the value for TLS 1.1 (0x00000200) and the value for TLS 1.2 (0x00000800), then add them together in calculator (in programmer mode), and the resulting registry value would be 0x00000A00.
To add the DefaultSecureProtocols registry subkey automatically, click here. In the File Download dialog box, click Run or Open, and then follow the steps in the easy fix wizard.
Note In addition to the DefaultSecureProtocols registry subkey, the Easy fix also adds the SecureProtocols at the following location to help enable TLS 1.1 and 1.2 for Internet Explorer.
The SecureProtocols registry entry that has value 0xA80 for enabling TLS 1.1 and 1.2 will be added in the following paths:
Per the TLS-SSL Settings article, for TLS 1.1 and 1.2 to be enabled and negotiated on Windows 7, you MUST create the “DisabledByDefault” entry in the appropriate subkey (Client) and set it to “0”. These subkeys will not be created in the registry since these protocols are disabled by default.
Create the necessary subkeys for TLS 1.1 and 1.2; create the DisabledByDefault DWORD values and set it to 0 in the following locations:
Registry location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\ClientDWORD name: DisabledByDefaultDWORD value: 0
Registry location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\ClientDWORD name: DisabledByDefaultDWORD value: 0
Powered by BetterDocs
@ 2021 Central Plains Computer Service, Inc.