Sandboxie Plus 0.7

Discussion in 'Sandboxie (SBIE Open Source) Plus & Classic' started by DavidXanatos, Feb 15, 2021.

  1. algol1

    algol1 Registered Member

    Joined:
    Aug 10, 2020
    Posts:
    136
    Location:
    Vienna, Austria
  2. catspyjamas

    catspyjamas Registered Member

    Joined:
    Jul 1, 2011
    Posts:
    157
    Location:
    New Zealand
    State of the nation with my machines and Sandboxie:

    Machines 1-5 with Sandboxie 5.49.7: Edge v 90.x will open with a hang (which is easily remedied by disabling hardware acceleration). Chrome opens with an extremely minimal hang. Vivaldi and brave both require the --no sandbox change to the target to allow the browser to work since they updated to v 90.x.

    Machine 6 with Sandboxie 5.49.7: Edge WAS refusing to open with an error message when it changed from v 89.x to v 90.x, however since installing the CU (KB 5001391) on 28th April, Edge v 90.x will now open with a hang just like machines 1-5, which I find very interesting. However installing this KB has NOT fixed the error window that pops up (see the image in the linked to post) with version 90.x of Chrome, Brave and Vivaldi, which I cannot bypass. The browsers will flat out not open at all. I have tried the --no sandbox target for all three browsers on machine 6 - this change allows Chrome and Brave to open as per machines 1-5, but Vivaldi still fails with the same error window as linked to. Disabling hardware acceleration makes no difference.

    As stated previously. ALL browsers worked flawlessly with Sandboxie 5.47.9 on all machines with all Chromium version 89 and below. As each browser updated to 90.x, they would fail.
    All six machines are configured 100% identically down to the last software and setting. The only difference is the CPU and GPU - machine 6 is the only one with 11th gen CPU & Iris Xe graphics. All machines are malware free, and all have clean SFCs. All on Win 10 19042.964, with Windows Defender.

    I have tried all Sandboxie releases as far back as 0.7.2/5.49.0 on machine 6 but am getting the same results. I'm not prepared to try a version lower than that because 5.49 has security fixes. The common denominator in every case for me is moving from version 89.x to 90.x of Chromium browsers.

    @DavidXanatos - I hope this helps. Sorry for the headaches this must be causing you!
     
  3. la5vna

    la5vna Registered Member

    Joined:
    May 2, 2021
    Posts:
    2
    Location:
    Norway
    Hi all
    Brave Version 1.23.75 Chromium: 90.0.4430.93 (Official Build) (64-bit) and SB Version 5.49.7 (64-bit) is working with this switch:
    --disable-gpu-sandbox
     
  4. la5vna

    la5vna Registered Member

    Joined:
    May 2, 2021
    Posts:
    2
    Location:
    Norway
    Sorry, my mistake it is not .
     
  5. Stelica

    Stelica Registered Member

    Joined:
    Nov 10, 2014
    Posts:
    33
    Location:
    Romania
    I'm sorry about the problems some users have. I have no problems with my three browsers. I use firefox, default browser, edge 90 and chrome 90 latest update and sandboxie classic 5.49.7. It is true that I use a dedicated sandbox for each browser. I learned many things from Bo and I want to thank him very much for indications and tutorials!
     
  6. algol1

    algol1 Registered Member

    Joined:
    Aug 10, 2020
    Posts:
    136
    Location:
    Vienna, Austria
    Would you mind humoring us by sharing the Sbie-ini-part of the dedicated Chrome-sandbox and its options according to Bo's template?
     
  7. catspyjamas

    catspyjamas Registered Member

    Joined:
    Jul 1, 2011
    Posts:
    157
    Location:
    New Zealand
    Hi. Not meaning to assume your reason for asking, but if it is to find a workaround to the error with v 90.x of Vivaldi and Brave (and v 90.x Chrome on one of my machines, though few users seem to be affected on Google Chrome so far...) - I can tell you from trying on all six of my machines that a dedicated sandbox vs default box makes no difference to whether the browsers work. If it's for other reasons you're curious, then feel free to ignore my comment.
     
  8. Melionix

    Melionix Registered Member

    Joined:
    Jun 22, 2020
    Posts:
    31
    Location:
    Earth
    Not the guy you're responding to, but I wish to see just to see if you've done any hardening that I haven't.
     
  9. algol1

    algol1 Registered Member

    Joined:
    Aug 10, 2020
    Posts:
    136
    Location:
    Vienna, Austria
    I don't use Vivaldi or Brave and therefore have the problem only with Chrome itself which I AM using on rare occasions for compatibility on certain poorly programmed websites which won't support Opera or load certain videos therein (I'm an Opera guy which will also run into this issue when its next stable release will change to Chromium v.90. How would I know for sure? Well, the advanced "developer-version" already on Chromium v.91 already does!). And so far - after all I've tried - I have to admit that I also have little hope that a dedicated sandbox would resolve the problem.

    But if @Stelica claims that he could resolve it - or didn't run into in the first place - by using very special tailored settings for that dedicated box - who am I to say it wouldn't be possible that they could do the trick? So if I knew about those special settings I could try them out. It's that simple.
     
    Last edited: May 3, 2021
  10. Stelica

    Stelica Registered Member

    Joined:
    Nov 10, 2014
    Posts:
    33
    Location:
    Romania
    I didn't claim to solve anything. I had no problems and I did not make any special settings. In my sandbox I only have restrictions for internet acces and start / run acces and direct access for uBlock Origin!
    If someone has no problems, it does not mean that something has been changed!
     
    Last edited: May 3, 2021
  11. Rasheed187

    Rasheed187 Registered Member

    Joined:
    Jul 10, 2004
    Posts:
    14,542
    Location:
    The Netherlands
    I'm also having no problems with Sandboxie 5.45, Vivaldi, Edge and Firefox run just fine on Win 10 1909. I did have to disable hardware acceleration for Edge to make it launch more quickly. But I'm probably not having any problems because I'm using older versions of Sandboxie, Windows and Vivaldi.
     
  12. catspyjamas

    catspyjamas Registered Member

    Joined:
    Jul 1, 2011
    Posts:
    157
    Location:
    New Zealand
    I was just trying to save you wasting your time and going to unnecessary bother, but of course you're free to try whatever you want for yourself.

    Stelica isn't using problematic browsers, except for Chrome which at this point, is barely causing problems for anyone (for me, Chrome v.90 on fails on only 1 of 6 laptops, and reading through the comments here it seems that for most Chrome v.90 is fine). So it's not surprising he/she is having no problems - his/her experience matches most here. Vivaldi and Brave on v90.x are another story though. Sorry to hear Chrome is borked for you too. I use it for one website only which Edge isn't supported on, and Firefox doesn't work as well with.

    For what it's worth the only "tweaks" I make are to enable auto-deletion of the sandbox, and to enable immediate recovery (some releases immediate recovery it is already checked, but I had to enable that on a clean install of 5.49.7). I've unsuccessfully tried it out of the box with clean installations, and with my only 2 tweaks, and also with and without dedicated sandboxes. It needs to work out of the box though, as not every user is a tech head like many on here! It would be awesome if someone found a successful tweak to help David fix it for the next release. So far the only success I've had is the --no sandbox target change in the browser properties. As I wrote above, even that didn't work for Vivaldi on one of my machines.

    I note Rasheed is using Vivaldi fine on 5.45, however 5.45 is a very old version without the security fixes applied in later versions. Personally I'm not prepared to use insecure versions (not saying others are wrong to do so - that's their choice), I'd rather just stick to a new versions and browsers Sandboxie is working with (browsers I don't have to apply the --no sandbox change to). I've tried as far back as 5.49 (with no success), which is the last build with a security fix applied.
     
  13. catspyjamas

    catspyjamas Registered Member

    Joined:
    Jul 1, 2011
    Posts:
    157
    Location:
    New Zealand
    All good. I'd be interested in seeing that too actually.
     
  14. Rasheed187

    Rasheed187 Registered Member

    Joined:
    Jul 10, 2004
    Posts:
    14,542
    Location:
    The Netherlands
    I have got no problems with using old versions. I just noticed that Vivaldi 3.8 won't run with Sandboxie 5.45 so I'm glad that I haven't upgraded Vivaldi yet, because there is no downgrading option. I always first install new versions of Vivaldi as a portable version to test stuff, this way I can avoid having to perform a reinstall. Newer versions of Sandboxie may or may not give any problems, so I always wait for a while.
     
  15. FredB

    FredB Registered Member

    Joined:
    Apr 27, 2020
    Posts:
    7
    Location:
    Australia
    I have been struggling with browsers based on chrome v90. My portable apps chrome worked OK but brave browser wouldn't.
    Portable chrome is a 32bit version. So I have tried the 32bit versions of brave and vivaldi and they seem to be working.
    Hope this is of use to others.:)
     
  16. n8chavez

    n8chavez Registered Member

    Joined:
    Jul 19, 2003
    Posts:
    2,968
    Location:
    Location Unknown
    Has anyone been able to successfully get Vivaldi (Chrome < 90 build) to run inside sbie? If so, how?
     
  17. deugniet

    deugniet Registered Member

    Joined:
    Nov 25, 2013
    Posts:
    989
  18. Brummelchen

    Brummelchen Registered Member

    Joined:
    Jan 3, 2009
    Posts:
    4,005
    fully sandboxed without any rule or exception. Even when setup crashed at last in the box vivaldi has been fully installed. But vivaldi need as standalone (=portable) full rights, it will end immediately without. same for user folder installation - quit after init.

    i need to verify with windows 10 (all builds here). you forgot to tell about your used windows, i assume windows 10, but defender is also good on windows 8.

    if you can eliminate impacts of HMPA, adguard, mullvad you maybe can narrow the problem. but i have doubt people will be able to reproduce your configuration and more. its all on you.
     
    Last edited: May 9, 2021
  19. DavidXanatos

    DavidXanatos Developer

    Joined:
    Sep 6, 2006
    Posts:
    1,123
    Location:
    Viena
    Short update:I was very busy with my day job jast month so I hadn't much time for anythign at all, sory for that, i hope in the next week i'll have time agian for all the new bugs with chrome 90 and alike, stay tuned...
     
  20. Mr.X

    Mr.X Registered Member

    Joined:
    Aug 10, 2013
    Posts:
    3,973
    Location:
    Mexico
    Lol ok thanks
     
  21. stapp

    stapp Global Moderator

    Joined:
    Jan 12, 2006
    Posts:
    17,417
    Location:
    UK
    Thanks for the update on your situation.
     
  22. plat1098

    plat1098 Registered Member

    Joined:
    Dec 19, 2018
    Posts:
    1,130
    Location:
    Brooklyn, NY
    Sandboxie continues to be a great complement to Firefox 88.1. Good to hear back from you. :)
     
  23. henryg1

    henryg1 Registered Member

    Joined:
    Jun 14, 2020
    Posts:
    186
    Location:
    uk
    Phew :thumb::thumb::thumb:
     
  24. sevenstar

    sevenstar Registered Member

    Joined:
    Oct 19, 2010
    Posts:
    37
    Any Insight into why I'm unable to force thunderbird properly in a sandbox? When I try to start Thunderbird sandboxed, Rpcss.exe and SandboxieDcomlaunch.exe don't run. Thunderbird is listed as running in the sandbox. I'm using Sandboxie-Plus v0.7.4
     
  25. The Count

    The Count Registered Member

    Joined:
    Jun 13, 2016
    Posts:
    176
    Location:
    France
    Where in sbie settings would I find this switch?
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.