Sandboxie Support

FF is very unstable with latest beta 5.07.6

Dun wrote:FF is very unstable with latest beta 5.07.6

How so? We haven't noticed anything.

No prblems with FF or anything else, very stable.


Sandboxie 5.07.6 beta | personal lifetime license | Win8.1 x64 | Avira Pro | Firefox 44 x64

5.07.7 has been released.

Craig@Invincea wrote:

Dun wrote:FF is very unstable with latest beta 5.07.6

How so? We haven't noticed anything.

Dunno, I had like 10 FF crashes in an hour. Updated FF, addon and SBIE. No crashes so far

Curt@invincea wrote:5.07.7 has been released.

Thanks for the fix. It works fine now

Just installed 5.07.7 over previous 5.07.05 and now Chrome is giving me the following errors on Windows 10 x64.

Did you delete the contents of your Sandbox? Try creating a new sandbox and running Chrome?

What addons/extensions are running? The winnsi.dll is a function that programs use to call on. I'm suspecting an add-on.. If delete the contents/new sandbox does't work.

Beta 5.07.8 has been released.

Hi. Chrome 48 (32 bit, no extension installed) sandboxed with all 5.07.x versions sometime don't load correctly HTTPS pages (https icon striked out in red, connection not private) even on incognito mode. However, the https connections launched out of the sandbox works perfectly. Thus, i'v come back to the 5.06 version with which this problem does not exist.
Regards

Pelone wrote:Hi. Chrome 48 (32 bit, no extension installed) sandboxed with all 5.07.x versions sometime don't load correctly HTTPS pages (https icon striked out in red, connection not private) even on incognito mode. However, the https connections launched out of the sandbox works perfectly. Thus, i'v come back to the 5.06 version with which this problem does not exist.
Regards

Not seeing it. Delete the contents of your Sandbox. I am having no problems in Chrome 48 or Beta 49 using SBIE 507.8...Win 10 64 (FR builds)

Thanks the problem fixed itself after a reboot. I upgraded to 5.07.8 and have no problems.

dja2k

Updated to 5.07.8. Getting the errors shown below when starting Chrome in Windows 10 Pro. Running HitmanPro.Alert3 as well looks to be the reason for this. Stop Hitman running in Windows Services and the problem goes away. HitmanPro.Alert is showing in Sandboxie's Software Compatibility list.

SBIE2203 Failed to communicate with Sandboxie Service: *GUIPROXY_00000002 - chrome.exe [FF000000]
SBIE2203 Failed to communicate with Sandboxie Service: *GUIPROXY_00000002 - chrome.exe [FF000000]
SBIE2203 Failed to communicate with Sandboxie Service: *GUIPROXY_00000002 - chrome.exe [FF000000]
SBIE2203 Failed to communicate with Sandboxie Service: *GUIPROXY_00000002 - chrome.exe [FF000000]
SBIE2203 Failed to communicate with Sandboxie Service: *GUIPROXY_00000002 - chrome.exe [FF000000]
SBIE2203 Failed to communicate with Sandboxie Service: *GUIPROXY_00000002 - chrome.exe [FF000000]

Edit: A couple of words missing.

For your information, forcing Outlook 2016 to run in the sandbox (v.5.07.6) under Win10 64bit, unfortunately resulted in the following errors:

SBIE2303 Could not hook WSANSPIoctl (888)
SBIE2318 DLL initialization failed for 'ws2_32.dll'
SBIE2303 Could not hook NetUseAdd (999)
SBIE2318 DLL initialization failed for 'wkscli.dll'
SBIE2303 Could not hook SxsInstallW (999)
SBIE2318 DLL initialization failed for 'sxs.dll'
SBIE2303 Could not hook IcmpCreateFile (999)
SBIE2318 DLL initialization failed for 'iphlpapi.dll'
SBIE2303 Could not hook NsiRpcRegisterChangeNotification (999)
SBIE2318 DLL initialization failed for 'winnsi.dll'

Craig@Invincea wrote:

Pelone wrote:Hi. Chrome 48 (32 bit, no extension installed) sandboxed with all 5.07.x versions sometime don't load correctly HTTPS pages (https icon striked out in red, connection not private) even on incognito mode. However, the https connections launched out of the sandbox works perfectly. Thus, i'v come back to the 5.06 version with which this problem does not exist.
Regards

Not seeing it. Delete the contents of your Sandbox. I am having no problems in Chrome 48 or Beta 49 using SBIE 507.8...Win 10 64 (FR builds)

My sandboxes have always active the setting for automatic removal of contents on close.