1-800-691-1991 | 9am - 8pm ET

Secure channel communications stop working after disabling TLS 1.0/1.1

KB ID: 2853
Product: Veeam Backup & Replication
Version: 8.x, 9.x
Published: 2018-12-26
Last Modified: 2020-08-13


After disabling TLS 1.0/1.1, Veeam functionality which utilizes the SCHANNEL security provider, such as license auto-update, license usage reporting and Veeam explorers with remote mounts stop working.
You can see the following error in the Svc.VeeamBackup.log log file and/or in the pop-up error window.
The client and server cannot communicate, because they do not possess a common algorithm



The currently targeted .NET Framework version, 4.5.2, defaults to TLS 1.0 and doesn’t switch automatically to 1.2 when TLS 1.0/1.1 is disabled.


The following registry keys will need to be added on machines where TLS 1.0/1.1 has been disabled to force the usage of TLS 1.2.

Locations: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 and HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319

Name: SchUseStrongCrypto
Value: 1

Name: SystemDefaultTlsVersions
Value: 1

A .reg file is provided by Microsoft that will set these keys to their most safe values:


More information

Microsoft .NET Framework Best practices for TLS

KB ID: 2853
Product: Veeam Backup & Replication
Version: 8.x, 9.x
Published: 2018-12-26
Last Modified: 2020-08-13

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.


error icon

Oops! Something went wrong.

Please go back try again later.