getting TLC errors today, just after a "fix"

Hi and thanks for reaching out. My name is William. I'm a Windows technical expert. I'll be happy to help you out today.

Starting with the C++ 2010 runtime, you can repair this by opening appwiz.cpl > locate Microsoft Visual C++ Redistributable 2010 > select Change > Repair. If that does not correct, then uninstall it and reinstall from https://www.microsoft.com/en-us/download/detail...

The TLS errors you are seeing area result of the "handshake" failing between client (you) and server (lets assume McAfee DNS). This happens when both parties are unable to agree on what cipher to use to secure their communication with each other. McAfee does a good job with respect to using only TLS 1.2 so lets assume that protocol has been disabled.

To address the TLS issue, run inetcpl.cpl to open Internet Options > go to the Advanced tab > scroll down to Security sections > make sure at least TLS 1.2 is checked.

If you are still having issue afterwards, then open regedit.exe > navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL > right-click SCHANNEL > select export > save the file > right-click the file > select Edit > paste the output in a reply.

I uninstalled MS11-21, the security update to VS C++ 2010. and then I put it back in as I was still getting those TLC errors.  However, I am no longer getting DNS errors to McAfee but that might be because the TLC errors prevent or masks the DNS error (just a guess)

1.2 is enabled

schannel info txt file

You are seeing the TLS errors because you or a program has enabled TLS logging via:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL]
"EventLogging"=dword:00000001

You can delete the DWORD value EventLogging to stop these events from appearing. A restart is required after making this change.

Additionally, it looks like you specifically (or a program) has enabled support for all cipher suites, some of which have been deprecated. That means your computer will try to negotiate with any outbound connection hosts using the deprecated ciphers, which would also cause an uptick in TLS event errors since each rejected cipher will illicit an event. For the most part, you can usually get by with TLS 1.2 enabled since that is standard today (you may encounter a few legacy sites that are still using 1.1.)

[EDIT]  Setting the log to 0 simply stopped reporting the errors.

Temporarily I fixed the problem by using revo pro uninstaller to complete remove McAfee LiveSave.  It was unable t connect to its DNS servers as it seems the handshaking i snot working.

McAfee needs to go back in. I looked here

and also will try to fix the problem with McAfee help.