.NET Framework 3.5 and TLS 1.2

I currently have a web application that uses the .NET 3.5 framework and I am wondering if it will be compatible with TLS 1.2. No where in our code are we dictating TLS version. This is a legacy application and recompiling is not on the table right now. I am not finding much info on whether you can or cannot, but I was under the impression that compatibility is more dependent on the OS version. It looks like the minimum is 2008 R2. The goal is to get paypal to communicate properly come July 1st.


Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or not), leave a comment & I’ll get back to you as soon as possible.

Method 1

As was mentioned .net 3.5.1 DOES now support TLS 1.2; but you don’t need the registry changes mentioned by @Paulina’s answer.

I’m using VS 2008 with .net 3.5.30729.4926. All I had to do was:

Add imports:

Imports System.Security.Authentication
Imports System.Net

Add this to my code (C#):
public const SslProtocols _Tls12 = (SslProtocols)0x00000C00;
public const SecurityProtocolType Tls12 = (SecurityProtocolType)_Tls12;
ServicePointManager.SecurityProtocol = Tls12

VB.net version:
Const _Tls12 As SslProtocols = DirectCast(&HC00, SslProtocols)
Const Tls12 As SecurityProtocolType = DirectCast(_Tls12, SecurityProtocolType)
ServicePointManager.SecurityProtocol = Tls12

Culled from: https://support.microsoft.com/en-us/help/3154518/support-for-tls-system-default-versions-included-in-the-.net-framework Note: by defining the const in my code I could ignore everything else in the article including the registry edits and cs files.

Method 2

As you can see from the docs, TLS 1.2 is not in the enumeration for SslProtocols, it was added to the enum in .NET 4.5 (thanks @orhun).

There is no workaround for TLS 1.2 compatibility on .NET 3.5.

Unfortunately you will have to upgrade to .NET 4.5 or later to get TLS 1.2 compatibility.

EDIT 10/11/17

My above answer is no longer accurate. In May of 2017, Microsoft released a package to allow TLS 1.2 in .NET 3.5.1.

Method 3

You can make TLS 1.2 work with Framework 3.5.

Microsoft have released update for it.

Follow this steps

  1. Install Support update for TLS in Framework 3.5 from here:


  1. Go to registry
    • Type regedit in start
    • Right click and run as administrator
    • Navigate to registry keys


  • Right click on the registry key and click Export
  • Name the file and save it with .reg extension (keep them as your backup in case you need to restore them)
    1. Add entry to registry keys
  • Make copy of the saved files and rename them
  • Open with text editor and add following text to each key (this is for 64-bit operating system) and save changes (for 32-bit operating system look at the info in the link)


  • Double click on the file and click Yes on the window to allow changes
    1. Add code to your project as specified in the link – Developer Guidance section

I applied this solution and it worked for me.

Method 4

I have just verified that this is all you need in your code to enable support for TLS 1.2 in .NET Framework 3.5:

ServicePointManager.SecurityProtocol = (SecurityProtocolType)3072;

I verified by creating a unit test in .NET Framework 3.5 that fetches this HTML page: https://clienttest.ssllabs.com:8443/ssltest/viewMyClient.html

Without the above line, the TLS test page says that I’m using TLS 1.0, which is .NET 3.5’s default.

TLS 1.1 is deprecated along with 1.0, but if you want to enable it as well, you can use this line instead (not recommended):

ServicePointManager.SecurityProtocol = (SecurityProtocolType)3072 | (SecurityProtocolType)768;

The “magic” values 3072 and 768 are taken from .NET Framework 4.5’s version of the SecurityProtocolType enum:

  • 192: Specifies the TLS 1.0 security protocol
  • 768: Specifies the TLS 1.1 security protocol
  • 3072: Specifies the TLS 1.2 security protocol

I’m not sure whether the server running this code has to have .NET Framework 4.5 runtime installed or not, but it could be so.

Method 5

I am having the same problem as the OP – old .net 3.5 code having to connect to an external service using tls 1.2.

As mentioned in the accepted answer there is a patch for tls1.2 released by MS.

After this they have released a patch for Server 2008 (not R2):

So it should be possible to upgrade to tls 1.2 while still running server 2008.

All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

0 0 votes
Article Rating
Notify of

Inline Feedbacks
View all comments
Would love your thoughts, please comment.x