Deprecating TLS 1.0 and 1.1 on

Karan Nandwani


co-authored by Scott Bommarito

At Microsoft, using the latest and secure encryption techniques is very important to us to ensure the security and privacy of our customers. TLS 1.0 and TLS 1.1, released in 1999 and 2006 respectively, are known to be vulnerable to a number of attacks including POODLE and BEAST. In the past, we removed support for SSL 3 because it was also vulnerable to attacks. For those reasons, will be removing support for TLS 1.0 and 1.1. This means that you will no longer be able to restore packages, upload packages, or browse using these outdated security protocols. The vast majority of requests that we receive using these protocols are to our deprecated V2 API, which was replaced by our V3 API in 2015. To be ready for this transition, ensure that your systems support TLS 1.2 or higher. will remove support for TLS 1.0 and 1.1 in April, 2020

We realize adapting to change can take time, and we want to share our plans early. To help minimize the number of affected users, we plan to make this change in two stages:

  1. February 2020: Temporarily remove support for TLS 1.0/1.1 in 3 timezones, for 4 hours each, to ensure overlap with normal working hours across the globe
  2. April 2020: Permanently remove support for TLS 1.0/1.1

We hope that the first stage will help you identify systems that may be affected and will give you an opportunity to take action before we permanently remove support for TLS 1.0/1.1 in April, 2020. We will share more specifics, and send out reminders as we get closer.

Ensuring your system uses TLS 1.2

Operating Systems


When browsing the website, ensure that you are using the latest version of your web browser. Chrome, Edge, Internet Explorer, Firefox, and Safari have all committed to deprecating TLS 1.0 and 1.1, and the latest versions of each support TLS 1.2.

NuGet clients and PowerShell

We recommend upgrading to the latest NuGet clients (nuget.exe, dotnet.exe, the Package Manager UI in Visual Studio, Visual Studio for Mac, etc)** as well as updating your builds to use our V3 API instead of the V2 API. We’ve added many features and made many performance and reliability fixes over the years that will improve your development process. The latest versions of our clients default to your operating system’s default version of TLS, which should be TLS 1.2.

Versions of nuget.exe older than 3.4.4, however, may default to using TLS 1.0. Additionally, PowerShell also defaults to TLS 1.0. This can be fixed by changing your .NET Framework default TLS version, which is configured in your registry keys:

    reg add HKLM\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 /v SystemDefaultTlsVersions /t REG_DWORD /d 1 /f /reg:64
    reg add HKLM\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 /v SystemDefaultTlsVersions /t REG_DWORD /d 1 /f /reg:32

If you are using PowerShell and are writing a custom script but cannot edit your system’s registry keys, you can also set your TLS settings using ServicePointManager.SecurityProtocol:

[Net.ServicePointManager]::SecurityProtocol = [Net.ServicePointManager]::SecurityProtocol -bOR [Net.SecurityProtocolType]::Tls12

.NET apps

If you interact with our APIs using your own app, consider upgrading to .NET Core or .NET Framework 4.7.2 or higher. This will ensure that your app defaults to using your operating system’s default TLS version. Alternatively, you can also set your TLS settings using ServicePointManager.SecurityProtocol:

    ServicePointManager.SecurityProtocol |= SecurityProtocolType.Tls12;

Take note that your app will ignore your operating system’s TLS settings if you set ServicePointManager.SecurityProtocol directly. If you explicitly disable TLS 1.2, your app will not use it. It is recommended that you do not set ServicePointManager.SecurityProtocol unless you cannot upgrade your .NET version.


If none of the above steps work and you are still having issues with TLS 1.0/1.1, there may be some other settings on your system that are preventing TLS 1.2 from being used. Here are links to additional resources on how to ensure TLS 1.2+ readiness:


We are working to make this transition as smooth as we can. If you have any issues in this process, feel free to reach out to our Twitter handle, @nuget or email support at


Comments are closed.