ESET Chromium Issues

B

BigDonut67

New member
Hello. After the most recent ESET Home Security (the paid version) program update, attempting to open any Chromium browsers inside a sandbox causes a Werfault.exe error from Chrome (and Edge) in the process list of the sandbox. I believe it was something to do with a hooking issue, going by the error codes and documentation about them online (I think they were 2301, 2303, and 2304). I also had "EnableWin32kHooks=y" in the template ini, but that didn't change anything. I tried many fixes listed online, none of which worked. I finally decided to uninstall ESET today and see what would happen, and suddenly it started working fine again. I had the NOD32 compatibility template enabled and disabled during my tests (despite the fact I'm not using NOD32), and Sandboxie Plus worked fine until the most recent ESET application update. My guess is Sandboxie just needs to be updated to fix this conflict. I tried disabling the web addons and whatnot, to no avail. All the issues went away once I uninstalled ESET.

I'm on the most recent Windows version (not part of the Insider program), and have Sandboxie Plus up to date.

It's entirely possible that I'm just dumb and have no idea how to make exceptions in the right category to exclude Sandboxie in ESET, so please do let me know if that's the case, lol. 😂 I'm just looking for any fix at this point, as I prefer my subscription for ESET not be wasted. I can try to provide more info if needed, though I forget a lot of what I tried because I did so many different things. Hopefully my description of this issue helps it get fixed.

Thanks. 👍
 
I believe I already had it set up to not use the custom logon token, if that's what that setting would change. If that's not what that does, I can try it out and see what happens.

Chrome wouldn't even open and just crashed on open every time, with the WerFault.exe process popping up in the sandbox process list. I wasn't able to attempt loading a page as a result.
 
Last edited:
Hey. Just wanted to report back that I believe the issue has been fixed. I will be sure to post again if it crops up again in the future.

Thank you for the swift response and assistance. :)
 
I had the problem come back, but was able to fix it by disabling the "Safe Banking and Browsing" feature of ESET. Please let me know if you guys ever find or develop a solution that doesn't require doing that. 👍
 
You must log in or register to reply here.
Back
Top