{"id":13240,"date":"2020-02-19T00:11:39","date_gmt":"2020-02-18T23:11:39","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=13240"},"modified":"2024-10-05T20:53:07","modified_gmt":"2024-10-05T18:53:07","slug":"firefox-73-0-1-with-0patch-and-g-data-fix","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2020\/02\/19\/firefox-73-0-1-with-0patch-and-g-data-fix\/","title":{"rendered":"Firefox 73.0.1 with 0patch- and G-DATA fix"},"content":{"rendered":"

\"Mozilla\"<\/a>[German<\/a>]Mozilla's developers have just released (February 18, 2020) version 73.0 .1 of the Firefox browser. This is a maintenance update for the browser that fixes the conflict with 0patch agents. <\/p>\n

<\/p>\n

The 0patch issue<\/h2>\n

\"\"I had the topic on my agenda for a few days because it concerned myself, but I have not yet got around to preparing it. There were several reader hints by mail or in the German comments here<\/a> and (very cryptic here<\/a>). <\/p>\n

The problem: On my system I had installed the 0patch agent for testing. Later I faced the problem, that the Firefox browser won't work anymore – the browser could get started in version 72.x, but I was not able to access web pages anymore. <\/p>\n

Unfortunately, the time between installing 0patch and finding that Firefox was causing problems was too far apart. I also covered at that time the Internet Explorer 0-day exploit story and tried the workaround recommended by Microsoft, which disables jscript.dll. As a result, I could not establish a association between the Firefox error and the 0patch installation. <\/p>\n

When updating to Firefox 73 I found that it crashed immediately, but could not find anything when searching the web. At some point I uninstalled the 0patch agent and later reinstalled Firefox 73 on my system as a portable application. And suddenly the browser was running again.<\/p>\n

One day later I came across this explanation<\/a> by Mitja Kolsek, who explains the technical background of the problem. Mitja also provided a workaround on how to fix the collision between 0patch agents and Firefox that caused the malfunction. I had pointed out the issue in comments like here to German readers. But this workaround is now superfluous, since Firefox in version 73.0.1 has solved the problem.  <\/p>\n

Firefox 73.0.1 fixes<\/h2>\n

Blog reader Ralf pointed out in this German comment (thanks for that) the update to Firefox 73.0.1. Also this comment<\/a> from EP on the topic informed me about the update (thanks also). In the release notes<\/a> the following bug fixes are listed:<\/p>\n