Sandboxie Support

Will this be fixed at least in this update?
It is very annoying Network Connection Settings are not sandboxed!

I still believe the best way is to add some parameter for sandbox to allow forward all traffic through proxy. In this way it is not necessary to change parameters of browsers at all.

But it's up to devs of course.

Hi All. OS: Windows 10 Pro x64 I am observing a strange behaviour of IE proxy settings when running in sandbox. From time to time this settings are getting active in unsandboxed IE also. Disabling it in unsandboxed IE leads to disabling it in sandboxed IE (and it's normal), so I have to re-enable it...

The link without password: hxxp://www5.zippyshare.com/v/6wcBDcHb/file.html
However the development is stopped. I am not interested any more in this project as long as BSA is not supported in Sandboxie.

This is clearly Comodo issue, by the way as far as I see only Windows Explorer is affected.
I have created a ticket in Comodo forum concerning this issue: https://forums.comodo.com/bug-reports-c ... 195.0.html
Will see..

otreus, x64 is not supported yet by this portable system. You should install Sandboxie and BSA and configure them by yourself.

Thanks, Buster, but I believe you mean Sandboxie.ini file, not BSA.conf.

All your suggestions will be used.

The constantly updated portable Buster Sandbox Analyzer + Sandboxie system is located at http://tools.safezone.cc/gjf/Sandboxie-portable.zip
All manuals are within the archive.
If you have some problems and/or suggestions - please PM me.

It is not possible to restore settings from one start to another using silent install. It is not possible to use presets for plugins also. And so on. For general use - yes, possibly silent install can help. In particular, flexible ways of use, when user wants to have his own settings - no. I believe...

There is a small syntax error in sc command - so I believe it should be as follows: sc create SbieDrv type= kernel start= demand binPath= "path" So in general it looks like: copy "Sandboxie.ini" "%windir%" sc Create SbieDrv type= kernel start= demand binPath= "%~dp0SbieDrv.sys" sc Create SbieSvc bin...

"SbieDrv is not Win32 application" .

So I've tried. It doesn't work. SbieDrv didn't start so SbieSvc stopped and SbieCtrl showed an error.

So you believe all will be working in the case of such script: copy "Sandboxie.ini" "%windir%" sc Create SbieDrv "%~dp0SbieDrv.sys" sc Create SbieSvc binPath= "%~dp0SbieSvc.exe" REG ADD HKLM\SYSTEM\CurrentControlSet\Services\SbieSvc /v Language /t REG_DWORD /d 1049 /f net start SbieDrv net start Sbi...

loader.exe is driver loader by Sav1or. It is opensource and you can find the code here, for instance.

Simple creating service entry won't work for driver - I will not be able to start it like "net start SbieDrv", reboot is necessary. With loader it is not necessary.

Hello all! I am sure the correct answer on my question only tzuk can give but anyway. I am working now at improving of portable version of Sandboxie. So the question is as follows. AFAIK the loading of Sandboxie can be presented as the following script: copy "Sandboxie.ini" "%windir%" loader.exe Sbi...