Sandboxie Plus 1.0.6

SBIE2224 crash error on VNC-Viewer.exe [VNC_Viewer]

This error is always reproducible when I try to copy to the clipboard any document, file... on the host, then I get this error automatically and the connection closes from the client computer (viewer.exe) to the host where the vnc server (host) is located. I work on a lan where both the client and the server are running windows 10 and my sabdboxie is v5.55.5 64bit.

As always, thank you very much for continuing to develop this wonderful software.

 

I went back to 1.0.5 because of Edge sandbox not auto deleting as well. I used the classic interface in the 1.0.6 package.

 

is the auto delete related may be with edge processes staying active?

 

After installing latest classic version I lost all bookmarks in Vivaldi. Edge was okay.

 

@j9ksf do you use auto delete of the sand box as well?

 

I do use auto delete. Just reverted to 5.55.5 and that is okay.

 

I have found the issue causing the bookmarks to get lost, will be fixed in the next build

 

Not yet, also not sure if its related,

What I see in your last screenshot is that some msedge.exe's are still running, hence the issue is not the box deletion failing, but the last msedge not terminating and staying open.

Can others confirm that this is the failure mode they experience.

 

Yes.

 

I have a sandbox for SumatraPDF, sbie terminates adequately all pdf processes and quick as usual but now the sandbox is not emptied.

Edit: I tested for other dedicated sandboxes for other programs and same behavior. Processes end quickly as usual but the sandboxes are not emptied.

 

Can you please try the attached driver, note that its not signed and requiters test mode,
alternatively you could try toe driver from 1.0.5 with the test from 1.0.6
This should fix the bookmark issue. Can you plese test if on your system this also solves the browsers not closing?

 

Its not a zip but a txt.file.

 

Come on just change the file extension, ie, delete .txt part only in the filename.

 

I think you need to download, rename to delete the '.txt' extension
and find the driver inside the zip file.

 

because you cant upload zips, just rename it to zip

anyhow, I think I pinpointed the not closing issue its related the this bugfix:

fixed issue with SeAccessCheckByType and alike

Now that said the bugfix is correct, but apparently some of these calls actually failing was beneficial to chromium browsers closing.
I'll need to look into adding a chromium special case handling and fail the right call at the right time.

 

I have pinpointed the issue, without the mentioned bugfix instantiation of Windows.UI.Notifications.ToastNotificationManager failed early, with it it almost works, just well it dead in a later call.
There is a workaround:
ClosedRT=Windows.UI.Notifications.ToastNotificationManager
this will be hard coded in the next build

 

I have an interesting problem after updating an older piece of software (PopPeeper 4.5.2 -> 5.2.2), maybe someone can help.

Win 10 pro, 21H2 19044.1415, SBIE classic x64, 5.55.6

The program is set to start at windows startup (it worked fine before the upgrade).

It now does not start, but when I start it manually after boot it works fine.

I do have it configured as a forced program to start under SBIE, and also listed under restrictions. This was working fine before the update.

I removed the entries and added them back, and this odd poppee~1 file shows up when I do so:



I was getting another error that said something about <sandbox:delete this operation requires admin privileges> but I did not save it.

I went and changed the ownership to give users full access and the error went away.

The item does not show in my startup folder, but there is an option in the software to start at windows start which I have enabled. I can also see it as a startup item in autoruns.

Sorry for the rambling note, any ideas? This is not a huge deal as I can start it manually but it worked before. I don't see any errors in my event log related to this. Could it be a boot order issue? Don't want to mess with that.

UPDATE: when I remove the program from the forced programs list it does not start at boot (as expected) because it is still restricted.

When I remove the restrictions it still does not start so this is likely not a SBIE issue.

 

Just a thought:
If you uninstall PopPeeper 5.2.2 and reinstall 4.5.2, does it work "as usual"?
If so, then the new version may be the culprit.

 

I have no problem running Pop Peeper Plus Pack/Pro. I've been using Windows 10, and recently upgraded to Windows 11, and both stated up just fine in Sandboxie

I'm using a .bat fine scheduled to run at startup with "START C:\Progra~1\POPPeeper\POPPeeper.exe /min"

My SBIE config for PP is:

Code:

[Mail]

Enabled=y
ConfigLevel=9
AutoRecover=y
Template=SkipHook
Template=LingerPrograms
Template=AutoRecoverIgnore
BorderColor=#00ffff,off,6
ForceProcess=poppee~1.exe
ForceProcess=poppeeper.exe
NotifyInternetAccessDenied=y
NotifyStartRunAccessDenied=y
BoxNameTitle=n
ProcessGroup=<StartRunAccess>,firefox.exe,poppee~1.exe,poppeeper.exe,RuntimeBroker.exe,rundll32.exe,PPhelper.exe,waterfox.exe
ProcessGroup=<InternetAccess>,firefox.exe,poppee~1.exe,poppeeper.exe
ClosedFilePath=!<InternetAccess>,InternetAccessClosedFilePath=!<InternetAccess>,InternetAccessDevices
AutoDelete=y
LingerProcess=poppeeper.exe,poppee~1.exe
CopyLimitKb=117917
LeaderProcess=poppeeper.exe
LeaderProcess=poppee~1.exe
DropAdminRights=y
OpenFilePath=poppeeper.exe,C:\Program Files\POPPeeper\Mail\AntiJunk.db
OpenFilePath=poppeeper.exe,C:\Program Files\POPPeeper\Mail\addrbook.inx
OpenFilePath=poppeeper.exe,C:\Program Files\POPPeeper\Mail\Spam\data.db
OpenFilePath=poppeeper.exe,C:\Program Files\POPPeeper\Mail\Inbox\data.db
OpenFilePath=poppeeper.exe,C:\Program Files\POPPeeper\Mail\Investments\data.db
OpenFilePath=poppeeper.exe,C:\Program Files\POPPeeper\Mail\Misc\data.db
OpenFilePath=poppeeper.exe,C:\Program Files\POPPeeper\Mail\Receipts\data.db
OpenFilePath=poppeeper.exe,C:\Program Files\POPPeeper\Mail\Personal\data.db
OpenFilePath=poppeeper.exe,C:\Program Files\POPPeeper\Mail\School\data.db
OpenFilePath=poppeeper.exe,C:\Program Files\POPPeeper\Mail\Work\data.db
OpenFilePath=poppeeper.exe,C:\Program Files\POPPeeper\Mail\Server\data.db
OpenFilePath=poppeeper.exe,C:\Program Files\POPPeeper\Mail\Sent\data.db
OpenFilePath=poppeeper.exe,C:\Program Files\POPPeeper\Pro\AntiJunk\
OpenFilePath=poppeeper.exe,C:\Program Files\POPPeeper\Pro\AntiJunk.dll
OpenFilePath=poppeeper.exe,C:\Program Files\POPPeeper\poppeeper.ini
ClosedIpcPath=!<StartRunAccess>,*

 

@DavidXanatos could you add the last digits to version number so we can have it in the About window please?

Spoiler

 

@DavidXanatos do you have a driver x86 to test this?