- #How to update companionlink how to
- #How to update companionlink install
- #How to update companionlink pro
- #How to update companionlink windows 8.1
Clicking "check for updates" in the update tab indicated that not even 386 was available, and that 381 (and on yet another system, 375) were up to date! For some unknown reason to me, one of the computers had SSL/TSL scanning off.
#How to update companionlink windows 8.1
Both these systems were running NOD32 9.0.381 (one Windows 8.1 machines, one Win10 machine w/o anniversary update installed). UPDATE: To test further, I went to several computers that have not been turned on since the end of June (the computers belong to my children who are at overnight camp). And again, why only on these two, clearly legitimate, sites? So, there could have been something legitimate going on to prompt the warnings, but it is hard to believe that that the reinstall/downgrade to 9.0.386 and the above warnings are a coincidence.
#How to update companionlink install
Those warnings only began to display after I had to uninstall version 9.0.396 and clean install 9.0.386 (due to the communication error between ESET and Windows detailed in other forum posts both here and on the ESS forum). The warnings have since been banished as far as I can tell, and the websites in question seem to be behaving normally (no decreased functionality thus far).ġ) The domains in question were being blocked by OpenDNS en-masse before the certificate warnings popped up on my system this past week. Also note, that even though ESET did throw up warnings for me this morning about these certificates, OpenDNS did NOT block these domains this morning, which makes me think there is not a direct connection between the OpenDNS blocking and ESET's warnings.Ģ) This morning, I choose - on the two Win7 systems thus far - to "always block" the certificates above when I generated the ESET warning by going to Amazon and CompanionLink. Note: Both these domains are being blocked by OpenDNS due to my catagory settings, in this case, they are being blocked as "Adware." They are not flagged by OpenDNS as botnets, malware, phishing, fraud, etc. Given the relatively low frequency that I go to Amazon or CompanionLink (maybe once a day compared to dozens of times a day to other secure websites), I have to assume that it is not only Amazon and CompanionLink that are generating these requests. What was particularly interesting, is that both were very far down on the last of "number of requests made" going back to early July, but really ramped up in late July through this past week (when ESET started throwing up warnings for Amazon and CompanionLink).īy late July, both were in the number 1 and 2 spots for blocked requests being made.
Both of the domains being flagged in the above certificates showed up in the OpenDNS log. And so far, these are the only two websites that seem to be affected.ġ) I employ OpenDNS (pro/paid version) at the network (router) level, and on a whim, reviewed domains that have been blocked by OpenDNS on my network over the past two months. My date and time are accurate on all systems. This error appeared after uninstalling and reinstalling NOD32 9.0.386 after the update to build 396 caused an error which did not allow Windows to recognize ESET being installed (see my post on this in the forum). This is most certainly an another ESET issue.
#How to update companionlink pro
I have tested this on two Win7圆4 systems running 64-bit Chrome and IE, and a brand new Win10 Pro 圆4 system that is updated with the "anniversary update" with 64-bit Chrome. Rinse and repeat for, but the certificate issuer is different. This warning does *not* pop up while using Firefox. I have reproduced this on two other computers while using Chrome (latest version) and Internet Explorer.
#How to update companionlink how to
If that doesn't help, provide us with instructions how to reproduce that.Ģ) Go to (this is the site with the domain - obviously, Amazon is legit)ģ) Wait for the warning dialogue above to appearĤ) Click block every time you click a link on the page If you are getting a warning about an untrusted certificate when opening or another 100% legit website, make sure that you have your system date set correctly. The other website utilize a valid certificate. As for the domain, it seems to be malware-related according to the information I've found.
0 kommentar(er)
