Sorry I didn't get back to you sooner. That is, I did respond, but just discovered that Optimum Online managed to barf my netnews post.
As a later poster mentioned, it's not possible to set the TLS one way for one financial institution and another for a second.
And I take your point that, if one is not having problems, not to mess with that TLS 1.2 setting. (To whoever it was that pointed out that TLS
2.0 does not exist, you're correct, I fumble f Over at beansmart.com, user JohnA states that after the December 11th, 2012 Windows (not Quicken!) update, Web Connect began having problems with secure connections. So that seems to set a start date for all this and is consistent with whatever vague memories I have these days.Second, we have this fellow, at , a Mr. Chen, who went so far as to delve into the system security alerts and tracked it down to failed SSL connections. His solution was to kill of the TLS 1.2. Interestingly, he states that the problems are specific to Internet Explorer and not other web browsers he mucked with. He also mentioned that he found a rumor somewhere that TLS 1.2 can prevent >other< versions of TLS from working. Which would explain what we're seeing.
When I first ran across this, I was fairly sure I was looking at a bug from Intuit. Now I'm not so sure and wonder if this is a Windows core problem. Now, how to get the Windows Security people to fix what they busted?
Ken Becker