I have Sandboxie (the last one released by them) installed on a Lenovo laptop on which I also just installed Chrome. My primary browser is Firefox and that’s the only one that opens Sandboxed. (My wife uses Chrome for one Zoom-like app. We use FF for all else. Chrome opens just fine.) When we open FF via Sandboxie, we now get error messages we’ve never seen before: SBIE1222 Error with security token (C00000BB /35) and SBIE2314 Cancelling process Start.exe What’s causing these errors and how do I fix them? We’ve been using Sandboxie for years. This is a PC and the O/S is Windows 10, latest patches. Thanks for your help and for taking up the cause of Sandboxie! WSC3
Please advise your Sandboxie version number? - Please review: SBIE1222 Error with security token: [C00000BB / 35] -1 year ago https://community.sophos.com/sandboxie/f/forum/113512/sbie1222-error-with-security-token-c00000bb-35 - Sandboxie Plus (Sbie fork) https://www.wilderssecurity.com/threads/sandboxie-plus-sbie-fork.427755/ - Sandboxie Technologies (SBIE Open source) https://www.wilderssecurity.com/threads/sandboxie-technologies-sbie-open-source.428156/
Version 5.31.4, 64bit. Don't have Windows Insider installed. I see that there are newer versions but none seem to address this specific issue. Thoughts?
The last 'legacy' signed release version was 5.33.6 however it will no longer work with Chrome based browsers (but will with Firefox) https://community.sophos.com/sandbo...ndboxie-5-33-6-release-and-open-source-update Have you tried using it with Firefox? Also see here https://www.wilderssecurity.com/threads/sandboxie-plus-sbie-fork.427755/page-26#post-2956467
We only use it with FF. My wife installed Chrome for a single use purpose, but it's not used sandboxed. The error message I just got on my laptop reboot is that "This app can't run because it causes security or performance issues on Windows. A new version may be available. Check with your software provider for an updated app that runs on this version of Windows." My wife has Windows Version 10.0.19041, build 19041. So I'm guessing an upgrade is necessary. Which of the new options on your link above is the safest one to use that will eliminate this error? Thanks!
I'm having the same error, except with all programs trying to be opened with sandboxie (file explorer, firefox, chrome, etc.). This only occured after updating to the latest Windows 10 Version 19041.572 build last night because I was literally using sandboxie just fine and then decided to update windows. I was previously using I believe sandboxie 5.31.02 or something and I just tried using the 5.43.6 fork release but both still have the same error and I also get the security error referenced above when starting the computer (This app can't run because it causes security or performance issues on Windows).
It worked! Thanks so much. So we're waiting on the ability to buy security certificates for 5.43.6 to be a better solution?
I'm having same issues with Sandboxie and Chrome the last few weeks. While I love sandboxie and have been using it for years...I am not technically knowledgeable enough to be trying to fix SB to work with Chrome. I am committed to Chrome. Is there another sandbox product/software worth using instead of sandboxie?
Give 5.43.6 a try. https://www.wilderssecurity.com/threads/sandboxie-plus-sbie-fork.427755/page-26#post-2956467 or follow the steps here for 5.336 (which I presume you are using?) https://www.wilderssecurity.com/thr...-sbie-open-source.428156/page-20#post-2954919 Do everything the same as it says but instead of the words Vivaldi.exe just put Chrome.exe
5.33.6/ 5.43.6 worked for me, apparently when I first installed 5.43.6 it didn't update everything so I had to uninstall my 5.31.2 first. My problem now with both 5.33.6 and 5.43.6 is that some programs are running markedly slower than before. If I use file explorer sandboxed, it takes a couple of seconds to open a folder and I can't use the search bar for some reason (can't click into the search bar). I thought it might've just been 5.43.6 that was causing the issue so I tried going to 5.33.6, but same issue. I'm assuming this problem has to do with the most recent 19041.572 windows update I did because it was never this slow previously.