Jump to content

Search the Community

Showing results for tags 'sandboxie'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • ESET General Forums
    • ESET Announcements
    • General Discussion
    • Forum FAQ's and Rules
  • ESET Home User Products
    • ESET Internet Security & ESET Smart Security Premium
    • ESET NOD32 Antivirus
    • ESET Cyber Security (for Mac)
    • ESET Cyber Security Pro (for Mac)
    • ESET NOD32 Antivirus for Linux Desktop
    • ESET Products for Mobile Devices
    • Web portals
  • Malware Detection and Cleaning
    • Malware Finding and Cleaning
    • ESET Standalone Malware Removal Tools
  • ESET Business User Products
    • ESET Endpoint Products
    • ESET Products for Windows Servers
    • ESET Products for Linux Servers
    • ESET Products for Mobile Devices
    • Remote Management
    • ESET Enterprise Inspector (EDR)
    • ESET Products for Virtualized Environments
    • Encryption
    • ESET Licensing for Business
  • ESET Beta Products
    • ESET Beta Products for Home Users
    • ESET Beta Products for Business Users
  • Slovak and Czech forums
    • ESET NOD32 Antivirus, ESET Internet Security a ESET Smart Security Premium
    • Produkty pre mobilné zariadenia
    • Vírusy a iné hrozby
    • Ostatné

Categories

  • Files
    • Early Access
    • Miscellaneous

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Interests

Found 1 result

  1. 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.
×
×
  • Create New...