Sandboxie Plus 0.7

Thank you, that worked.

 

OK thanks, there is definitely something wrong, because I just saw that I can't install any extensions anymore, I get some error. To clarify, Vivaldi is installed outside the sandbox because both Firefox and Vivaldi will start to malfunction when they are installed inside the sandbox, at least on my system. This strangely enough doesn't happen with portable versions though. Portable versions of Firefox and Brave run just fine.

 

Hi,
Edge//Brave v90 hang with 5.49.7 and hardware acceleration.
Addditional Error with deleting sandbox browser will not fully delete.
ect.....

Solution uninstall completely for the time being.......

 

Thunderbird (78.10) not working



although I rarely use it Sandboxed so I do not know when the problem started.

Googling the error message didn't give me a solution.

 

I'm now running the 21H1 preview (Insiders Beta) and the basics are all working perfectly right now--Firefox 88 + Sandboxie Plus 0.7.4 | 5.49.7.

Microsoft Edge still has the hang w/hardware acceleration enabled. If it's disabled, it opens instantly in Default Box mode but still hangs in New Box mode. Unique to here or..?

 

Like I said in the Edge thread, I have checked out Edge v89 and I noticed that it didn't start up that fast when running under Sandboxie 5.45, but I still need to test it without hardware acceleration. Outside the sandbox it works smoothly.

 

Understood, Rasheed. Did you happen to try the Plus version 5.49.7 yet? With this build, Edge opens literally instantly but only with H/A disabled. It's like there's no obstacle hardly (talking about Sandboxie). I was getting a 4-5 sec delay with the Sophos build myself. That's not something I will tolerate anymore.

Yes, if you try it with- and without hardware acceleration and on the latest Sandbox version, what are your experiences then? I actually run Firefox sandboxed, not Edge so much anyway. It was a way to evaluate some things on the latest 21H1 preview/Insider build 19043.962.

 

Turning off hardware acceleration works for me, but I have a more general problem. When Edge was failing, I got the following notification:



which I could not select or close because



was completely hidden behind it, and could not be selected even from Task View. So I had to crash the notification from the Task View. Any other way to get round this?

 

Thank you.

I was able to download 5.33.6 directly from Sophos.

 

To be honest, I see no reason to upgrade Sandboxie to 5.49.7 at the moment. But I did notice that even with Sandboxie 5.45, Edge will only start up quickly when hardware acceleration is disabled. Browsing goes smoothly with or without hardware acceleration. So this is good enough for me, I will use both Firefox and Edge purely for testing, I'm using Vivaldi 100% of the time.

 

Contrary to what I've read so far I have to report that also Chrome won't launch any more with Sbie-Plus v.0,7.4

In a Sbie-popup window when trying to launch Chrome there will appear an error message - and then nothing happens, that is no launch of Chrome.

"WerFault.exe (11992): SBIE2101 Object name not found: Unnamed object, error OpenProcess (C0000022) access=001FFFFF initialized=1

Oh, and I might add that Chrome will refuse to launch sandboxed with above cited error - regardless of whether or not hardware-acceleration is turned on in Chrome.

 

Ok so which version broke the compatibility?
v0.7.3 and later
or already an earlier version?

 

I'd suppose that it has been some recent Chrome-update that broke the compatibility.

Went back to v.0.7.3, same behavior, no launch.

Then went back to v.0.7.2 - no launch either - but: there came up no Sbie-popup-window yet to tell me about why and hence displaying the above cited error message.

 

Hi @DavidXanatos I have reported this a few pages back, see here. Same behaviour for me with all chromium browsers once they update from 89.x to 90. It is not a sandboxie version thing as they all worked on 5.49.7 prior to the browsers updating (updating outside of a sandbox obv). Disabling hardware acceleration makes no difference to this problem.

 

Hey all, been using Sandboxie Plus for a while and loving it. When Windows 10 upgraded this morning I started getting this message when I started up a Sandboxed Chrome instance...

WerFault.exe (10880): SBIE2101 Object name not found: Unnamed object, error OpenProcess (C0000022) access=001FFFFF initialized=1

Nothing else changed that I know of and I'm using SB+ 07.4. Chrome doesn't start up anymore. Tried Uninstall/Reinstall SB+ but nothing seemed to do it.

Thoughts or ideas to fix this welcome!

Thank you!

-Harmony

 

