TLS 1.1/1.2 and Vista issue (no options)

[Chociu]

Hi,

I applied all updates up to April 2017. I do have IE9 installed. I have also installed KB4019276 and the latest IE9 cumulative update.

On Vista Home Premium x64, there seems no options for TLS 1.1 and 1.2 even after deleting or blanking out the OSVersion string, and apparently the only way to the enable is use group policy (which obviously isn't included). I did reboot after and nothing happened.

XP x86 with KB4019276 and cumulative IE8 update works fine on a different machine.

any help would be appreciated.

Edited December 3, 2018 by Chociu

[mike_shupp]

 

Click on START.  Enter REGEDIT in the box.  In the Registry, seek out "Software\Microsoft\Internet Explorer" and delete any entries to "OSVersion 3.1.6.0"   . Then save and exit and start up the browser. Go to Internet Options, then hit Advanced Tab, slide down to Security.   Make "Use SSL 1.0" thru "Use TLS1.0" boxes blank, check "Use TLS 1.1" and TLS 1.2.   Save and restart the browser.

These are security settings used by websites over time. SSL got beaten by malware and thus has fallen out of use. TLS 1.0 was the default for Vista and others for a long while (it goes with those "http//" URLs), but has been obsoleted by TLS 1.1 and now TLS 1.2 (all those "https//" URLs that Vista couldn't open).    

You may find that options for 32-bit and 64-bit IE9 are different,  that TLS 1.1 and 1.2 appear for one browser version but not the other.  Alter the one that you can, and try to remember to use that browser.  Another happy note:  TLS 1.3 is due to appear shortly; I've no ideas as to whether Microsoft will fit that into IE9 (or IE11).   There are a few other browsers than IR9 that work with Vista fortunately.

[Chociu]

I'm probably looking at the wrong browser bits setting then for my machine >_> I'll give it a try tomorrow, I am currently very tired ~_~

[WinClient5270]

Since you're running 64-bit Vista, be sure to go to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO and delete the 'OSVersion' values in the 'TLS1.1' and 'TLS1.2' keys (folders).

Edited July 26, 2020 by WinClient5270

[Chociu]

@WinClient5270 Cool, thanks for that: I wasn't aware that I needed to change a different part for x64 Windows, it's not said in the tutorial. 

Edited December 4, 2018 by Chociu

[jaclaz]

As often happens a surely accidental little mistake is (has been, and will be) perpetuated forever until someone actually corrects it EXPLICITLY.

This:

On 12/4/2018 at 4:32 AM, WinClient5270 said:

Since you're running 64-bit Vista, be sure to go to HKEY_LOCAL_MACHINE>Software>Wow6432Node>CRYPTO and delete the 'OSVersion' values in the 'TLS1.1' and 'TLS1.2' keys (folders).

is WRONG.

The correct path is:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\TLS1.1
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\TLS1.2

See this updated thread:

https://msfn.org/board/topic/181705-solving-vistas-lack-of-tls-11-or-12/

And this reference one:
https://www.vistax64.com/threads/ie9-last-supported-browser-for-vista.305228/

jaclaz

[WinClient5270]

On 7/25/2020 at 11:50 AM, jaclaz said:

As often happens a surely accidental little mistake is (has been, and will be) perpetuated forever until someone actually corrects it EXPLICITLY.

This:

is WRONG.

The correct path is:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\TLS1.1
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\TLS1.2

See this updated thread:

https://msfn.org/board/topic/181705-solving-vistas-lack-of-tls-11-or-12/

And this reference one:
https://www.vistax64.com/threads/ie9-last-supported-browser-for-vista.305228/

jaclaz

Oops! Sorry for the mistake. I'm only human I will fix the original post so that others that run across it aren't thrown off by the typo.

[jaclaz]

23 hours ago, WinClient5270 said:

Oops! Sorry for the mistake. I'm only human I will fix the original post so that others that run across it aren't thrown off by the typo.

Yep , don't worry, no harm was done.

jaclaz