5.14 Released

[Healer135]

Thank you for your quick reply.

1. Yes. It is ok with 5.10 as I mentioned above. I jumped from 5.08 right into 5.13.1 then tried 5.12 and 5.13.2. I did not try 5.11 since installers of this version are not present on the site any more. But I suspect it all started with 5.12 because of “The new, faster loader code developed for Windows 10 is now used for Win 8.0 & 8.1". Sorry I did not indicate before that I run Win 8.1.

2. Yes. I am trying new programs and workarounds and browsing within a sandbox. It is also my rule of thumb not to install older programs directly into a modern OS, esp. for the first run, where possible. Because older programs (incl. and esp. legal ones) may leave lots of obstructive trash inside the system (obsolete libraries, unnecessary file associations, non-uninstallable elements of old-fashion license protection etc.) or even unrecognizable threats (all sorts of accompanying riskware or rare trojans) and may refuse to run or to install at all when prevented doing so. VMs are too heavyweight and wasteful, imply too many virtual hardware compatibility issues and significant performance drop for that sole purpose. They also protect from threats but do not provide insight into the real situation under the host OS. So I still hope I do not use Sandboxie improperly, i.e.in the way it is not meant to be used, although it is not an universal solution. As I said, I just noticed that Sandboxie has changed its behavior and lost a little parcel of its functionality (something stopped working that worked before, this time a game, both when installed within and just started from within the sandbox), be it for safety sake or by coincidence. And that with such a surprising error (SBIE2310 – but I never installed PC-Tools Spyware Doctor). I thought it would be of interest for developers to know about that unexpected effect. Because it might be (or not be) a sign of a more general issue. Sorry again if I was some kind of misunderstood.

[Craig@Invincea]

But I suspect it all started with 5.12 because of “The new, faster loader code developed for Windows 10 is now used for Win 8.0 & 8.1". Sorry I did not indicate before that I run Win 8.1.

Doubtful.

It is also my rule of thumb not to install older programs directly into a modern OS,

SBIE is not guaranteed to be able to host and run any and all programs. You'd need a VM for that. You need to realize the difference between an isolated container and a VM.
A VM is heavy, because it needs to be able to host a full fledged OS and the programs along with (drivers, services, etc.) which is NOT possible in SBIE.
A container is simply a layer over your OS.

I thought it would be of interest for developers to know about that unexpected effect.

Thanks, but you need to know the limits of a container vs a an actual VM. SBIE was never designed to be a VM or to host any and all programs. Simply impossible.

Sanboxie was designed to run IE in a container. Hence, SandboxIE. That's the core of it, that's what it does, but now we have many many browsers, office suites, chat clients and some programs that can be installed directly into the SB (most browsers) and almost ALL programs can be "run as sandboxed" when installed on your host.

[barny]

Is it possible to look into this issue http://forums.sandboxie.com/phpBB3/view ... 17&t=19588 ?

The topic gives more info, but it relates to Immediate Recovery not working when you save a file to a location where that file already exists (ie. replacing the file).

[BilleBarrett]

I started to get these errors this morning after my Windows 10 was updated again
Windows 10 Pro Build 14393.rs1_release.160715-1616
This is happening using Chrome Version 52.0.2743.82 m (64-bit)
It occurs when I call Teamviewer from my Maxfocus monitoring software

SBIE2314 Canceling process SandboxieBITS.exe [3216 / 9]
SBIE2314 Canceling process SandboxieBITS.exe [3216 / 9]
SBIE2314 Canceling process SandboxieBITS.exe [3216 / 9]
SBIE2314 Canceling process SandboxieBITS.exe [3216 / 9]
SBIE2314 Canceling process SandboxieBITS.exe [3216 / 9]

[Craig@Invincea]

Yes, we are aware of it.

FR builds will always be ahead of SBIE beta builds. Issues such of these will come up. This is why FR builds and Beta builds should not be used on production machines.

SBIE2314 Canceling process SandboxieBITS.exe

And it's a warning, a nag. It doesn't affect the program. You just can't hide it. It'll be addressed in upcoming betas. We only have seen this is Chrome.

call Teamviewer from my Maxfocus monitoring software

We haven't tested these with SBIE. So it may/may not work.

[BilleBarrett]

I had to stop using Beta 5.13.2 because the errors previously were getting to bad, when ever I had to invoke a program on a remote site I would start getting
SBIE2314 Canceling process SandboxieBITS.exe [3216 / 9]
SBIE2314 Canceling process SandboxieBITS.exe [3216 / 9]
SBIE2314 Canceling process SandboxieBITS.exe [3216 / 9]
SBIE2314 Canceling process SandboxieBITS.exe [3216 / 9]
SBIE2314 Canceling process SandboxieBITS.exe [3216 / 9]
errors, I believe it has something to do with the new windows 10 upgrade
Should I go back to 5.12 and see if it happens there
I am not comfortable running outside the Sandbox

[BilleBarrett]

I had to go back to 5.12 for everything to work

[Craig@Invincea]

I had to go back to 5.12 for everything to work

It's not that it isn't working, It's just a nag message. SBIE and the programs in the sandbox are within the container. You just can't hide that message at this time.

TeamViewer hasn't been tested by us with SBIE, but for that message, we've seen it. It's new and rare. But the programs still function.

Again, That's why it's called a beta as well!

[BilleBarrett]

Can any one help with this
SBIE2314 Canceling process SandboxieBITS.exe [8076 / 9]
SBIE2314 Canceling process SandboxieBITS.exe [8076 / 9]
SBIE2314 Canceling process SandboxieBITS.exe [8076 / 9]
SBIE2314 Canceling process SandboxieBITS.exe [8076 / 9]
SBIE2314 Canceling process SandboxieBITS.exe [8076 / 9]
Ever since I upgraded to new windows version I get it constantly

Thanks
Bill e. Barrett

[BilleBarrett]

I just had to send this to you
My Client David in HP got hit by ransomware, OMG everything was encrypted, but wait no it was not.
David is a user of Sandboxie, everything that happened, happened in the confines of the Sandbox
I saw the encrypted data, but when I looked in his document folder everything was OK
Then I look at the content of the Sandbox and it was full of Encrypted Data, all I did was a Terminate All and it took the sandbox a few minutes deleting the encrypted Data
Sandboxie save David's Company data, OMG I’m so glad

[Peter2150]

No surprise here. That is what Sandboxie is all about.

[Craig@Invincea]

@BilleBarrett That's what we strive to do with SBIE all the time! Fantastic that everything is safe data-wise.

[Curt@invincea]

5.13.3 has been released.

[ssj100]

5.13.3 has been released.

Thanks. Can I ask what's an example of a specific situation where this feature would be useful?:

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.

I don't quite understand what the feature does. Is there a way to test it in action?

[bo.elam]

5.13.3 has been released.

Looking good .

Bo