5.01 Beta Available (latest version 5.04 RC)

[albert17]

I downloaded sandboxie to version 5.01.13 today the 64-bit version and it worked temporarily I use firefox 40.0.3 but when I tried sandbox the browser it only worked with msn.com than I tried firefox and that worked as a forced programm.
After a reboot the PC chrashed again. I am lucky to have a backup of my system but Sandboxie I will not use it for the time being.While I have a lifetime contract. It worked always ver good maybe I will try it again in the future.

I read that Microsoft is only using their own browser may be that's the problem in Europe ? In 2009 the EC forced microsoft a choice of browsers MS paid as a penalty 497 million euros to Brussels.

Mozilla complains that Edge is after an upgrade to OS Windows 10 the standard browser.

http://www.nytimes.com/2013/03/07/techn ... .html?_r=0

When are you able to use firefox 40.0.3 to be browsed as sandboxed browser or has it to do with commercial reasons

[rbrauer]

I have tried various 5.x versions and at some point started having the issue with (SBIE2303) described in the release notes.



I finally started doing clean installs and was testing by trying to start notepad sandboxed. When I actually followed instructions given by the installer to disable anti-virus before the driver install by using AVG's temporary disable function, I found that notepad worked again. Later, I tried running Firefox installer sandboxed on the same install and got the same error. AVG had automatically restarted after five minutes.

So it looks like, for me at least, AVG is causing the problem. Does anyone know of a fix or workaround? Thanks.

[panasonic]

Hi,
I have windows 10, Chrome Version 45.0.2454.85 m (64-bit), and sandboxie 5.01.13
I just updated chrome to that version.

This is the error I get when I launch chrome sandboxed.




If chrome manages to launch sandboxed, this is the error I get when I close it:



Running the same version of Chrome v45.0.2454.85m without issues all morning in SBIE v5.01.13. I would first empty your sandbox.




everything was fine with sandboxie 5.01.13 until I updated chrome to version 45.

Thanks for the reply. Well, I solved it by reverting Chrome back to v44 using Acronis disk image, and blocking google update with firewall.

Now chrome works fine again sandboxed.

I'm a little surprised this sandboxie version is already RC without code change. For me, Windows 7 and sandboxie 4.20 was nearly perfect. Windows 10 and sandboxie 5.02RC is nowhere near. Obviously, thanks for all the hardwork getting to this point, though. Windowds 10 has been and is a PITA.

[Craig@Invincea]

Thanks for the reply. Well, I solved it by reverting Chrome back to v44 using Acronis disk image, and blocking google update with firewall.

Now chrome works fine again sandboxed.

I'm a little surprised this sandboxie version is already RC without code change. For me, Windows 7 and sandboxie 4.20 was nearly perfect. Windows 10 and sandboxie 5.02RC is nowhere near. Obviously, thanks for all the hardwork getting to this point, though. Windowds 10 has been and is a PITA.

Glad it's working, but that new version of Chrome does in fact work with SBIE. Yes, there is plenty of code changes, etc. in the v5 RC.

[Extremezhazha]

I'm Currently Running WIndows 10, after Windows Update Installed one of those updates, Sandboxie is no longer able to start any Windows Explorer session, with the message below:

SBIE2205 Service not implemented: Win32Init.5 (00000000)
SBIE2205 Service not implemented: GdiInit.C0000017

But other stuff can be started...So hopefully the fix will arrive pretty soon?

[Craig@Invincea]

I'm Currently Running WIndows 10, after Windows Update Installed one of those updates, Sandboxie is no longer able to start any Windows Explorer session, with the message below:

SBIE2205 Service not implemented: Win32Init.5 (00000000)
SBIE2205 Service not implemented: GdiInit.C0000017

But other stuff can be started...So hopefully the fix will arrive pretty soon?

Yes, we're seeing the same. We're looking into it.

[Craig@Invincea]

Since Sandboxie 5.01.12 the fonts in Opera 12.17 work perfectly. But it gives following error (also in 5.01.13):
Ad blocker: AdMuncher https://www.admuncher.com/

Error when loading winsock library from hook DLL in the following process: opera_plugin_wrapper (error code WSPF-P-connect)
Error when loading winsock library from hook DLL in the following process: sandboxierpcss (error code WSPF-P-connect)
Error when loading winsock library from hook DLL in the following process: opera (error code WSPF-P-connect)

See Curt's response here for AdMuncher http://forums.sandboxie.com/phpBB3/view ... er#p112792

