Sandboxie-Plus 1.0.22

Discussion in 'Sandboxie (SBIE Open Source) Plus & Classic' started by DavidXanatos, May 10, 2022.

  1. DavidXanatos

    DavidXanatos Developer

    Joined:
    Sep 6, 2006
    Posts:
    2,319
    Location:
    Viena
    hmm... wired that in the more advanced insider builds edge stil works, wil have to set up a non insider win 11 vm to test that
     
  2. DavidXanatos

    DavidXanatos Developer

    Joined:
    Sep 6, 2006
    Posts:
    2,319
    Location:
    Viena

    hmm indeed edge is broken with that update...
     
  3. DavidXanatos

    DavidXanatos Developer

    Joined:
    Sep 6, 2006
    Posts:
    2,319
    Location:
    Viena
    With enabled HW acceleration in edge and disabled win32 hooks in sandboxie (driver restart required) edge works, but than the search window does not as it requires win32 hooks.
     
  4. DavidXanatos

    DavidXanatos Developer

    Joined:
    Sep 6, 2006
    Posts:
    2,319
    Location:
    Viena
    I am not sure about the details of the issue, it seams MSFT changed something with regard to required privileges to access the GPU but strangely as said more advanced insider builds don't have that issue.
    That said, I found a fix add
    PreferExternalManifest=msedge.exe,y
    to the affected sandbox, note though that changing advanced options for that box may remove that preset, hence if the issue comes back check the ini section if the option is still there.
    I'll add that hard coded to sbiedll.dll in the next build
     
  5. focus

    focus Registered Member

    Joined:
    Feb 5, 2007
    Posts:
    503
    Location:
    USA
    Nice.
     
  6. catspyjamas

    catspyjamas Registered Member

    Joined:
    Jul 1, 2011
    Posts:
    288
    Location:
    New Zealand
    Works like a charm David! Thanks so much for checking that out & for providing a workaround. I'll remove the line from the ini prior to upgrading to the next version.
     
  7. stapp

    stapp Global Moderator

    Joined:
    Jan 12, 2006
    Posts:
    23,933
    Location:
    UK
    Using Plus v22 I have 2 boxes, Default and tester.
    I run Edge in tester when I need to.
    Default box runs Vivaldi.

    When I close tester box in the last few days. the flames stay lit and the Sandman status says Edge is running. I have to right click on the Tester box in the taskbar box options to delete content.

    Default box works ok.

    I know I can delete the Plus .ini as I had to before, but thought I'd mention this corruption happening again.

    https://www.wilderssecurity.com/threads/sandboxie-plus-1-0-22.445247/page-2#post-3082800
     
  8. stapp

    stapp Global Moderator

    Joined:
    Jan 12, 2006
    Posts:
    23,933
    Location:
    UK
  9. DjKilla

    DjKilla Registered Member

    Joined:
    Oct 4, 2021
    Posts:
    207
    Location:
    Tampa, FL
    I've noticed a bug in Sandboxie Classic 5.55.22 (64-bit). I always do a clean install and always use the same settings. One of the settings I set is 'Automatically delete contents of sandbox.' I noticed that many times now when I close Sandboxie it doesn't automatically delete the contents of the sandbox so I have to manually delete the contents. Never had this issue with previous versions of Sandboxie Classic. The only programs I have sandboxed is Microsoft Edge, Firefox and Thunderbird. It may be related to stapp's post above. I'll test further and see if it's only Microsoft Edge or one of the other programs I have sandboxed.
     
  10. n8chavez

    n8chavez Registered Member

    Joined:
    Jul 19, 2003
    Posts:
    3,336
    Location:
    Location Unknown
    @DjKilla that's a well know bug that seems to be affecting a lot of us. I do hope it gets fixed.
     
  11. DjKilla

    DjKilla Registered Member

    Joined:
    Oct 4, 2021
    Posts:
    207
    Location:
    Tampa, FL
    Well, did some testing and here's what I found. Using Sandboxie Classic 5.55.22 (64bit) with Microsoft Edge and other programs sanboxed, open any other program then Microsoft Edge. Now close Microsoft Edge and reopen Microsoft Edge again. Now close Microsoft Edge and the other program and the sandboxed contents don't get deleted. This is the ONLY way to get the bug where the sandboxed contents don't get deleted. No other combinations work. It ONLY happens when you open another sandboxed program, then open Microsoft Edge twice and close twice then close the other sandboxed program. Hope this helps and adds some usefulness for a fix!
     
  12. catspyjamas

    catspyjamas Registered Member

    Joined:
    Jul 1, 2011
    Posts:
    288
    Location:
    New Zealand
    By it's very nature, having start-up boost enabled in Edge settings will stop the contents of Sandboxie deleting, because start up boost stops Edge from fully closing. That setting also mucks up CCleaner from cleaning anything Edge related. I keep it disabled, but Edge has, on more than one occasions, re-enabled it on my systems. Grrr. I don't see this as a Sandboxie bug. Not sure if that is a setting you have enabled DjKilla? If not, then your issue may not be related to what stapp is referring to in his post. Having "continue running background extensions & apps when Edge is closed" enabled has also periodically caused problems with some programmes that need Edge fully closed to work too (like Sandboxie & CCleaner). I keep them both unchecked.

    Also today, which I assume relates to Edge getting updated last night, I am having to add: PreferExternalManifest=msedge.exe,y as per David's instructions above in reply 79, to the ini of the Sandboxes I run Edge in. Without adding that line I'm getting the same white box that won't fully load as I got after a Windows Update on my Win 11 machine. Seems to now be affecting my Windows 10 machines, however there hasn't been a Windows Update on those, just an Edge update.

    Looks like David will be adding that fix to an upcoming build, but for anyone else having problems with Edge loading to just a white box all of a sudden - that fix works like magic. I reboot after adding it. Make sure the box is fully emptied first too.
     
  13. DjKilla

    DjKilla Registered Member

    Joined:
    Oct 4, 2021
    Posts:
    207
    Location:
    Tampa, FL
    Yea, I had that stupid start-up boost enabled that caused the issue. I'm positive I had that setting dis-abled but an update must have forced it on again. I'll have to pay attention next time I do an update from the evil empire known as Microsoft.
     
  14. Moose World

    Moose World Registered Member

    Joined:
    Dec 19, 2013
    Posts:
    905
    Location:
    U.S. Citizen
    Salutations/Greetings,
    Brave and LibreWolf work very well with Sandboxie-Plus v1.0.22
    * Brave is slow at starting up, after start it okay!
    * LibreWolf is outstanding, run like a champ!
    * Avast Secure Browser as problems still and has to be copy to the Sandboxie.
    Hope this help somebody out and always the best to everyone.
     
  15. Brummelchen

    Brummelchen Registered Member

    Joined:
    Jan 3, 2009
    Posts:
    5,868
    OT: LibreWolf is a broken Firefox with a lowered security as in Firefox, by prefs. nothing above can fix thoses issues.
    this need more investigations why Edge is spreadings its startup behavior. i read before the automatic startup and Edge insert several entries for autostart. what i can tell you that user is able to disarm those, and sysinternals autoruns can perform it. this behavior is obviously wanted. you can also break the automatic update, Edge will update when you start it.

    for the "startup" feature, MS disabled it in the past, then re-enabled it.
    btw you dont need ccleaner to clean its cache or more, Edge can do itself like any chromium fork. you can select what to clean up when edge is closing.
     
  16. beethoven

    beethoven Registered Member

    Joined:
    Dec 27, 2004
    Posts:
    1,388
    I noticed two new issues starting in 1.0.21 but ongoing after update to 1.0.22:

    1) running browsers unsandboxed to add tabs to the bookmark bar, these new tabs do not stick sandboxed. So I can see my new tab each time I open the browser unsandboxed but once I move to sandboxes, the new tabs are gone. It's almost as if sandboxed and unsandboxed are reversed?

    2) Vivaldi was temperamental in the past but generally speaking ran for me fine. I realise others had problems with this browser but I only encountered this occasionally. For the past week, it has become unusable when running sandboxed. The browser starts and immediately shuts down again.
    Stopping all running processes, running it unsandboxed first, removing using Vivaldi as leading or lingering process - nothing has made a change.
    Chrome sometimes acts the same but usually works fine (though this is the prior Vivaldi behaviour). Firefox so far is the most reliable.

    Edit: Just tried one more thing - based on Bo's golden Rule :thumb: - I set up a new sandbox and surprise, surprise both issues are gone :)
     
    Last edited: Jun 6, 2022
  17. bo elam

    bo elam Registered Member

    Joined:
    Jun 15, 2010
    Posts:
    6,144
    Location:
    Nicaragua
    @beethoven I am going to tell you about something that causes issues between browsers and Sandboxie. This is pretty common. An issue might take place if you set the sandbox were you run the browser not to delete on closing.The issue takes place when you run a browser that has just been updated (outside the sandbox) in a sandbox with old content.

    So, if you don't set your browsers sandboxes to delete on closing of the browser, make sure to delete content before running sandboxed an updated version of the browser. Doing this takes care of the issue and perhaps it is what happened to you.

    Bo
     
  18. beethoven

    beethoven Registered Member

    Joined:
    Dec 27, 2004
    Posts:
    1,388
    thanks Bo - but I don't think this is what happened here. I was used to updating my browsers outside of the sandbox and have the sandboxes to always autodelete. I have been doing this for many years and moving from the old version to plus did not
    change my procedure. But I guess maybe something corrupted a sandbox and creating a new one fixed that problem. I even pay attention to the sandbox showing up as empty after having closed the browsers. I don't really have many special custom features, so redoing it was quick for me and I remembered that your advice to do so had
    worked before for other users.
     
  19. bo elam

    bo elam Registered Member

    Joined:
    Jun 15, 2010
    Posts:
    6,144
    Location:
    Nicaragua
    @beethoven I am glad you are good now. Good seeing you. :)

    Bo
     
  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.