Sandboxie Plus 0.7

FWIW ~ Edge 90.0.818.39 & Chrome 90.0.4430.72 ...okay, for me, with 5.49.7 UI
0.7.4 - 20H2 (19042.867)

 

Yup, for me it's just one machine that it fails with, see my reply to n8chavez, who is also having the issue.

 

I was sharing my experience with 5.49.7 UI with 0.7.4 + 20H2 (19042.867).
I'll try my spare dust collector machine.
Edit:
FWIW ~ Edge 90.0.818.39 & Chrome 90.0.4430.72 ...okay, for me, with 5.49.7 + 20H2 (19042.867).
FWIW ~ my Edge 90.0.818.39

 

To confirm: on here: Edge v. 90--opens to a blank white page via New Box and Default Box configurations.

Can't run latest Edge in Sandboxie 5.49.7 right now. Windows 10 19043.928.

 

This sounds different to the error I posted about. On my machine it is failing with, I get a very specific error window, which I cannot progress from. Chromium v 90.x browsers will not open at all, even to a white page. They open instantly when not under Sandboxie. It is only one of six machines I'm getting this with though, which is weird because they're configured identically down to the last setting and soft.

But on my other five machines, I am seeing what you describe (hanging on a white window on launching), but only with Edge v 90.x. Try giving it a few mins to sort itself out, as that is working for me on said machines. For me it takes anywhere from seconds to 2-3mins to load, but it will eventually. This behaviour for me is only when it's launched in Sandboxie.

 

Long time SBIE user but new to the forum.

I've been having problems with the last several releases of Chromium Edge being a little slow loading sandboxed but the latest release it now takes Edge about 16 seconds to load. Outside the sandbox Edge pops right up. Since I haven't seen any other complaints it must be something specific to my system.

The details...
Windows 10 20H2 19042.867 X64
Sandboxie Plus 0.7.4/5.49.7, I use the classic interface.
Chromium Edge 90.0.818.39

What I have tried...
Clean installed Sandboxie Plus.
Deleted the Edge profile and started fresh.
Deleted sandboxie.ini and started fresh.
Tried running Edge from the default box, normally Edge has a dedicated sandbox.
Disabled extensions in Edge.

None of the above has made any difference in Edge's load time.

Any suggestions on what else to try?

 

Curious, what are your System settings here > #178 (click pic to expand thumbnail)

 

My settings are the same as yours, except I have hardware acceleration enabled. I turned hardware acceleration off and this time didn't get the hang on launching Edge v 90.x in Sandboxie. Looks like that one setting might be the culprit for the Edge hangs if it's repeatable. I'll test it out on the other four machines later.

Sadly changing this doesn't fix the error I posted about here on machine number 6. I'd already tried disabling hardware acceleration on Chrome on that one as part of my troubleshooting process, but it made no difference. I just tried it in Edge on the off chance and no luck there either. I cannot get past that error box.

 

Thank You!

Disabling hardware acceleration did the trick.

Apologies to the moderators for making my first post in the wrong forum.

 

Since disabling hardware acceleration stops the Edge hangs on launching (introduced with Chrome based browsers updating from 89.x to 90.x), perhaps just perhaps, the CPU/GPU combo of the one machine I cannot launch any Chrome based browsers on at all, is not entirely irrelevant after all? (Disclaimer - I am by no means as tech savvy as most on here). It's pretty much the only difference between that machine and the other 5 that are working.

The machine in question has an i7-1165G7 with Iris Xe and no dedicated GPU. My other five machines are a mixture of various CPUs and GPUs. Anyone else with an ultrabook with an i7-1165G7 and Iris Xe? Can you launch Chromium browsers running 90.x under Sandboxie without getting this error? I'm not talking about hangs, I mean with the error and nothing launching full stop.

 

Suddenly when sandboxed in Sandboxie Plus my Brave browser gives an error page every time.
I suppose Brave updated and now it's not compatible with Sandboxie + any more.
Unsandboxed it works normally.

 

