Search the Community
Showing results for tags 'sandboxie'.
Found 1 result
Hello, Recently, changes to either ESET's definitions or modules have caused a problem with the program Sandboxie. Everything was working splendidly until yesterday morning (03July2019, ~7:00AM Pacific Standard Time). 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. 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. 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)". This prevents deletion of the REGHIVE file in the sandbox root, and causes Sandboxie to throw an "Access Denied" error as a result. Other users of Sandboxie and ESET are reporting the same issue on other forums. Is there a possibility to resolve this issue, or revert the change that caused this sudden shift in behavior? Thank you.