Browser Support • Re: "Couldn't load XPCOM" - Browser is completely bricked.

If in fact the version of mozjs.dll that people have (did someone figure out how to substitute that file in transit and still pass the download check?) does not have any bad code, why not make some minor change to it so that it doesn't trigger any warning, since otherwise you are out of business until Microsoft does something.

It's not that simple. The match is against a compiled binary -- we don't know what detection was used for it, and even if we did, we can't control what assembled machine code the compiler spits out, precisely, or how to manipulate it into avoiding certain markers.

I'm also unhappy that Microsoft is apparently ignoring the fact it is digitally code-signed (through their own Azure infra, to boot!) for which they are actually getting my money (and signing has been primarily to avoid being constantly flagged by their SmartScreen...).

Also, we aren't "out of business until Microsoft does something", since you can just make an exception as a user. Defender gives notifications so people can immediately see it was Defender doing something wrong and allowing them to take action -- so it's not like the topic title here says that it just "bricks" after update and there are no pointers why.