Hey BarnStormer, sure, I added this context to the bug comments!It seems that the issue should be tackeld by Microsoft and not Mozilla. I was not able to do a proper regression analysis, since the detection also persists with older versions of Firefo...
Mozilla is looking into the issue. They need a regression analysis of an affected FF. I will be able to deliver one end of the week, but if one also wants to contribute one earlier, please go ahead and upload it to the bugzilla report: https://bugzil...
Sounds plausible! By the way, I also have the error on Windows 11, so it's not Windows 10 only.Is there a way to escalate the issue to Mozilla? I haven't had a point of contact with Mozilla development regarding bugs and such, but I think the develop...
I agree, but I am still wondering what the root cause is. I fixed the problem with the method that JackB described, but what was the original cause? I see four possible explanations:1) It's a false positive,1.1 caused by Windows Defenders wrong detec...
