Sandboxie Technologies (SBIE Open source) (VERSION 5.33.6 ONLY!)

Discussion in 'Sandboxie (SBIE Open Source) Plus & Classic' started by bo elam, Apr 22, 2020.

Thread Status:
Not open for further replies.
  1. Sandboxer

    Sandboxer Registered Member

    Joined:
    Sep 22, 2020
    Posts:
    19
    Location:
    Sydney
    After turning off forcing-browsers-to-open-in-a-sandbox:
    * Vivaldi --disable-gpu launches Vivaldi very quickly.
    * Sandboxie Vivaldi --disable-gpu fails, with the same stuttering cursor as before.
    But worth trying.
     
  2. stapp

    stapp Global Moderator

    Joined:
    Jan 12, 2006
    Posts:
    23,936
    Location:
    UK
    Tried that and no joy as @Sandboxer found out too.
    Thanks a lot for idea though, much appreciated.

    I have no issues running Vivaldi as long as Sbie isn't involved :(
    However new Edge Chromium runs great under Sbie, but it is only on Chromium build 85.0.5641.51 whereas the Vivaldi snapshot contains build 86.0.4240.38 (a beta build)
     
  3. RioHN

    RioHN Registered Member

    Joined:
    Mar 14, 2017
    Posts:
    117
    Location:
    Here
    I don't currently have access to my Win10 machine (can test it later) but on a Win7 pro SP1 VM I found snapshot 3.4.2049.2 works fine in Sandboxie 5.33.6. If it helps I installed Vivaldi outside of Sandboxie for all users (So C:\Program Files etc)... Then ran sandboxed. I was unable to install 3.4.2049.2 directly into a sandbox.
     
  4. stapp

    stapp Global Moderator

    Joined:
    Jan 12, 2006
    Posts:
    23,936
    Location:
    UK
    Be interested if you get this to work on your Win 10 2004 version this way. I tried portable version but no joy.
    I always install browsers outside of Sandboxie first.
     
  5. RioHN

    RioHN Registered Member

    Joined:
    Mar 14, 2017
    Posts:
    117
    Location:
    Here
    I currently run Win10 Pro 1909 so it may not be a fair test. I'll take a look when I get back though.
     
  6. stapp

    stapp Global Moderator

    Joined:
    Jan 12, 2006
    Posts:
    23,936
    Location:
    UK
    I just tried on another machine with Win 10 2004 build 19041.508.
    That machine still has stable Vivaldi (3.3.2022.47)running and Sbie works no problem with it.

    I downloaded standalone (portable) snapshot 3.4.2049.2. Opened it and Vivaldi ran fine on its own.
    I then ran it Sandboxied and it wouldn't open.
     
  7. Krabbath

    Krabbath Registered Member

    Joined:
    Jun 24, 2020
    Posts:
    49
    Location:
    Earth
    FWIW: I can confirm this. Sandboxie 5.33.6 (64-bit), Windows 10 Home 2004 build 19041.508:

    I installed "Vivaldi.3.4.2049.2.x64.exe" (Language: English US; Installation Type: Install standalone) outside Sandboxie. It starts without issues on my system.

    Sandboxed started (first without switches, then with the switches --disable-gpu and --disable-update), Vivaldi shuts down immediately without showing its program window, only Vivaldi's "update_notifier.exe" remains open.

    Sandboxie copies Vivaldi's profile folder on my PC into the sandbox, I have not checked if it is complete.

    If the latest Chromium version causes this situation, other Chromium-based web browsers might also refuse to open sandboxed with the next updates.
     
  8. focus

    focus Registered Member

    Joined:
    Feb 5, 2007
    Posts:
    503
    Location:
    USA
    Chromium - stable version: 85.0.4183.121 (September 23, 2020)

    Anyone try this out yet with SBIE?
     
  9. Brummelchen

    Brummelchen Registered Member

    Joined:
    Jan 3, 2009
    Posts:
    5,871
    85.0.4183.102 as the previous build is running a full featured profile in sandboxie 5.43.5 / Win8 flawlessly. Incl. GPU processing shown in chromium task manager, no spiking.

    but after downloading two files:
    downloads have finished successfully.

    https://community.sophos.com/sandbo...al-ole-init-hook-failed-errors-from-sandboxie

    could be the download-jingle → no audio. youtube audio+video playing.
     
    Last edited: Sep 24, 2020
  10. stapp

    stapp Global Moderator

    Joined:
    Jan 12, 2006
    Posts:
    23,936
    Location:
    UK
  11. RioHN

    RioHN Registered Member

    Joined:
    Mar 14, 2017
    Posts:
    117
    Location:
    Here
    Just to confirm, I see the same thing on 1909, Vivaldi immediately closes.
     
  12. focus

    focus Registered Member

    Joined:
    Feb 5, 2007
    Posts:
    503
    Location:
    USA

    I see this after an Edge update today:

    "Microsoft Edge is up to date. Version 85.0.564.63 (Official build) (64-bit)"

    Which is based upon Chromium version 85.0.4183.121.

    Works fine with SBIE 5.33.6.
     
  13. Buster_BSA

    Buster_BSA Registered Member

    Joined:
    Nov 29, 2009
    Posts:
    748
    Considering this thread is about Tom's Sandboxie fork, everything related to version 5.33.6 should be talked in other thread.
     
  14. stapp

    stapp Global Moderator

    Joined:
    Jan 12, 2006
    Posts:
    23,936
    Location:
    UK
    Most people in this thread are using the Sophos 5.33.6 build. No need for yet another Sbie thread.
     
  15. Buster_BSA

    Buster_BSA Registered Member

    Joined:
    Nov 29, 2009
    Posts:
    748
    But this thread is about Tom's fork, not Sophos stuff.
     
  16. stapp

    stapp Global Moderator

    Joined:
    Jan 12, 2006
    Posts:
    23,936
    Location:
    UK
    As yet there is no fork, and 5.33.6 is the most used build mentioned in this thread.
    If it turns out that any Chromium based browser is unable to run under the supervision of Sandboxie because of the 86.0.4240.38 build of Chromium then it could have a big impact.
    I have raised a bug with Vivaldi and will report back when I get any info.
     
  17. paulderdash

    paulderdash Registered Member

    Joined:
    Dec 27, 2013
    Posts:
    4,639
    Location:
    Under a bushel ...
    And, having 5.33.6 installed, I don't really want to be monitoring the other thread when I have no intention of pursuing that fork.
     
  18. stapp

    stapp Global Moderator

    Joined:
    Jan 12, 2006
    Posts:
    23,936
    Location:
    UK
    Remarks about moderation removed.
     
  19. plat

    plat Registered Member

    Joined:
    Dec 19, 2018
    Posts:
    2,233
    Location:
    Brooklyn, NY
    Opera updated last night to 71.0.3770.171, a small update it looks like. No changelog yet on their Blogs page. Sandboxie continues to work well on here in a basic-use sense. Takes about 2 seconds to open sandboxed w/ i9 processor.

    Hopefully, this compatibility issue betw. Vivaldi and SBIE gets ironed out.
     
  20. Krabbath

    Krabbath Registered Member

    Joined:
    Jun 24, 2020
    Posts:
    49
    Location:
    Earth
    Opera names as chromium version v85.0.4183.102 for this release, at least in its User agent identification string (see [Menu] > Help > About Opera --> Browser identification).

    There are so-called developer versions of Opera. The current developer version (73.0.3820.0 - 2020-09-22) uses, according to its corresponding blog post, Chromium 87.0.4252.0
     
    Last edited: Sep 25, 2020
  21. Krabbath

    Krabbath Registered Member

    Joined:
    Jun 24, 2020
    Posts:
    49
    Location:
    Earth
    Thank you very much.
     
  22. plat

    plat Registered Member

    Joined:
    Dec 19, 2018
    Posts:
    2,233
    Location:
    Brooklyn, NY
    Yes, that's where one looks for the versions but I wasn't sure if Opera was using the very latest chromium--Opera stable that is. I see now that it doesn't so the post of focus' remains unanswered.

    Thank you for the clarification.
     
  23. Krabbath

    Krabbath Registered Member

    Joined:
    Jun 24, 2020
    Posts:
    49
    Location:
    Earth
    You are welcome.

    ---

    By the way, Opera's developer versions can be installed alongside to its standard versions, the standard installation remains untouched.

    I had therefore considered installing Opera's current developer version in addition to my Opera standard version, but from the Opera forums I know that browser developers make individual adjustments, which can also affect the chromium functionality, which means that even if Opera Developer with chromium 87.0.4252.0 were to run under the supervision of Sandboxie, this would not necessarily allow conclusions about Vivaldi + Sandboxie.

    stapp's direct clarification with the Vivaldi developers via bug report is therefore the best solution in my eyes.
     
  24. g17

    g17 Registered Member

    Joined:
    Sep 30, 2017
    Posts:
    101
    Location:
    MI
    Apologies in advance if this question is common knowledge...

    I'm running v5.33.6 on Win10 Pro v2004 OS build 19041.508

    Lately (can't say when exactly), when I open or close Chrome I briefly see a cmd prompt window with some bold yellow text in it. This seemed odd to me and malware like, so I got concerned. It closes too fast to read.

    After some fiddling I finally captured the window and this is what I see.

    cmd window in chrome.JPG

    Good news is, it's not malware. Bad news is, I'm not smart enough to fix it. I know people who are though.

    If I force chrome to open sandboxed, will it update and will those updates stick after deleting the SB contents?

    Seems unlikely, but is there a way to give chome update priveleges in the default box? I did not see this at first glance, maybe I can add manually?

    Last, how do I make this go away? I disable UAC since I'm sandboxed and hate pop ups.

    Thanks all, sorry if this was a stupid question.
     
  25. Peter 123

    Peter 123 Registered Member

    Joined:
    Feb 1, 2009
    Posts:
    596
    Location:
    Austria
    When I started to use Chrome, exactly the same window flashed for a second (in my case with the program name GoogleChromePortable.exe).

    The simple solution for me was: to determine Chrome as a forced program in the sandbox (so that it automatically starts within it) [Sandbox Settings --> Program Start --> Forced Programs --> Add Program --> chrome.exe]

    (Probably I owe this solution to the Forum here, but I do not remember when and where exactly. ;-) )

    I should clarify that I use the portable version of Chrome but I assume that it works for the installed version too.

    As there is no automatic update for the portable version, the question does not arise for me. But I imagine that with the installed version of Chrome it works like for other browsers: Yes, I think that updates will happen within the sandbox. But whenever you close the sandbox (and delete its contents) the update is gone. ---> In order to keep an update you should make it outside of the sandbox.

    Maybe that it is necessary to add something manually in the Sandboxie configuration so that the update of Chrome works.(?) Perhaps other members can tell you the details. But as mentioned above: to my mind it should be preferred to update a browser outside of the sandbox (except for testing purposes, of course).

    Try it like suggested above: Add Chrome to your forced programs in your preferred sandbox.
     
    Last edited: Sep 26, 2020
Thread Status:
Not open for further replies.
  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.