Sandboxie Support

Combined 32/64 installer:
http://www.sandboxie.com/SandboxieInstall.exe

Separate:
http://www.sandboxie.com/SandboxieInstall32.exe
http://www.sandboxie.com/SandboxieInstall64.exe

Changes in 5.14 RC
1) Added OpenClsId={3480A401-BDE9-4407-BC02-798A866AC051} under Thunderbird in templates.ini.

Changes in 5.13.8
1) Fixed hang when starting MS Office applications.
2) Eliminated error SBIE2314 Cancelling process xxxx.exe [xxxx / 9]
3) Added Vivaldi settings to templates.ini

Changes in 5.13.7
1) Proxy Auto Config (PAC) files were not functioning in Win 10 Anniversary.

Changes in 5.13.6
1) Fixed issue some users had with blank web pages in Chrome 53.

Changes in 5.13.5
1) Fixed Recover to Any Folder browse dialog box.

Changes in 5.13.4
1) Vivaldi is now supported.
2) All browse for folder dialog boxes have been updated. They are now larger, re-sizable and have more features.

Changes in 5.13.3
1) Added new Sbie setting BlockNetworkFiles. It is available under Sandboxie Settings -> Restrictions.
When BlockNetworkFiles=y, sandboxed applications are blocked from reading network files or folders. Individual files/folders can be opened for reading/writing using the normal Resource Access settings.
This option is enabled by default for new sandboxes.
2) Eliminated the SBIE2314 Canceling process SandboxieBITS.exe [xxxx / 9]
3) Fixed the Microsoft Account Sign-in Assistant issues (hotmail.com, outlook.com, etc.)


Changes in 5.13.2
1) Fixed clipboard copy/paste failure from sandbox to host.

Changes in 5.13.1
1) Fixed Actual Window Manager (and maybe some other apps).

(re)Installed AWM 8.8.3 to test this and it's only been a short time but no crashes in palemoon or weird cpu usage like with 5.12. Thanks, it's nice to be able to stick with my standard setup! :D

Great! It works with Internet Explorer and AWM again.

Thanks a lot, Curt and Craig!

All runs well with 5.13.1 in my XP and W7 32 bits. Appreciate the quality.

Bo

With 5.13.1 Beta, steam start up very slow inside sandboxie. Launching games through steam will either fail or crash due to steam_api unable to communicate with steam client process. All was fine with 5.12

Windows 10x64.

syazaz wrote:With 5.13.1 Beta, steam start up very slow inside sandboxie. Launching games through steam will either fail or crash due to steam_api unable to communicate with steam client process. All was fine with 5.12

Windows 10x64.

Nothing in beta 5.13.1 had ANYTHING directly to do with Steam

Changes in 5.13.1
1) Fixed Actual Window Manager (and maybe some other apps).

Again, we do not test steam games. We know the Steam client works. But that's all we test, and not all the time. That's up to users to test. We have done ZERO Sandboxie updates since before 5.10 as it relates to Steam in almost a year.

Try deleting the contents of your SB and try again, or create a new sandbox.

syazaz wrote:With 5.13.1 Beta, steam start up very slow inside sandboxie. Launching games through steam will either fail or crash due to steam_api unable to communicate with steam client process. All was fine with 5.12

Windows 10x64.

Not sure what to say, 5.13.1 and Steam here on Windows 7 x64 is still working fine. I just played Grim Dawn for 2 hours in sandboxie :-/ I have noticed that the load time for steam in sandboxie is a lot slower as well but it has been like that forever on my end, not a new thing with 5.13.1 for me.

Thanks, GreenCloud Printer is working again.

It was working fine during v5.11 Beta, but stopped working with the launch of v5.12

secret365 wrote:Thanks, GreenCloud Printer is working again.

It was working fine during v5.11 Beta, but stopped working with the launch of v5.12

Interesting. Again, nothing in 5.13..1 that would directly affect that.

5.13.2 has been released.

After installing 5.13.2 when I rebooted, I had to reactivate my license, is this supposed to happen

I guess that depends, normally all major X. or X.X changes require a re-activation while X.X.X usually don't so if you were coming from 5.10 or 5.12 that would be normal. If you had the 5.13.1 beta already and re-activated for that previously then it would be odd having to re-activate for the 5.13.2 beta...I guess I'll find out within the next few days if happens to me but atm I'm focused on some Windows 10 tests I have going on in a VM [I'm currently waiting for the latest dism session to finish] so I haven't gotten around to trying the .2 SBIE release on my live OS yet since the copy/paste issue isn't something I've encountered so far but 5.13.1 has been great on my system though I do still have time to troll forums :-/

Curt@invincea wrote:5.13.2 has been released.

Copy/Paste and Cut/Paste from a sandboxed explorer window appear to be fixed on Windows 7, 64-bit. Thanks.

ssj100 wrote:

Curt@invincea wrote:5.13.2 has been released.

Copy/Paste and Cut/Paste from a sandboxed explorer window appear to be fixed on Windows 7, 64-bit. Thanks.

Question, you brought up a good point about drag and drop. We know this seemed to work before, but it appears, even with the latest fix, it doesn't. Copy/paste works, but if you have any recollection of using that in the past, let us know? We're all trying to question that too. We know it did work, at least we keep telling ourselves that.

Craig@Invincea wrote:Question, you brought up a good point about drag and drop. We know this seemed to work before, but it appears, even with the latest fix, it doesn't. Copy/paste works, but if you have any recollection of using that in the past, let us know? We're all trying to question that too. We know it did work, at least we keep telling ourselves that.

Drag/drop from a sandboxed windows explorer certainly does not work with recent versions of Sandboxie. For some reason, I also seem to recall that it did work at some point in the past, but I can't reproduce it - in fact, I just tested as far back as Sandboxie version 3.20 (released around 2007) and drag/drop does not work even with that. I actually never use drag/drop, favouring the mouse right click copy/cut and paste and keyboard Ctrl-x/c/v commands over it. But perhaps I've always used that because drag/drop has never worked?

EDIT: in my opinion, I wouldn't spend too much effort looking into it - it doesn't significantly affect usability/convenience, given there are several other ways to "drag/drop" as above. Furthermore, my fear is that if something like this is fiddled with, we'll start to see "bypasses" like this again (these were some interesting POCs that froze the mouse and terminated processes outside the sandbox, despite the POCs being run sandboxed etc):
http://forums.sandboxie.com/phpBB3/view ... 0&start=45