This release introduces several important fixes to enhance functionality and improve user experience. A new debugging feature has been added with the inclusion of the HookTrace=y setting, which provides enhanced debugging capabilities for API hooking. The Sandboxie-Plus data folder has been relocated from C:\Users[User]\AppData\Local\Sandboxie-Plus to C:\Users[User]\AppData\Local\Xanasoft\Sandboxie-Plus. This change is automatic for users upgrading to this version, but those downgrading to an older version will need to move the folder back manually. Additionally, some options in the box context menu have been re-ordered for improved usability. This update resolves several critical issues and enhances overall stability. The crash triggered by selecting "Run as Administrator" in the non-advanced view has been fixed, along with a crash caused by missing IP definitions in DNS filtering (#3600, #4475). Compatibility with ARM64 systems has been significantly improved, addressing issues such as x64 executables failing to run on Windows 11 ARM64 (#4422, #4415) and resolving compatibility MSEdge and explorer problems with Windows 10 ARM64. Several user experience issues have also been addressed. These include process self-termination failures, infinite loops when Gui_ConnectConsole waited for SbieSvc.exe to quit (#4462), and missing program icons when paths with spaces were specified in the RunCommand setting (#4416). Additional fixes include template scanning reliability (#4401) and the proper display of credential dialogs for RDP connections in encrypted boxes (#4389). This update aims to provide a smoother, more reliable experience across supported platforms, particularly for users on ARM64 systems. For a full list of changes please review the change log. Download: https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.15.5 Anouncement Additionally, I am pleased to announce that TaskExplorer, a powerful system exploration tool first launched in 2019, has been revitalized and is now production-ready thanks to its fully signed driver. With a host of new features and enhancements, including advanced security options, expanded data columns, and improved usability, TaskExplorer is an ideal choice for both casual users and IT professionals. For more details and to download the latest release, visit: TaskExplorer on GitHub.
Just installing over the top of previous build on Win 10 now. I am being offered the wizard ?? I don't have the UI in black, but it is now !! How do I change it? EDIT.. Changed back to Fusion View.
them the move of the data folder did not work Changed moved Sandboxie-Plus data folder from C:\Users\[User]\AppData\Local\Sandboxie-Plus to C:\Users\[User]\AppData\Local\Xanasoft\Sandboxie-Plus Note: the folder will be moved automatically, when downgrading to an older version you would need to move it back manually. You can just close the wizard and confirm not to show it again
David, I just installed this update from 5.69.6 classic and the same problem I was having before is back. I use a email notifier program called PopPeeper to check my gmail. It uses Oauth2 as a sign in. After the update, the program fails to connect to the Oauth2 server: If I remove Poppeeper from the forced program folder and start it unsandboxed, it works fine. I also log into another email account and that one works fine sandboxed with the new update.
5.69.6 is quite old could you try 5.70.4 or other in betwee. if we can pinpoint the exact version where the issue started it would be much easier to solve.
OK, I will start reverting and see where it started. Browser (chrome) is getting these errors also as of this morning and will not start sandboxed. I also use Tinywall and restrict the svchost to the local network and block most everything else. I do see the sandboxiecrypto.exe is blocked but this worked in prior versions. I also use start/run access restrictions and in my list is runtimebroker, chrome and poppeeper. This always worked OK before. 1) reverted to 5.69.6 and everything is working sandboxed after a reboot
As I said to investigate this further I need to know which version introduced, from your screen shot i see that you are using window 10, in my windows 10 VM chromr works fine in the default yellow box.
Interesting. 5.70.0 is hanging on the Oauth2 server. Removed poppeeper.exe from the forced program folder and started it non sandboxed and it works fine.
I reverted to 5.69.10 and all is well. Gmail goes right through and I can exit the PopPeeper program and start it again under the forced program folder and it works fine. No browser issues either, so it looks like the issue starts for me with 5.70.0 Update: all is still working well 2 days later. No Oauth2 server issues or browser issues.
Also which version of PopPeeper and you said it works with one account but not an other which one works and which one does not? PS: Could you pleas test a 5.70.0 install with the sbiedll.dll from the 5.69.10
Yes, certain. As soon as I switched to 5.69.10 from 5.70.0 the issue immediately went away. It is the latest pop peeper, v5.5.3 The problem is only with Gmail. I have another POP account that goes through with no issues. The error is with the Oauth2 server, it will not connect. I would normally suspect this is a Google issue but the issue shows up when the only change is to upgrade to v5.70.0. Yes, I will try the 5.70.0 with the old dll. Question though - when I search for the dll it shows up in 2 places, do I replace both? C:\Program Files\Sandboxie\SbieDll.dll C:\Program Files\Sandboxie\32\SbieDll.dll Do I upgrade to 5.70.0 and then just delete those dll's and replace with the old one (that I will save before the upgrade?) Thank you.
Well, now the fresh install of the 5.70.0 is working. I did not swap the dll's out. I'll use it tomorrow and if all goes well I'll try upgrading again until it breaks. Should I always reboot between upgrades? I'm trying to think of anything I did before that may have caused this. Update 1: The program is now hanging on the Oauth2 server connection after working for 3-4 times. I tried deleting the .dll and replacing it with the 5.69.10 version but it would not let me do it. I did both a drag and drop and a copy/paste and it said it was doing it but the file version did not change. Is this a privilege problem? I am an admin user. Update 2: PopPeeper is not working with Gmail this morning (2/26) after a reboot. It works outside the sandbox though.
Thanks - I did try that before and it does not work. If I run the program outside Sandboxie it works fine. Very odd.
@DavidXanatos PopPeeper will eliminate the Oauth2 authentication for Gmail when their next update comes out. Instead they will use something called App passwords. I switched over to the new way now and updated to the latest SBIE classic 5.70.7 and everything appears to be working fine. I guess somehow the Oauth2 servers were the issue but I still don't understand how a version change to SBIE would have broken it. Thank you for the time you spent helping me on this!
Portable POP Peeper (not Pro) working fine since last year. It's running fine ever since on top of SBIE+ and Oauth2. I don't understand why... https://support.google.com/accounts/answer/185833?hl=en Edit: OK now I found the reason behind such decision: https://www.esumsoft.com/news/important-gmail-oauth2-news/
