Sandboxie Plus 1.0.0

This options menu is really cool!
The button for 'Start Restrictions' may be more appropriate in green perhaps (just nit picking)?

 

No, not green - better red.
I am joking a little bit, but indeed it would be more consistent in red than in green because the button concerns restrictions - that means something that shall not run.

 

I see your point @Peter 123

 

Well that depands on the sellected radio button one mode is allow all except i.e. block something and the otehr is block everythign except, i.e. allow only something
so than the icon should change teh color?

 

This could drag into an 'opinion war', please leave it be.
I'm sure there are other issues you are working on
to resolve for the next build that take precedence!

 

OK, so in other words, it might work for some people and for others not. About Vivaldi, it's quite easy to test. Just install it and surf to a couple of websites, exactly as you would do on Edge, Opera and Chrome. Installation should go rather quick and obviously it's safe to use. And of course it should be installed outside the sandbox, but you probably already knew that.

 

OK thanks, then I misunderstood. I thought that sandboxing was completely disabled and Sandboxie would only virtualize software installation similar to Symantec Workspace Virtualization for example. I wonder if this less secure mode would fix the problem with browsers like Firefox and Vivaldi starting to malfunction after a while when they are installed inside the sandbox.

https://en.wikipedia.org/wiki/Application_virtualization

 

Yummy! Thanks a lot!

 

Is anyone noticing Plus is using slightly more cpu than prev. versions? Now, pls. don't poo-poo this but the prev. version to this one had the cpu never going above 0% on idle. This version is 1-2% when system is idle. No boxed browser would be open then.

I exited out of Plus and cpu immed. went to 0% in Task Manager--simple cause and effect. This is a fairly strong cpu so it's all relative. Is there anything about this latest Plus version that would justify the admittedly slight increase in cpu demand while idle?

Edit: another crash. Only things I recall doing are exiting out of the Plus UI and Disabling Forced Programs.

Spoiler

 

BSOD today Windows 10 with PAGE_FAULT_IN_NONPAGED_AREA with Sandboxiw Plus version 1.0

 

If you read previous posts you will see that you are not alone in this.

 

You refer to this?

https://github.com/sandboxie-plus/Sandboxie/issues/1389

- fixed BSOD issue introduced in the 1.0.0 build [#1389](https://github.com/sandboxie-plus/Sandboxie/issues/1389)

https://github.com/sandboxie-plus/Sandboxie/commit/cf166ed79e71862ebd59c4629c2d1e90959f63ac

 

In the latest Windows 11 (version 21H2 build: 22000.348 Sandboxie Plus (ver 1.00 and 0.9.8.4) does not work. Firefox (94.0.2 (64 bit) launches, but I don't see it in Sandboxie among the running programs. The yellow frame is not visible in Firefox either. I tried a completely clean install for both versions, but that didn't work either, it didn't run the program, the situation is the same. I usually start with a batch file:

Code:

"C:\Program Files\Sandboxie-Plus\Start.exe" "C:\Program Files\Mozilla Firefox\firefox.exe" -no-remote -P Karcsu

or:

Code:

Target: "C:\Program Files\Sandboxie-Plus\Start.exe" "C:\Program Files\Mozilla Firefox\firefox.exe" -no-remote -P Karcsu
startup location : "C:\Program Files\Sandboxie-Plus\"

On the first startup it works a few times, then it doesn't, if I run it in two copies, the second one starts correctly. I do not understand.
It doesn't run other browsers (edge, chrome) too, but it does run other programs.

I also tried "run default web browser" within Sandboise, but it still doesn't run in sandboxie.

 

It seems the sandboxie classic thread is closed. So I have to report it here.

In Sandboxie Classic 5.53.3, Win 11, Firefox 94.0.2 doesn't run in a sandbox. I have tried it Forced. I have tried it non-forced. I have tried setting Firefox as the default browser and using Sandboxie systray menu > Firefox sandbox > Run Web Browser. They all try to run WerFault (the windows error reporter)

 

Sorry for that to many channels of communication + poor social skills a good combination doe snot make.
So the BSOD's reported in github seam to have the same reason and I'll release soon a new build where this should be fixed.

 

No its its not relates to the BSOD, but i think its the new OpenClsid handling which I'll also roll back in the next build

 

Thanks for your update.

 

Fixes should not be features, they are fixes.

The validity is as write on the shop page
Small: 1 year, after expiration new features get disabled in all builds
Medium: 1 years, after expiration new features get disabled only in builds newer than the expiration date
Large: 2 years, new features added after expiration don't get unlocked but exclusive features added before that date remain functional even in newer builds