I was experiencing very similar symptoms that you guy do but with avast Pro, so it's not only related to ESET, although, ESET might work around it, sandboxie has too many flows now.
My comment it's not directed towards license, the only reason I have mentioned is that even thou I have about 30 lifetime licenses I had no choice but to ditch sandboxie due to similar and other unresolved issues. The isssue should be reproducible by ESETĮither I didn't make it clear or you misunderstood me. Lifetime licenses have been honoured by Sophos, so I am not sure what you are talking - don't know about Win 10 - still using Win 7/64 bit - if I have time over the weekend I will try to generate the logs but looking at the posts here and at the sandboxie/sophos site, with this issue discussed on the last few pages and the Sandboxie forum is now housed at Sophos. Is there a possibility to resolve this issue, or revert the change that caused this sudden shift in behavior? Thank Urbano - Tzuk sold his product many years ago to Sophos and despite some concerns at the time, the product has continued to work well with regular updates - there is a mammoth thread at Wilders Securities Other users of Sandboxie and ESET are reporting the same issue on other forums. This prevents deletion of the REGHIVE file in the sandbox root, and causes Sandboxie to throw an "Access Denied" error as a result. Tracking the issue with Process Explorer reveals that, even after shutting down and terminating all other programs, EKRN.EXE maintains interaction with the registry key "HKU\Sandbox_(UserName)_(SandboxName)".
The autodelete command is now failing due to the fact that ESET is keeping files within the sandbox open, even after all processes in the sandbox are closed.
I have a Sandbox set up so that Chrome will launch within it automatically, and upon closure of Chrome, the sandbox is purged via an auto-delete command. Everything was working splendidly until yesterday morning (03July2019, ~7:00AM Pacific Standard Time). Recently, changes to either ESET's definitions or modules have caused a problem with the program Sandboxie.
0 kommentar(er)
