Sandboxie Plus 1.0.7

64bit classic version. Was an update nothing else changed on my settings.

 

Need a little help here. Does Write/ClosedKeyPath=HKEY_USERS work? I'm still able to access the mounted registry of 2nd box despite having this line under 1st box.

 

huh hows that possible your windows must have a csrss.exe process else it wouldn't work
does this com again when you try to restart the driver?

 

I'm still trying to find the issue causing the UAC popup. I did try the DependOnService.reg but it didn't seem to work. I did notice something strange though. If I uninstall Sandboxie, then try to install Sandboxie after rebooting, I get the same issue as Freki123 post above. I have to wait about 20-25 minutes after rebooting, then Sandboxie installs correctly. I still get the UAC though after installing Sandboxie and rebooting. I'm starting to wonder if it might be a Microsoft Windows 10 update that's causing these issues with Sandboxie. Tomorrow (second Tuesday of every month) is when Microsoft releases Windows updates. After installing the updates, I'll see if anything changes when installing Sandboxie. There's definitely something going on, I'm just not sure if it's something thats changed in Sandboxie or Microsoft Windows.

 

Just had the UAC pop up again during boot-sequence with "DependOnService.reg" installed and "Win32k hook" set to ON again.

 

I only got the error once and it looked so broken for me I redeployed a backup instantly.

I just uninstalled 5.55.7 on my admin account (keeping the ini file), rebooted and instantly got a UAC from "Service Device Manager configuration Tool" to allow sc.xxx (forgot exact extension sadly) to run.
No screenshots possible at that stage sadly. After clicking "yes" it opens a black window like for cmd prompts for under a second and that's it.
Rebooted pc again and hoping sandboxie under SUA behaves better now.

If it doesn't help I will try on of your fixes.

 

I was hoping to find an answer to a problem I just encountered when installing latest firefox 96.0 64bit. and sandboxie 5.55.7 (64bit).When opening firefox sandboxed,it tried to open and never loaded anything,just a message saying to wait the program might respond and it never did.After 15 min.,I closed program.I also am running Eset smart security premium.I have allowed everything in eset to allow firefox and sandboxie to run.Firefox will open unsandboxed.Firefox 95.0.2 (64) and Sandboxie 5.55.7 (64) worked great.I don't know really if it is a firefox problem or sandboxie problem.I did install sandboxie 5.55.5 and the latest firefox 96.0 (64) it also wouldn't opened.Any help would be appreciated.

 

So far FF 96.0 64bit and Sandboxie 5.55.7 64bit are working for me (haven't installed the monthly windows update so far but that shouldn't make a difference I hope).
Maybe try to run FF in the sandboxie "default box" (or a fresh created on) and create a new firefox profile (just for testing and see if it works then).
For other suggestions wait for the pros

 

Hi
it's a silly question
I have installed on a laptop sandboxie classic 5.55.7 and when i click check for updates , i get 2 identical windows check for updates , and with the older versions it doesn't detect updates
thanks

 

i think i have found the issue with the csrss.exe the function to find its PID was failing when very quickly while it was operating new processes were created, as it can happen on boot.
Will be fixed in the next build

 

Ah well done @DavidXanatos

I haven't had any UAC prompts at all on any machines with win32 hooking disabled. It's only been 2-3 days but that's a promising sign that that is the cause as you thought. I've had UAC prompts on the Windows 11 machine with hooking enabled though (I need that enabled for Find on Page in Edge to work).

I haven't tried the reg fixes you put on the previous page. I'm nervous to change the registry, and I note it didn't stop the UAC prompt for algol1.

 

Why, just make a system image, that's it.

 

On Widows 10 64bit, I'm bouncing around with Vivaldi, Edge, and FF using UBO and Privacy Badger. Would it be advisable and/or necessary to disable these extensions running inside Sandboxie plus? Would these extensions even serve a functioning benefit under the protection of a sandbox? Also inquiring if there may be compatibility issues with Brave and Bitwarden (installed on all of the aforementioned browsers) sandboxed. Thanks in advance, and my apologies if I've overlooked these same compatibility topics that may've been previously addressed. Bon jour.

 

Looks like v1.0.8 is on the way and might include improvements to the portable mode.
In v1.0.7, I am using PortableRootDir=0 (with my own FileRootPath) and PortableStop=0
My question is about PortableStart.
PortableStart=? What are the possible (and default) values and their usage/meaning?

 

PortableStart and PortableStop controll if you get a message box before sandman asks for admin rights and try to start stop the service and driver in portable mode

 

In my setup, I have:
PortableRootDir=0
PortableStop=0

I do not get any prompts to start the service or driver (exactly what I want).
What is the value of PortableStart (is it 0 or 1 or 2) in this scenario?
My sandboxie-plus.ini does not have a PortableStart line! That is why I ask.
Thanks.

 

1 to start the service and produce an uac prompt
0 to do nothign without running driver no sandboxing

 

Thank you!!

 

Help! First time using SBIE Classic upgrading from SBIE

Win ver 21H2 (OS Build 19044.1466)
FF 96.0.1, SBIE Classic 55.55.7

1) FF is not opening sandboxed
2) DefaultBox > Delete Contents > There is nothing to delete but
after restart Windows there is files and folders Why?

Thanks

FF crash:

Delete Contents AFTER restart Windows:

 

You did an uninstall of the old sandboxie (maybe keeping the ini file) and rebooted. After that you started the install of classic right?
Running Shadow Defender ? Maybe disable it just for testing (till you know that sandboxie works.)
It's working for me 96.01 and even on 5.55.3 (just saw I have to update now)

 

That is correct. So for now I'm back to Win32_hook=OFF and those reg-hacks removed again. As a consequence Chrome won't start with HW-Acceleration=ON (default setting), though.

As an OFF-TOPIC sidenote, if you're uncomfortable making changes to the registry you might want to have a look there:
https://www.resplendence.com/registrar
It is an excellent shareware registry-editor that allows far superior handling of the registry than regedit. It can even remotely load (broken) registry-hives from different machines over the network (admin-access to them provided) to fix them remotely as well as making snapshots of your running present machine's reg-hive with the ability to restore those later in case you've made an unfavorable change. END OFF-TOPIC

 

need more explanation, that sentence makes no sense this way
W10 20H2 (20H1 to install), 5.55.7 classic - firefox + full featured profile = no issues

in most cases firefox will fail when another 3rd-party dll injection (most scenarios: security programs) is done. do you have installed another beyond windows defender?

 

Hi
Just wondering if anyone else on here using portable apps chrome browser with sandboxie?
I'm trying to get it to direct access bookmarks but can't seem to get it to work?
I'm forcing the chrome.exe and have the direct access chrome bookmarks app template selected but new/deleted bookmarks don't get persisted.
Do I need to force the PortableGoogleChrome.exe or just the chrome.exe?
Any help appreciated thanks.

Chrome Version 97.0.4692.71 (Official Build) (32-bit)
SB+ version 1.0.7
Windows 10 Home 21H2

 

The templates only work if you have Chrome installed by default. For the bookmarks you need the following files:

Code:

OpenFilePath=chrome.exe,C:\Users\[your user name]\AppData\Local\Google\Chrome\User Data\Default\Bookmarks*
OpenFilePath=chrome.exe,C:\Users\[your user name]\AppData\Local\Google\Chrome\User Data\Default\Favicons*

You need to adjust the path in these two lines according to your portable installation and then add them to the Sandboxie.ini file (in the corresponding sandbox configuration).