WinHTTP TLS 1.1 and 1.2 support Defaultsecureprotocol

Trying to implement the DefaultSecureProtocol flag for enabling TLS 1.1 and 1.2 in WinHTTP and having success under the location HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp.  However when attempting to apply the same setting A80 or 2688 to the wow6432node location:

HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp

The setting is reverting to A0 as if it is not correct.  I've tried entering it as decimal 2688 and hex A80.  Both are reverting to A0 (10) after rebooting.

Anyone run into this?
JessicaAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

JessicaAuthor Commented:
Nevermind, hidden GPO with invalid settings!
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.