JerryG

Hi Admin and Superusers, I am a long time user and financial supporter of ESET and today i was working on another infected PC and was able to locate the infected file (fyi the file is about 18 months old so not new). I safely moved it to my PC and scanned it with ESET Internet Security and it came up clean. I then uploaded it to Virus total and 51 vendors cited it as being infected INCLUDING ESET-NOD32. I can't understand why if ESET on Virus Total flagged it, why didn't my current updated version on my PC flag it. My PC version: Internet Security 16.0.26.0, Version of detection engine: 27035 (20230407). Thanks In advance J

I can confirm that the issue was fixed with the 1140 update . Thanks @Marcos

Yep that fixed it alright, thanks so much Marcos. Amazes me how you worked that out. For anyone else, you must select Permanently disable Banking and Payment protection for this to work.

Thank you itman, Chrome does run outside sandboxie

Chrome 68 worked fine, but once chrome updated to 69 I started to get 0xC0000005 execution error when trying to run the sandboxed browser in Sandboxie. Other browsers work fine, it is just effecting Chrome. I have gone through disabling and enabling settings in ESET and the only thing that allows chrome.exe to run sandboxed is Disabling ESET Protocol Filtering. A post to the ESET forums got a reply that i could (although not advised) exclude chrome.exe from filtering within ESET ie "You can exclude chrome from protocol filtering as shown here: https://help.eset.com/eis/11.2/en-US/idh_config_epfw_ssl_app.html?idh_config_epfw_content_scan_exclude.html" I tried that too and it didn't work either. Any other ideas

yes i like it too. BTW I am just posting a new problem post that includes what has been tried to fix it.

I excluded everything one by one and it didnt help. I agree with you about running the system without protection, I wont be doing that.

Ok so here is an update, i have uninstalled all 3 software packages again, thoroughly scrubbed the system for traces and reinstalled everything again, and i have the same error. But this time its not HIPS. The error only occurs when i enable Protocol Filtering. I will start another Thread with the error specifics.

Ohh now i understand. Thank you for your replies Rami

Thank you. Google has sandboxed Chrome for some years now, its not a new thing. I was running it in the last version Sandboxed. I am still keen to use Chrome as i have been using it for a long time and comfortable with it.

Firefox is now installed and runs ok. No problems with this. Thank you

maybe, but it does run sandboxed without HIPS enabled so i am not sure what to do with HIPS .

Its not so obvious to me, and there is nothing in that link that helps. Here's what i know. Without HIPS enabled everything on my system works as it should. With HIPS enabled everything works up to Google ver 68. HIPS is preventing me from running as i should be running. Update google to 69 and it wont run in the sandbox with HIPS enabled, need to turn HIPS off for it to work. So for me it's related to HIPS, Google & Sandboxie. But without HIPS everything works, so what is HIPS doing. Thank you.

I have the same problem after the Chrome updated from 68 to 69. But i am running Chrome through Sandboxie (version 5.26). Note, when i run Chrome unsandboxed it does not crash with the 0x000005 execution error, instead it runs as it should without issue. I have no other antivirus or exploit software running on my WIN 10/64 machine. Tried to reinstalled Chrome, Sandboxie, and then ESET and these changes didn't fix. Then completely removed ESET along with all traces, installed and switched to interactive mode, and permanently approved everything i was asked to approve - it still didn't work ie it crashes with the above error. Tried Chrome beta 70 version and it did not work. Switched off HIPS and am able to load Chrome through Sandboxie as it should. I don't want to run without HIPS enabled so I have rolled back Chrome to Version 68.0.3440.84 (Official Build) (64-bit) and all is working as it should. If anyone has to rollback make sure you disable Chrome auto update. Rollback versions can be found using a google search, google does not provide rollback versions. I have no other problems running programs through Sandboxie with HIPS enabled. Example Internet Explorer and Opera both work. I have wasted hours of time, and need to get on with my life, so I will now wait until someone has fixed this issue before updating Chrome to Version 69 or greater. Thank you OP for your post.

edited