@LodeHere Looks like same error as as I'm getting, except on sandboxie classic 5.47.9 I don't even get as far as you - just the error window.

 

Works perfectly now with hardware acceleration disabled. However, this was working with it prior to the Chrome update.

 

Thanks Bo for all of this feedback. I think I might make a new sandbox for Vivaldi, but currently files are loading normally again. So it might have been a temporary problem. BTW, now that I think of it, I give "direct access" to the Vivaldi profile folder, so can I then simply delete the whole sandbox without losing any Vivaldi settings? Of course I have already moved all of my downloaded files from this sandbox to my real system.

 

Edge/Chrome/Brave v90 hang with 5.49.7 and hardware acceleration on #795
https://github.com/sandboxie-plus/Sandboxie/issues/795

 

Appreciate the info, bjm_.

For now on here, Edge is out of the sandbox with hardware acceleration enabled again, until this issue is resolved.

 

I've never run Edge with 'Use hardware acceleration' on.
I've never run Edge with 'Startup boost' or 'Continue running background' on.
I've never run Edge Services on.
I'll run Edge toggles off, if I can.
Just me.

 

Yes, you can Remove the sandbox, and won't lose your settings (as long as you gave direct access to the Vivaldi profile folder and the folder is outside the sandbox). If Vivaldi is installed inside the sandbox, you lose the settings when you delete the sandbox. Also, if Vivaldi is installed inside a sandbox, you gained nothing by giving direct access to the profile folder since all changes stay in the sandbox when a program is installed in a sandbox..

Bo

 

And I was thinking of returning to the classic again... so thank you much for sharing that. (I still have the installer for it on my laptop. No sense using it to replace Sandboxie Plus with it.)

In Sandboxie Plus via Help > Visit Support Forum one gets here:
https://forum.xanasoft.com/

I made an account for it many hours earlier today, and am still waiting for the confirmation email before I can log in and post. Nothing seems to be happening there.

For now I made Chrome (with Sandboxie Plus) my default again.

 

Well you're doing better with it than me. I can't use any chromium browsers running 90.x with Sandboxie on this one laptop. I just installed Sandboxie plus 0.7.4 to see if I could at least use Chrome (since you can) and it's a no go on that too. Same error, browser won't load at all past the error box. Not surprised, they share the same core components, it's basically just the UI that's different. Back to Sandboxie Classic 5.4.7 (just because I know it better). Using it with FF, which has no probs at all.

EDIT: Actually I have just discovered Brave 1.23.71 has the same problems as LodeHere in #187 on the machines that I initally said were having no problems with Chromium 90.x. They still load Edge and Chrome OK though. On said machines, Brave browser opens but is completely unusuable with the "Aw Snap" message, error box after error box from Sandboxie, and the extensions get eaten one by one with repeated error messages. Disabling hardware acceleration in Brave does not change this. This is new behaviour, Brave was working with Sandboxie 5.49.7 before the browser updated.

 

I had nothing to set in Sandboxie Plus, it worked out of the box. (In Sandboxie Classic I had to add brave.exe and give permissions to Chrome.)
I'm using Window 8.1 (with StartIsBack so it looks like a modernized Windows 7. Had 10 for a few days but liked 8.1 better).

I don't know much about these things. Hopefully this gets fixed, especially for you. I keep Chrome as default in the mean time. In Chrome -as in Brave- I use Starpage.com as default.

 

Leak report

Sandboxie-Classic-x64-v5.49.7, Windows 7 64-bit

Launched Pale Moon (fresh install) and found cert9.db and blocklist.xml leaked in AppData folder:
...AppData\Roaming\Moonchild Productions\Pale Moon\...

Sure, all other files were contained, but still...

 

I seem to be having the same issue as you. Only seems to be brave browser. Chrome & Edge are working OK sandboxed??

 

Simply remove the "Firefox_Phishing_DirectAccess" template from the settings of the sandbox you are using.