Sandboxie-Plus v1.8.4

This build fixed a compatibility issue with MSEdge 112.x as well as a few other bugs.

Please review the full Changelog for more details.

Download: https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.8.4

 

What happened in the red box? (sorry, couldn't resist )

 

strange a red box is juts a combination of a orange and blue boxes

 

If you have not set up access to the profile path, you will see the First-run experience screen. (FRE)

MSEdge checks the value of the has_user_seen_fre option in the Local State file and shows the first-run experience screen if not set to TRUE.

You can also try outside the sandbox by setting it to FALSE. (%LocalAppData%\Microsoft\Edge\User Data\Local State)

TRUE -> skips the FRE
FALSE -> shows the FRE
UNSET -> shows the FRE
NOT EXIST (Local State) -> shows the FRE

https://learn.microsoft.com/en-us/deployedge/microsoft-edge-policies#hidefirstrunexperience

HideFirstRunExperience.reg:

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge]
"HideFirstRunExperience"=dword:00000001

SandboxOnly:

Code:

AutoExec=regedit /s "D:\MyPath\HideFirstRunExperience.reg"

 

It could be a bug if you get different results with the same configuration and empty Blue and Red boxes. It can also be caused by a snapshot set in the sandbox.

 

Here to report everything works including my taskbar! Big thanks for the fix. I didn't realize how much I depend on that taskbar to get around.

 

Thank you @DavidXanatos for addressing this issue so quickly. I really appreciate your quick action and I think you are doing a great job in the development
of Sandboxie. Been using it for years, you've made it even better.

 

Does it show up on edge://policy/?

 

What does it say when working in a sandbox? At least "StartupBoostEnabled - false" should appear.

 

My apologies. I feel awful for causing you all the trouble (your kind emoji notwithstanding).
I hope @busy will come up with something OT for @busy , does "busy=offhub" ?

 

@soccerfan I can neither confirm nor deny.

@stapp Can you try applying the registry entry to the sandbox and running MSEdge in that sandbox without clearing the sandbox content?

 

Keep up the good work Mr Xanatos.

It seems that damn near every application wants to be invasive as possible. And the only way the avaerage home user has to prevent your apps from snooping through your data is compartmentalization.

With sandboxie plus, I can deny discord, skype and many others access to my personal files and prevent anything launched by them from accessing the internet on their orders.

 

the strange thing is that for me thay work on 10 and 11 strange...

 

@stapp , I have the same problems with Edge 112 in the red box, the orange box starts without any problems. Now I have tried something with the user profiles and I was able to successfully start the red Edgebox with the following entries:

PreferExternalManifest=msedge.exe,y
NormalFilePath =%UserProfile%

my question to @david or @busy: Is this entry (NormalFilePath =%UserProfile%) in the red Edge-Box even safer than the orange Edge Box without this entry?

Thanks, Sabine
Win11 SB 1.84

 

@Glitzersternchen Yes, although the user profile is readable, it will not have read access to other paths.

Spoiler: Red vs Orange

Red = default block (every path is WriteFilePath [don't allow read, write changes to sandbox] unless it is specifically allowed by a rule.)

Orange = default allow (every path is NormalFilePath [allow read, write changes to sandbox] unless it is specifically blocked by a rule.)

 

Sbie Plus v1.8.4. Testing downloads in BlueBox (privacy enhanced).
I have "RecoverFolder=D:\Download". When trying to download a file, I get this message.

I do not have Desktop as a recover-folder, so this message should not appear!
However, it shows even if I add "RecoverFolder=%Desktop%" to the BlueBox ini.
Workaround: Adding "NormalFilePath=%Desktop%\*" gets rid of the message.
I don't know if this also happened in earlier versions.

 

When opening the "Save as" dialog from within Chrome, it wants to access the Desktop location and gives an error when it cannot access it. Privacy mode blocks access to the true path.

A more restricted rule:

Code:

NormalFilePath=|%Desktop%