XPCOM problem ONLY with ESET Internet Security protected browsing
I can use firefox just fine (win10 home, v2004, os build 19041.1415)- I only get the XPCOM error when trying to open the Eset protected browsing window (for banking and protection). This has not happened before when using/updating Firefox and only just happened when I updated Firefox today to 96.0.2.
I've been browsing the XPCOM queries and have tried the basic reinstall (deleting program folders prior to installing) with no luck, but so far but wanted some clarity prior to trying other things-
Some of the answers here point out that security software can block the folder access when Firefox attempts updates/installs. I attempted an install with Eset paused, but no change. On another computer, a similar problem - a firefox error message occurs when trying to run the Eset protected browsing window, so attempted the same "program folder delete>reinstall" method, only now when clicking the Eset window, it just gives the loading symbol then nothing happens. Again- Firefox also works fine on that computer as well save for the same protected window usage. Not the same error, but still similar enough to think it's related.
Is a safe mode firefox install the next step forward? Should firefox be uninstalled prior to doing so? (Not just deleting the program folders via file explorer, but an actual uninstall process). Or is this something that should be breached with Eset tech support (beyond just pausing the internet protection and functionality, should it be uninstalled prior to firefox reinstall and than installed again afterwards)?
Please advise and thank you in advance!
Tất cả các câu trả lời (3)
I don't want to dampen your spirit of adventure in trying to sort out this seeming incompatibility, but would it work to use Firefox normally and have ESET sandbox one of your other browsers instead? Otherwise, I do think you should ask ESET if they know of this issue and what causes it.
One thought is: it's preferable to let Firefox manage its system permissions rather than set Firefox to run with Administrator privileges. I don't know whether that might be a factor.
Hi, thanks for the suggestion- it would simplify matters if I did separate my browser usage, tho I actually don't have any other browsers installed since I've used firefox exclusively for some time now so that would take some getting used to again as well. That being said, I'd still like to explore a fix if possible, and will bring it up with Eset as well to see if they are aware of the issue.
As to the system permissions idea- what and where is the setting I need to change for Firefox to manage on its own? Quick look at the settings page didn't have anything specific to that effect.
Since around Firefox 67-68, Firefox runs with Medium to Low privileges whenever possible. As long as you are not starting Firefox as Administrator or modifying the "UAC" behavior of Windows, then this would not be a factor.