


I understand it probably doesn't help you to know this, but I currently run those three programs together (with HIPS enabled) on the same OS that you are running, and I do that on two computers. In your particular case, I would keep SBIE, keep Chrome, and run ESET with HIPS disabled, or configured so as to run correctly with SBIE, if/when you eventually figure it out. That has always been my method, for at least the last 10+ years as a Sandboxie user. I will say that personally, I have always ranked Sandboxie as my most crucial security program, and if I came across another program that I could not get to coexist with it, I would always choose to keep Sandboxie, even if it meant removing and not using the the other program.

Click to expand.I am sorry, I do not have any proposed solutions for you beyond what I have already stated.