Just to give a positive message to David :

For Google Chrome - using the portable version - I cannot confirm the reported problems.
I just updated from version 88.0.4324.150 to 90.0.4430.85 (outside of Sandboxie of course).
Chrome continues to start and to work in the sandbox as it did before. (Using Sandboxie Classic 5.49.7 / 64-bit).

 

Hi, I have Windows 10 Pro 20 H2, Sandboxie Classic 5.49.7 / 64-bit. All my browsers, firefox, edge and chrome works well sandboxed with hardware acceleration enabled!

 

Ok, I can confirm now that this issue came with Chromium-engine v.90 as my current stable Opera browser works still fine using Chromium v.89 while the latest Opera-developer-browser uses Chromium v.91 and won't launch any more either!

 

All my browsers, firefox, edge and chrome are up to date. No problems! But I use only Sandboxie Classic 5.49.7 not Sandboxie Plus

 

And while we're at it looking into this matter I'd like to ask @DavidXanatos for two improvements for the Sandman-UI:

1. Please add an immediate right-click-option to the Sandman-tray-icon offering to delete the content of the current sandbox right from the icon without having to open Sandman first.

2. For testing situations like the current one it would be nice and helpful to have a new option added to the "Forced Folders / Forced Programs"-section that would allow to just pause (or comment out) certain folders / programs temporarily from being forced to run within a sandbox - so that they could be re-activated after testing or at a later time without having to delete that path altogether in the first place and therefore having to browse and search for that path again before it could be re-enabled within the field of forced folders / programs.

Of course these would be minor improvements that do not fall into the "most-urgent"-category but would be nice to have in the long run. So many thanks in advance to David should they be implemented in the near future.

 

Nice for you - but doesn't make any of the problems go away which have been reported here. Usually the users posting here are Sbie-veterans and know what they are talking about.

 

Maybe I can't call myself a Sandboxie-veteran. I have been using Sandboxie for 5 years!

 

@algol1:
I know how annoying it can be when someone tells you: "Well, I don't have the same problem as you. So it must have to do with your computer, your own mistakes etc."
But I think whether Stelica's and surely not my intention was to doubt the existence of the problem that you or other users experience. It simply may be of interest (especially for the developer) to know that some people are not affected of the issue, as it could be an indication that the problem may only have to do with a certain version of a software, certain settings etc.

 

@Peter 123
No offence taken, especially since you reported about a different setup with the portable version and even did bother to report the exact Chromium-version-number of the engine used in there. Because by now it seems evident that the problems - where they occur - seem to be related to a change in Chromium-engine used when changing from v.89 to v.90.

 

@algol1 Things are even more complex each and every different program you have installed on your PC, could make the difference. Even if your hardware is identical. Sometimes it is almost impossible to pinpoint it exactly. Without diving in the PC and installation in person. Even an uninstall can have a catastrophic failures following with a program not related.
Just had this lately, new PC installation FF worked well, Win update, still OK, but after preinstalled office and McAfee removal, FF didn't start anymore with MS VC library missing error. Search the net, there is no real answer. Workarounds but no answers.
Like I had those unity issues for some time, David didn't have any idea and I doubted more and more it is SBIE itself. Then after one Win Update it worked suddenly. No change in SBIE. David can't fix none SBIE issues and I guessed it wasn't SBIE for sometime, even if it worked without sandbox.
That's life.
It is not unimportant to know if another setup has no issues. However without at least Win and program versions the info is not enough. But here the info was giving all.
One more point think that some functions of SBIE might be sensed by the programs as evil, think of copyprotections not allowing drive emulators, or certain other programs while running. So many possiblities...
Honestly the veteran status is no go. The oldest still existing setup I have is 3.20.01 from ~2007, so what does that make me, Senior Veteran? This fact doesn't rate my today comments valuable, smart or dumb.
Peace and happy hunting the bugs, wherever they are, but in the end David can only fix SBIE issues.

1 Would it be an option to open the GUI, if you anticipate that you want to delete immediatly? However if David adds more in the right click menu, it would be good to have those options in a Submenu, as we already have two options, which you might click accidentialy when you try to open the interface.

2 I would copy the sandbox and experiment with the second one. Alternative, in Sandman you can go to the option dialog, last entry is the INI and edit it. put a ; in front of the option you want to remove, apply and run the program again. You can keep the options open and adjust as you go.