-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run Outside Sandboxie stopped working #614
Comments
I have the same problem with Sandboxie Classic 5.48.5 / 5.49.0 x64 and Windows 10 2004 x64. Workaround to avoid the issue: Press down CTRL+SHIFT when you click the Run Sandboxed command or when you double click the shortcut. Possible files involved here. |
Did that ever worked for em itdoes not even work with the last sophos version |
Probably it doesn't work since 2017, but I can't be sure. According to the last post in this discussion from tzuk, Run Outside Sandbox was surely working in version 4.01.02:
Lucky for you, you might want to download it from here and test it accordingly (stricly in a VM with Windows 7): |
@DavidXanatos |
that should be fixed in the 0.9.2 build can you please test and confirm |
ok so the status, the thing fixed was an otehr dfp bug... |
David has added a simple fix in Sandboxie Classic 5.51.3 after writing the previous post, so the Run Outside Sandbox command has finally been fixed. |
IDK how long it stopped. I have some shortcuts that execute Start.exe to make some app run inside some sandbox. I use that so that these apps' profiles aren't changed and are restored to host's version every time the sandbox content is deleted.
When I need to change anything on host's version, I right click on the shortcut and choose to run it outside Sandboxie, then the app does that. I make the editions I need and close it ASAP, then I delete the sandbox content and execute it back inside it.
I just tried to do that and it failed. There's no error message, the app just executes inside the sandbox even though I had selected to run it outside any.
The text was updated successfully, but these errors were encountered: