Windows 10: Deprecating Legacy TLS Versions in Google Chrome

Brink · Oct 1, 2019

Last October we announced our plans to remove support for TLS 1.0 and 1.1 in Chrome 81. In this post we’re announcing a pre-removal phase in which we’ll introduce a gentler warning UI, and previewing the UI that we’ll use to block TLS 1.0 and 1.1 in Chrome 81. Site administrators should immediately enable TLS 1.2 or later to avoid these UI treatments.

While legacy TLS usage has decreased, we still see over 0.5% of page loads using these deprecated versions. To ease the transition to the final removal of support and to reduce user surprise when outdated configurations stop working, Chrome will discontinue support in two steps: first, showing new security indicators for sites using these deprecated versions; and second, blocking connections to these sites with a full page warning.

Pre-removal warning

Starting January 13, 2020, for Chrome 79 and higher, we will show a “Not Secure” indicator for sites using TLS 1.0 or 1.1 to alert users to the outdated configuration:

The new security indicator and connection security information that will be shown to users who visit a site using TLS 1.0 or 1.1 starting in January 2020.

When a site uses TLS 1.0 or 1.1, Chrome will downgrade the security indicator and show a more detailed warning message inside Page Info. This change will not block users from visiting or using the page, but will alert them to the downgraded security of the connection.

Note that Chrome already shows warnings in DevTools to alert site owners that they are using a deprecated version of TLS.

Removal UI

In Chrome 81, which will be released to the Stable channel in March 2020, we will begin blocking connections to sites using TLS 1.0 or 1.1, showing a full page interstitial warning:

The full screen interstitial warning that will be shown to users who visit a site using TLS 1.0 or 1.1 starting in Chrome 81. Final warning subject to change.

Site administrators should immediately enable TLS 1.2 or later. Depending on server software (such as Apache or nginx), this may be a configuration change or a software update. Additionally, we encourage all sites to revisit their TLS configuration. In our original announcement, we outlined our current criteria for modern TLS.

Enterprise deployments can preview the final removal of TLS 1.0 and 1.1 by setting the SSLVersionMin policy to “tls1.2”. This will prevent clients from connecting over these protocol versions. For enterprise deployments that need more time, this same policy can be used to re-enable TLS 1.0 or TLS 1.1 and disable the warning UIs until January 2021.

Posted by Chris Thompson, Chrome security team
Click to expand...

Source: Chromium Blog: Chrome UI for Deprecating Legacy TLS Versions

:)

Xylee Del · Oct 1, 2019

problem uninstalling google chrome

Hi,

Since you already uninstalled Google Chrome using the Programs and Features, Google notifications may still be running in the background processes. We suggest that you follow these steps on how to end the Google Chrome process:

On your keyboard, press Ctrl+Alt+Delete.

Select Task Manager.

Under Processes, locate Google Notifications or Google Chrome.

Right click on them and select End Task.

Double check under Programs and Features if Google Chrome is completely gone.

Let us know if these steps worked.

Ashish Sondhi · Oct 1, 2019

Windows 10 and Google chrome problems

Hello,

Thank you for your interest in Windows 10.

As you have mentioned that now you rolled back to windows 7 ultimate.I would suggest you to follow the steps given below and check.

Uninstall and reinstall Google Chrome and check

To uninstall and reinstall Google Chrome follow the steps given below.

Press start button.

Select Control Panel.

In Control Panel , Click on
Programs

Then Click on Programs and features.

Select Google Chrome and Click Uninstall button

Uninstall Chrome prompt dialog appears and the further uninstallation process continues if you click uninstall button. Once Google Chrome gets uninstalled, you can download and install Google Chrome from its official website,
and check if issue persists.

If issue still didn’t get resolved by the above mentioned steps, I would also suggest you to post the query in Google support forums for more help.

Get help from the Chrome community:
Google Chrome Help

Hope this helps, if you need further assistance on Windows let us know we will be glad to help.

curatia · Oct 1, 2019

Microsoft Edge TLS Security

After trying everything (not a lot of steps) listed in the Microsoft Edge support site, I did a wider search and found this very simple youtube video that fixed it immediately:

For those who prefer not to click links the steps are simple:

1. Click in the Cortana search bar next to the Win 10 Start button

2. Type internet options

3. Select internet options (control panel) from the list

4. Click on the advanced tab

5. Scroll down to the security section

6. Make sure the following are all clicked:
Use SSL 3.0
Use TLS 1.0
Use TLS 1.1
Use TLS 1.2

7. Click apply

8. Refresh the page that was giving the error and it should now connect.

Hope this helps, it was a 30 second fix after hours of pounding my head against the error with the Support site suggestions.

Windows 10: Deprecating Legacy TLS Versions in Google Chrome

Deprecating Legacy TLS Versions in Google Chrome

Deprecating Legacy TLS Versions in Google Chrome

Deprecating Legacy TLS Versions in Google Chrome

Deprecating Legacy TLS Versions in Google Chrome - Similar Threads - Deprecating Legacy TLS

Deprecation of legacy Microsoft LAPS product

Deprecation of legacy Microsoft LAPS product

Google Chrome (currently version 88)

Google Chrome (currently version 88)

How to enable TLS 1.1 or TLS 1.2 in Chrome?

Microsoft and DigiCert to begin deprecating Symantec TLS certificates

Google Chrome SWReporter Is Back In Version 68.0.3440.106

Current Version of Google Chrome

Deprecation of SHA-1 for SSL/TLS Certificates in Microsoft Edge & IE11