How to Enable TLS 1.2 on Windows 10

TLS 1.2 is already enabled by default on Windows 10, and modern browsers like Chrome, Edge, and Firefox use it (or TLS 1.3) automatically. If an app or website still says TLS 1.2 is required, check three places: Internet Options (press Windows + R, type inetcpl.cpl, open the Advanced tab, and make sure Use TLS 1.2 is checked), the Schannel registry keys in case someone disabled it, and the .NET Framework settings used by older business apps.

Here’s how to check and enable TLS 1.2 in each place. Back up the registry before editing it.

Where TLS 1.2 settings live

What’s affected Where to enable it
Legacy Internet Explorer mode and apps that use WinINet Internet Options > Advanced
Windows system-wide (Schannel) Registry: SCHANNEL\Protocols\TLS 1.2
Older .NET Framework apps Registry: .NETFramework keys
Chrome, Edge, Firefox Built in. Just keep the browser updated.

Does Windows 10 support TLS 1.3?

Modern browsers support TLS 1.3 on Windows 10 using their own security libraries. Windows’ built-in TLS 1.3 support is mainly in Windows 11 and Windows Server 2022 and later.

Method 1: Internet Options

  1. Press Windows + R, type inetcpl.cpl, and press Enter.
  2. Click the Advanced tab.
  3. Scroll to the Security section and check Use TLS 1.2. Also check Use TLS 1.3 if it’s listed.
  4. For better security, uncheck Use SSL 3.0, Use TLS 1.0, and Use TLS 1.1, unless an old internal site needs them.
  5. Click Apply and OK, then restart the app.

Should I disable TLS 1.0 and 1.1?

Generally yes. They’re outdated, and major browsers no longer use them. Keep them only if an old internal system truly requires them.

Windows Internet Options Advanced tab with the Use TLS 1.2 checkbox checked and highlighted
(1) Check Use TLS 1.2 in the Security section, then (2) click Apply. (Illustration)

Method 2: Check the Schannel registry keys

These keys don’t exist by default, which means TLS 1.2 is on. If they exist with the wrong values, TLS 1.2 may be disabled.

  1. Press Windows + R, type regedit, and press Enter.
  2. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols.
  3. If you see a TLS 1.2 key, open its Client and Server subkeys.
  4. Make sure Enabled is 1 and DisabledByDefault is 0 (both DWORD values). If you need to create them, right-click, choose New > DWORD (32-bit) Value, and set the values.
  5. Restart the PC.

Method 3: Enable TLS 1.2 for .NET Framework apps

Older apps built on .NET Framework 4.x may try to use TLS 1.0 unless told otherwise. Add these DWORD values, set to 1:

  • SchUseStrongCrypto and SystemDefaultTlsVersions in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319
  • The same two values in HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319 (for 32-bit apps on 64-bit Windows)

Restart the app or PC afterward. Some apps also need an update from their vendor to support TLS 1.2.

How to check your TLS version

  • In a browser: In Chrome or Edge, press F12, open the Security tab (in Chrome, it’s in the More tools menu of DevTools), and look at the connection details, which show the TLS version.
  • For a server: See how to check the TLS version on Windows Server.

Still getting TLS errors?

  • Update Windows. Go to Settings > Update & Security > Windows Update. Windows 10 reached end of support in October 2025, so unpatched PCs may run into problems with newer security requirements.
  • Check the date and time. A wrong clock breaks secure connections.
  • Check your antivirus. HTTPS scanning features can interfere.
  • Update the app. Very old apps may not support TLS 1.2 at all.

Managing a server instead? See how to enable TLS 1.2 on Windows Server.