The AchieVer Posted February 1, 2019 Share Posted February 1, 2019 Mozilla Pulls Firefox 65 Update for Windows Due to Antivirus Issue Mozilla has decided to pull the automatic update to Firefox 65 for its Windows users after discovering an issue with certain antivirus products that breaks down websites. After installing Firefox 65 on Windows, some websites can no longer be loaded in the browser, and users who posted in this Bugzilla thread say they are being provided with an error reading "Your connection is not secure" "SEC_ERROR_UNKNOWN_ISSUER". Several users have confirmed that this problem is experienced with absolutely all websites they try to visit, though it appears that the number of pages affected by the problem varies from user to user. A report from TechDows reveals that the problem is encountered due to an issue with Avast or AVGantivirus, and Mozilla engineer Ryan VanderMeulen confirmed this is indeed the case.Automatic update pulledAs a result, to prevent the issue from hitting more devices, Mozilla has decided to pull the automatic update to Firefox 65 on Windows – note that the browser remains available for download as a stand-alone installer. “Our users updating to Firefox 65 with Avast & AVG installed have been encountering this error with regularity since we launched on Tuesday. We've temporarily halted all automatic updates on Windows to avoid further exacerbating the issue,” VanderMeulen explained. A workaround does exist, and users are recommended to open the settings screen of their antivirus and disable HTTPS scanning. The cited source indicates that some Firefox users may also experience similar issues with Kaspersky, though confirmation from Mozilla in this regard isn’t available just yet. By the looks of things, the culprit is the antivirus software trying to use their own certificates in Firefox when loading websites, so updates to the security products will probably resolve this. Mozilla and antivirus vendors are already investigating the problem, so it shouldn’t take long before a fix is available. Source Link to comment Share on other sites More sharing options...
Karlston Posted February 1, 2019 Share Posted February 1, 2019 Which is why dot-zero versions should be avoided and users should wait for the next minor update to fix any initial problems. There's no prize for having the latest version the instant it's released, though many think so. Waiting for 65.0.1 here... Link to comment Share on other sites More sharing options...
SPECTRUM Posted February 1, 2019 Share Posted February 1, 2019 19 minutes ago, Karlston said: There's no prize for having the latest version the instant it's released, though many think so. prize was needed for version 65 due it fixed few critical and important security issues: https://www.mozilla.org/en-US/security/advisories/mfsa2019-01/ Link to comment Share on other sites More sharing options...
Karlston Posted February 1, 2019 Share Posted February 1, 2019 12 minutes ago, SPECTRUM said: prize was needed for version 65 due it fixed few critical and important security issues: https://www.mozilla.org/en-US/security/advisories/mfsa2019-01/ Perhaps, but Avast/AVG users also got a second prize. Link to comment Share on other sites More sharing options...
leland Posted February 1, 2019 Share Posted February 1, 2019 Not the first time I have seen this kind of issue and it won't be the last. That is why I always download the updates manually so I can downgrade if needed. I find anything that tries to use it's own certificate can break things.... Link to comment Share on other sites More sharing options...
luisam Posted February 1, 2019 Share Posted February 1, 2019 8 hours ago, The AchieVer said: error reading "Your connection is not secure" "SEC_ERROR_UNKNOWN_ISSUER". After I'd updated to 65 started getting those strange messages, most notable trying to open google.com and specifically gmail; also computer returned that it had no connection to open https://web.whatsapp.com. Since then I've been using Google Chrome, expecting 65.0.1 So I learned that the bug is somehow related to Avast Antivirus. I've been looking for the option to disable HTTPS scanning in the settings screen of the antivirus but couldn't find it. Just to test, I disabled Avast for 10 minutes and it seemed to solve the issue. Then since I re-enabled Avast, it continued working, even after RESTARTING Windows 10. Apparently everything is well now, still running 65! Link to comment Share on other sites More sharing options...
debebee Posted February 5, 2019 Share Posted February 5, 2019 https://www.ghacks.net/2019/02/01/mozilla-halts-firefox-65-distribution-on-windows/ So for the sake of sanity should we roll back to the version before v65.0? Link to comment Share on other sites More sharing options...
Karlston Posted February 5, 2019 Share Posted February 5, 2019 1 hour ago, teodz1984 said: So for the sake of sanity should we roll back to the version before v65.0? I'd suggest if you're not having any problems with 65.0 to keep using it, but get 65.0.1 when it's released. To fix the problem with their products, Avast has rolled out an update that disables HTTPS scanning. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.