Sandboxie Support

Different design window in firefox 41
Early I did not notice because I use another theme

original

sandboxie

f10mpk wrote:Different design window in firefox 41
Early I did not notice because I use another theme

original

sandboxie

Yes, we saw this in Windows 10 with FF. We believe that SBIE is actually presenting the window correctly and forcing FF to conform to Win10 colors.

Looks like chrome is doing the same thing too. I'm running chrome out of a portable install ( http://portableapps.com/apps/internet/g ... e_portable ) since I had some initial difficulties installing it into a sandbox.

Note, on a lighter/white background the inactive window has a black border too.

Quite honestly I think calling the current state of SBIE a RC is a bit of a joke. Lots of programs don't work (Steam, Slack, probably many others) and it seems you're just taking stabs in the dark trying to fix it. I'm really surprised that there is still no stable version available as windows 10 didn't exactly come out of the blue.

ozb3n wrote:Quite honestly I think calling the current state of SBIE a RC is a bit of a joke. Lots of programs don't work (Steam, Slack, probably many others) and it seems you're just taking stabs in the dark trying to fix it. I'm really surprised that there is still no stable version available as windows 10 didn't exactly come out of the blue.

About Win 10 can not say anything ...
But in Win XP x86 and Win 7 x64 SBIE 5.04 work normally.

ozb3n wrote:Quite honestly I think calling the current state of SBIE a RC is a bit of a joke. Lots of programs don't work (Steam, Slack, probably many others) and it seems you're just taking stabs in the dark trying to fix it. I'm really surprised that there is still no stable version available as windows 10 didn't exactly come out of the blue.

Windows 10 may not have come out of the blue, but it has been and still is having major changes. In many ways Windows 10 is also a release candidate. Also remember 1st and foremost SBIE is a security program to protect your browsers.

ozb3n wrote:Quite honestly I think calling the current state of SBIE a RC is a bit of a joke. Lots of programs don't work (Steam, Slack, probably many others) and it seems you're just taking stabs in the dark trying to fix it. I'm really surprised that there is still no stable version available as windows 10 didn't exactly come out of the blue.

What I'd be interested in hearing from the developers/company is: What is the plan to move forward with Sandboxie on Windows 10 and in what timeline?

Although I am running ok with Sandboxie 5.04 on Windows 10 (fully patched as of today) I am still finding Sandboxie "flakey" (crashes, weird error messages, etc).

I'm curious, does AllowSpoolerPrintToFile=n override the changes recently made allowing the spooler to write to the temp directory? Also does that change only allow writing to the temp directory 'inside the sandbox' or is to the real system temp dir? It sounds like the 'real' system...but figured I better double check.

Curt@invincea wrote:Fixes in 5.03.1
2) The print spooler (spoolsv.exe) is now permitted to write files to the system temp folder (windows\temp) and the user temp folder (\Users\<username>\AppData\Local\Temp)

How to close this security hole you just have opened?

ozb3n wrote:Quite honestly I think calling the current state of SBIE a RC is a bit of a joke. Lots of programs don't work (Steam, Slack, probably many others) and it seems you're just taking stabs in the dark trying to fix it. I'm really surprised that there is still no stable version available as windows 10 didn't exactly come out of the blue.

Maybe you should be more specific about what doesn't work in steam ... because I've installed it and several games within a sandbox under default settings and have had zero problems to date with it.

kawaiiwolf wrote:Maybe you should be more specific about what doesn't work in steam ... because I've installed it and several games within a sandbox under default settings and have had zero problems to date with it.

If you read up in the thread you will see I have explained what the issue is with steam weeks ago. Others have confirmed the same problems.

Peter2150 wrote:Windows 10 may not have come out of the blue, but it has been and still is having major changes. In many ways Windows 10 is also a release candidate. Also remember 1st and foremost SBIE is a security program to protect your browsers.

I do realize this is a security program and hence I'm asking why this could be considered a RC when it is clearly in a state that does not justify it. There are still too many things broken or unfinished. Saying this is a program for your browser is simply false. Check the homepage it says "Safely try new software". It doesn't say safely try new browsers.

Win10 is also not a RC as you claim. Look at other security products, they achieved full compatibility weeks and months ago.

I have used SBIE on Win7, Win8, Win8.1 without any major issues, in fact it has been running fine for 99% of the time. However this Win10 release just seems botched from the start.

Steam client is buggy enough (out of sandbox). I use it for almost 10 years. They prefer to find workarounds rather than fixing simple issues. Only payments never failed to me All these protection and anti-cheating mechanisms were made exactly to prevent manipulations with the client and games.
Seriously this is so pointless, also wasting devs time knowing that future updates may break it again or giving direct access to revert changes made by sandboxie. Just because some people want it. There are many other more important issues to fix now... and other things especially for Win10.
I have never seen anyone who ever posted any reasonable reason to run games in sandbox.

Just my opinion

ozb3n wrote:The reason to run a game in a sandbox is simply the same as for any other program. I don't want it to touch my system by installing all sort of "additional extras" the publisher thinks I should have. I don't want the 150th copy of the C++ runtime installed or bundled "content" such as system surveys etc. Steam has been running fine in a Sandbox on Win7/8/8.1. What "workarounds" are you referring to that stream is using?

It's offtopic right now, but you can install software as layers. Enable, disable, remove them when not needed. Symantec Workspace Virtualization Admin can do that for example

Dun wrote:Steam client is buggy enough (out of sandbox). I use it for almost 10 years. They prefer to find workarounds rather than fixing simple issues. Only payments never failed to me All these protection and anti-cheating mechanisms were made exactly to prevent manipulations with the client and games.
Seriously this is so pointless, also wasting devs time knowing that future updates may break it again or giving direct access to revert changes made by sandboxie. Just because some people want it. There are many other more important issues to fix now... and other things especially for Win10.
I have never seen anyone who ever posted any reasonable reason to run games in sandbox.

Just my opinion

The reason to run a game in a sandbox is simply the same as for any other program. I don't want it to touch my system by installing all sort of "additional extras" the publisher thinks I should have. I don't want the 150th copy of the C++ runtime installed or bundled "content" such as system surveys etc. Steam has been running fine in a Sandbox on Win7/8/8.1. What "workarounds" are you referring to that stream is using?

will (can) the commodo problem be fixed or will sandboxie be incompatibe with comodo firewall installed?

i know there is a workaround but my question is if there is a better solution in sight?
the problem is know for a while but thw RC does not fix it.

so i am afraid that this issue will not be fixed.

ozb3n wrote:

Dun wrote:Steam client is buggy enough (out of sandbox). I use it for almost 10 years. They prefer to find workarounds rather than fixing simple issues. Only payments never failed to me All these protection and anti-cheating mechanisms were made exactly to prevent manipulations with the client and games.
Seriously this is so pointless, also wasting devs time knowing that future updates may break it again or giving direct access to revert changes made by sandboxie. Just because some people want it. There are many other more important issues to fix now... and other things especially for Win10.
I have never seen anyone who ever posted any reasonable reason to run games in sandbox.

Just my opinion

The reason to run a game in a sandbox is simply the same as for any other program. I don't want it to touch my system by installing all sort of "additional extras" the publisher thinks I should have. I don't want the 150th copy of the C++ runtime installed or bundled "content" such as system surveys etc. Steam has been running fine in a Sandbox on Win7/8/8.1. What "workarounds" are you referring to that stream is using?

Hi ozb3n

I understand your reason, but, and it's a big but. If any software published is forcing unneed, or unwanted stuff on you, you would be very wise to not install that software period. Ignoring that rule you will eventually get bitten badly.