[panasonic]

Thanks for the reply. Well, I solved it by reverting Chrome back to v44 using Acronis disk image, and blocking google update with firewall.

Now chrome works fine again sandboxed.

I'm a little surprised this sandboxie version is already RC without code change. For me, Windows 7 and sandboxie 4.20 was nearly perfect. Windows 10 and sandboxie 5.02RC is nowhere near. Obviously, thanks for all the hardwork getting to this point, though. Windowds 10 has been and is a PITA.

Glad it's working, but that new version of Chrome does in fact work with SBIE. Yes, there is plenty of code changes, etc. in the v5 RC.

Ok, I got Chrome v45 to work correctly with Sandboxie 5.02 RC. I had previously taken ownership of the google folder, and when chrome updated, the new chrome version folder didn't have ownership, I'm guessing. I took ownership of the entire google folder one more time, and everything works fine. Just wanted say it had nothing to do with Sandboxie. And what I meant about code change was that there was no code change from 5.01.13 to RC like the change log says. Anyway, keep up the great work. I won't take up anymore space in this forum.

[crypt]

I'm not sure if it's just me because I am running Comodo. A guy in another thread posted a workaround and it's been working ever since. However, when i try to run the installer 'mirc743.exe' I get this error:



I would like to have this fixed if possible.

[leeopop]

I'm Currently Running WIndows 10, after Windows Update Installed one of those updates, Sandboxie is no longer able to start any Windows Explorer session, with the message below:

SBIE2205 Service not implemented: Win32Init.5 (00000000)
SBIE2205 Service not implemented: GdiInit.C0000017

But other stuff can be started...So hopefully the fix will arrive pretty soon?

I have exactly same problems with Slack windows app (https://slack.com/apps).
According to my knowledge, Slack application uses internal browsers integrated with it.

My questions are:
1. Is this problem is known to developers and is it going to be fixed?
2. Can I trust this application? I mean, I trust slack.com, but I wonder whether this error is due to Slack application trying to break the sandbox.

I tried at both the stable release and the beta release, and got same errors.

[sandfan]

Sandboxie v5.02RC x64
run DAEMON Tools Ultra v3.1.0.368 setup

---------------------------
DAEMON Tools Ultra
---------------------------
Unable to initialize DAEMON Tools Ultra setup.
---------------------------
OK
---------------------------

[Craig@Invincea]

My questions are:
1. Is this problem is known to developers and is it going to be fixed?
2. Can I trust this application? I mean, I trust slack.com, but I wonder whether this error is due to Slack application trying to break the sandbox.

I tried at both the stable release and the beta release, and got same errors

1. Yes, we found out about this break late yesterday. It's being looked at. No ETA
2. Can comment one way or another about slack, but you error is what we are seeing as related to the MS update from earlier in the week breaking SBIE and Windows Explorer.

[bdg2]

There is a problem with Chrome 45 (64 bit) on Windows 7 Ultimate 64 bit which doesn't occur with V4.20.

When I start Chrome inside a SandBoxIE V5.02 RC sandbox and go to Virustotal.com check Choose File, choose a file and click Open the whole browser closes.

[albert17]

I downloaded sandboxie to version 5.01.13 today the 64-bit version and it worked temporarily I use firefox 40.0.3 but when I tried sandbox the browser it only worked with msn.com than I tried firefox and that worked as a forced programm.
After a reboot the PC chrashed again. I am lucky to have a backup of my system but Sandboxie I will not use it for the time being.While I have a lifetime contract. It worked always ver good maybe I will try it again in the future.

I read that Microsoft is only using their own browser may be that's the problem in Europe ? In 2009 the EC forced microsoft a choice of browsers MS paid as a penalty 497 million euros to Brussels.

Mozilla complains that Edge is after an upgrade to OS Windows 10 the standard browser.

http://www.nytimes.com/2013/03/07/techn ... .html?_r=0

Sandboxie 5.02 now works with Firefox 40.0.3. but make sure that in W10 by standad-apps you change Firefox as the standard
Webbrowser.

[Craig@Invincea]

There is a problem with Chrome 45 (64 bit) on Windows 7 Ultimate 64 bit which doesn't occur with V4.20.

When I start Chrome inside a SandBoxIE V5.02 RC sandbox and go to Virustotal.com check Choose File, choose a file and click Open the whole browser closes.

Hmm, Running Chrome v45.0.2454.85m in Win7 ULT and no issues here...SBIE 5.02rc