Sandboxie Plus 0.7

Ok hmm... may be its not a gpu issue but indeed related to this stack protection...

Could you please test if the last sophos sbie build works, I would expect also no, but just to have it verified that the issue is really caused by this new HW security feature and not related to any of my changes.

Also try running these browsers with the --no-sandbox flag, iirc chrome wont start on the sophos build without that anyways anymore but try it also with my latest build just to see what happens

 

Hi David. No old Sophos version doesn't work either - that was already bust with Chromium as you note. I went back as far as your 5.46 classic already too, but they also fail. It should be noted that 5.49.7 worked beautifully with all Chromium browsers right up until the browsers updated to version 90 - they failed on the next launch, no other change on my system took place at the time. They browsers all installed outside of Sandboxie too, btw. Unsinstalling/reinstalling including of a brand new .ini file also made no difference.

The --no-sandbox flag works with Chrome and Brave on the 11th gen machine and 5.49.8. It does not work with Vivaldi though, I still get the same error window. This was the same on version 5.49.7 btw. The only change 5.49.8 has made to my 11th gen machine is fixing the white box hang with Edge when hardware acceleration is on. I note a comment above asking to try --disable-gpu - tried and no luck either.

 

@DavidXanatos
I can confirm that the problem also exists with the old Sophos-version (just tested v.5.33-3) and that neither the "--no-sandbox"-switch nor the "--disable-gpu"-switch will make any difference.

 

David, if you are around this weekend, I can do a teamviewer with my personal machine.

I had the issue with Vivaldi and Brave, then with the v0.7.5 worked then stopped, without me updating the machine. Bizarre indeed. Just send a note here, it should ping my email and then we can get this testing on.

 

We can do some testing my time zone is CET hos wabout today between idk. 15 and 18 CET? when would it be good for you

 

Thanks to both of you for all the work and feedback and very weirth that Intel's 11th gen CPU gives this problem, can't this "stack protection" feature be turned off or something? But anyway, I installed the newest Sandboxie on Win 10 and it does indeed fix the problem with Vivaldi 3.8 and I'm sure Vivaldi 4.0 will also work correctly. This is of course on the Intel Core i5 10th gen CPU.

 

hi
is there a way to disable to check for update in sandboxie classic ?
thanks

 

I am sorry I did not see this till now, I am free when you are...

email me directly w h o da t1 @@ hotmail

remove spaces, add the .com

I can also be awake late for me

 

click the menu > help >search for updates and then the button "never"

 

hi @Brummelchen

may i know where sandboxie save such settings?
thanks

 

[UserSettings_<number>]
SbieCtrl_NextUpdateCheck=-1

Sandboxie only uses the INI file to store its settings, Settings can also be accessed with the menu > configuration > edit

Thx stapp

 

hi
thanks!

 

I still can't sign on to my firefox sync account from a sandboxed firefox with SB+

 

@DavidXanatos
Sorry for having to report that even the upgrade to the latest release Sbie+v.0.8.0 didn't resolve any of the issues here.

At least on my "11th gen Intel"-System latest versions of Chrome and Opera-browsers will continue not to launch producing "Werfault.exe" errors.

But thanks for your effort anyway.

 

@algol1
that was to be expected, as i havn't mentioned fixing anything chrome related in the changelog still havn't head access to an 11th gen machine
btw dies disabling things in windows deffender devide guard or so helps in any way?
I would have thought that it might be possible to disable this new mitigations globaly for the entire windows

 

Hi @DavidXanatos No there are no different settings in any section of the whole Windows Defender App between my 11th gen and other machines. So no particular settings to turn off/on. As part of trouble shooting I had already tried fully disabling Windows Defender as a test to see if Chromium 90 would load in Sandboxie, but it made no difference. I just tried again but no difference (using 5.49.8 - not updated to the 5.50 just yet).

I think the HW changes in 11th gen CPUs and the affected AMD CPUS are kinda 'baked in' as it were. I'm not sure if there is a setting in the Chrome flags that might help though.....

Fully understand that this issue may take some time to resolve, esp without affected hardware at your disposal. We can still run Edge and FF perfectly well.

 

either its sb+ related or your used box (emptied?).
this is sb (not +) 5.49.8, a clean box, a profile with connection to sync (the menu tell me so) - i am logged in right now in the box. Windows 8.

an earlier test was also negative, but that was another sandboxie build, you can find my answer in this sub forum.

#edit

sandboxie 5.50.1 after update (not plus)

to be specific - when loggied in outside i could use it also inside. logged out and loggin in in sandboxie failes - it accepts login data and the 6 numbers, but not looged in.

if i try with a fresh profile logging in works. so at least it must be some setting in your (my) profile or interception from an extension.

 

@DavidXanatos
after having upgraded to Sbie+ v.0.8.1 I observed the following differences:
Immediately after the upgrade when trying to start a sandboxed browser this triggered Sandman to open up in full window before anything else. After that Opera v.75 started as expected (using Chr.v.89) whereas Chrome all of a sudden didn't give any error messages - but didn't launch either without any further commentary.

Only after the 1st re-boot that changed for the previously observed behaviour. That is Sandman didn't pop up windowed but remained in the SysTray and then Opera would start normally whereas Chrome refused, this time showing the by now notorious
"WerFault.exe (18412): SBIE2101 Object name not found: Unnamed object, error OpenProcess (C0000022) access=001FFFFF initialized=1"
error message.

In the meantime and while introducing improvements to Sbie+ unrelated to possibly 11th-gen-Intel problems I would like to remind you - if I may - of 2 requests/suggestions for the GUI I've made earlier:

1. could you please augment the right-click-context-menu for the tray-icon by the option to delete the contents of the current/last sandbox directly from SysTray? Just in case Sbie upon close should have been unable to auto-delete the box-content the user by this new menu-option could avoid having to open Sandman first and then right-clicking the box in there and then again choosing "Delete Contents".

2. Especially now when testing various options with malfunctioning browsers changing settings to and fro it would be really nice to have an option in the "Forced Folders/Forced Programs"-section to JUST PAUSE a certain path or program-name from being forced to run in Sbie - instead of having to delete this path/program first and then after testing having to browse for that path in Explorer from scratch in order to re-declare it in the forced-list.

Let me explain that is is not enough to un-/re-check the "forced"-checkbox in the bottom "template-section" as for example for testing the compatibility of Opera I have currently installed 3 instances of that browser (the working/production version, the latest stable version not launching any longer and also the advanced developer-version). And yet there is only one template-setting for the main Opera- or Chrome-instance while the others need to be managed through the "Forced Folders"-section - which can become a little tedious in the current situation. So I would appreciate if you could consider implementing these two suggestions.

 

1. I'll improve the tray menu in one of the later build with much more options

2. you could create local templates for each browser location a custom one, anyhow I'l look intom improving the settings UI may be ba adding checkboxes to most lists to togle configured paths on and off

 

Spoiler: related pic

Maybe, observed similar with my v0.8.1 over-install ~ machine Restart sorted v.0.8.1... for me

 

Checkboxes in the forced-folders-section do sound like a brilliant idea! Thanks a lot.

 

Hmm, I didn't even receive that warning-message as depicted, Sandman would only open up unsolicitedly - and yes, after the 1st re-boot everything went back to normal.

 

I just tried out the latest sandboxie plus. I still can't log in to my firefox sync from a sandboxed firefox.

 

You already wrote that. didn't you read my test above? Its in your profile, either firefox settings or extension. You cannot expect from David to reproduce it without your used profile. create a new one, find the differences in prefs, disable extensions.