How to Check the TLS Version on Windows Server

Windows Server controls TLS through the SCHANNEL security provider, so the quickest check is in the registry. Open Registry Editor and go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols. Under each version (for example, TLS 1.2\Server), Enabled = 1 means on and 0 means off. If a key doesn’t exist, the Windows default for your server version applies. To confirm, test the server from another machine with openssl s_client -connect server:443 -tls1_2.

Registry Editor showing the SCHANNEL Protocols TLS 1.2 Server key selected and the Enabled value set to 1 highlighted
(1) The TLS 1.2 Server key under SCHANNEL Protocols; (2) Enabled = 1 means the server accepts TLS 1.2 connections.

Method 1: Check the SCHANNEL Registry Settings

  1. Press Windows + R, type regedit, and press Enter.
  2. Navigate to HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols.
  3. Expand each protocol (SSL 3.0, TLS 1.0, TLS 1.1, TLS 1.2, TLS 1.3) and check the Server and Client subkeys:
    • Enabled = 1 (on) or 0 (off)
    • DisabledByDefault = 1 means applications must explicitly request that version

Check the same thing with PowerShell:

Get-ChildItem 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols' -Recurse | Get-ItemProperty | Select-Object PSPath, Enabled, DisabledByDefault

Method 2: Test What the Server Actually Accepts

Registry values show configuration; a live test shows reality. From another computer:

  • OpenSSL: openssl s_client -connect server.example.com:443 -tls1_2. A certificate chain and “Protocol : TLSv1.2” means it works; a handshake failure means it’s disabled. Repeat with -tls1_1, -tls1, or -tls1_3.
  • Nmap: nmap --script ssl-enum-ciphers -p 443 server.example.com lists every supported protocol and cipher.
  • Online scanners: public SSL test sites can grade internet-facing servers.

Need OpenSSL on Windows? See installing OpenSSL.

Method 3: Check Client-Side .NET Settings

Older .NET Framework applications may not use TLS 1.2 unless configured. In PowerShell, [Net.ServicePointManager]::SecurityProtocol shows what the current session uses. System-wide .NET behavior is controlled by SchUseStrongCrypto and SystemDefaultTlsVersions values under HKLM\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 (and the WOW6432Node equivalent).

Default TLS Support by Windows Server Version

Version TLS 1.2 TLS 1.3 Notes
Windows Server 2012 R2 Supported No Out of support; TLS 1.0/1.1 on by default
Windows Server 2016 / 2019 Enabled No TLS 1.0/1.1 enabled unless disabled
Windows Server 2022 Enabled Supported First Windows Server with TLS 1.3
Windows Server 2025 Enabled Supported Older protocols increasingly disabled by default

Defaults can change with updates, so verify with a live test.

Changing TLS Settings

To enable or disable a version, create or edit the Enabled and DisabledByDefault DWORD values under the protocol’s Server and Client keys, then restart the server. Test in a lab first: disabling TLS 1.0/1.1 can break older clients, SQL Server connections, or legacy applications. See enabling TLS 1.2 on Windows Server.