Sandboxie-Plus v1.2.1,v1.2.2,v1.2.3

The Blue Screens are caused only by versions 1.2.0, 1.2.1, 1.2.2 and 1.2.3.

With the still current release version 1.1.3 and all older versions a Blue Screen was never caused.

Yes, I have a memory dump. Should I send it by e-mail?

Edit: Just sent you an e-mail with the download link.

Edit 2: The troubleshooting continues on GitHub: https://github.com/sandboxie-plus/Sandboxie/issues/2035

 

I have found the BSOD issue and it will be fixed in the next build

 

As for now I've had none of the severe issues described above, luckily enough.

Two observations though. With v.1.2.3 the font for menus and also right-click have become almost unreadably tiny and I don't know how to enlarge them. Question: Which system font exactly is there used now as opposed to which system font has been used in the old version? The old one could be tweaked by a sys-utility called "Winaero Tweaker" under Win_10, the new font, I'm afraid, not so much.

The second observation concerns opera-browser since the latest upgrade to v.89 (or maybe v.88 and so I don't know if this is a Sanboxie-issue introduced With v.1.2.2/v.1.2.3 or if it also would have occurred with v.1.1.3.

Anyway, upon start Opera comes up very sluggish, in the tile-bar even (sometimes) stating "Opera - Not Responding" and becoming inaccessible for half a minute or even up to a minute. But then it will slowly complete loading pages - and from then on operate quite normally and also in normal speed. Also this is not entirely reproducible. When closing down (and thereby killing the sandbox) it may happen on repeated fresh starts that the browser will come up normally and without significant delay. So at this time I'm unable to state exactly reproducible conditions for this sluggishness to happen other than that it will mostly happen on the very first start of the browser after system-boot-up.

Addendum: These start-difficulties will even become worse on "Opera Developer v.90" and I will (sometimes) get the following error-message:

 

Global Settings -> Interface Config -> High DPI Scaling & Font Scaling -> Apply
Note: Restart required = Exit tray icon -> call SandMan
Note: resize windows with Scaling change

 

I can't reproduce these CompPkgSvr.exe issues yet

 

Great news! Thank you very much for fixing the BSoD and the hooking error messages.

These seem to be the error messages caused by using "UseRegDeleteV2=y".

Please have a look at this post:https://www.wilderssecurity.com/threads/sandboxie-plus-1-1-2.445628/#post-3088160

 

Ok, I have to apologize. I didn't follow the course of events closely enough for some time. Font size problem solved. Thanks for bringing me up to date.

 

Thanks again "APMichael" for pointing this out. Yes, it seems You are correct. After taking those ..DeleteV2-statements out these error messages didn't occur again - at least for now. I was unaware of them being obsolete to be honest.

 

Ok, I have to apologize. I didn't follow the course of events closely enough for some time. But as "APMichael" has pointed out already these seem to be correlated to the "UseRegDeleteV2=y".-statement. To be honest I've been unaware that those ..DeleteV2-statements have become obsolete in the meantime.

And yet after removing those ..DeleteV2-statements I still can see some sluggishness in the startup, especially with the "Opera Developer v.90"-version. So the jury is still out if this is some newly introduced incompatibility by Opera-v.89/v.90 or if this has also a correlation with ..DeleteV2. But my current impression would be that those are separate issues. While the error-messages displayed in my previous post seem to be gone without ..DeleteV2 it would appear that the observed initial sluggishness, especially of "Opera Developer v.90", remains unchanged.

 

Hmm, I have UseFileDeleteV2=y & UseRegDeleteV2=y with my Global Settings. Just saying.
1.2.3 - W10 21H2 (19044.1826)
Note: I do not run Opera.

 

Looks like I have to apologize too! I haven't really been keeping up with these different threads and posts, plus I've recently made the move from Sandboxie Classic to the Plus version, so I might not know what I'm talking about. Lol! Just being honest! Anyway, I saw everyone talking about the file/program CompPkgSvr.exe. If I remember correctly, I only started getting these error messages after adding my programs (Thunderbird, Firefox, Microsoft Edge) to 'Start Restrictions' and selecting 'Allow only selected programs to start in the sandbox'. I believe the error messages included the following additional programs which are CompPkgSvr.exe, identity_helper.exe, RuntimeBroker.exe which appeared when using Microsoft Edge. I also got a plugin-container.exe error message when using Firefox. I looked up what these programs are and they seemed safe since it looks like these programs are needed when using the above programs. I added these programs to the 'Start Restrictions' and now I don't get these error messages anymore. Like I said, this might be unrelated since I'm still new to using Plus but it's what I discovered and might help.

 

FWIW ~ I have

Code:

SbieCtrl_HideMessage=1308, RuntimeBroker.exe [Edge]
SbieCtrl_HideMessage=1308, identity_helper.exe [Edge]

Curious, under your Edge sbox - Compatibility Templates -> Miscellaneous -> Block commom telemety processes = enabled or disabled?

 

In case you had not seen this or find it helpful:
I came across the following link about comppkgsrv.exe (which seems to be triggered
with chrome browser + facebook/youtube). It is apparently present since Win10, 1809+
https://forums.tomshardware.com/threads/component-package-support-server.3655228/

 

I have it disabled.

 

The setting "UseRegDeleteV2=y" is not obsolete, it is a newly introduced setting (since v1.1.0) that is still in the status "experimental". I assume that David will soon fix the problem with the error messages.

(The other new setting "UseFileDeleteV2=y" works fine for me so far without any error messages.)

 

Yes, I have it disabled, too. Disabled is default. I was thinking of enabling it, as test. Thanks

 

I can not reproduce this comppkgsrv issue with out without booth delevev2 options
i assume it happens only when a empty box is initialized first

 

Probably so b/c I have my boxes always deleted after a browsing-session is terminated. The error-messages turned up immediately on starting "Opera Developer v.90" in a freshly initialized box - but only with ..DeleteV2=y as it now seems.

 

I ran some tests in my VM and found out what are the conditions for the error messages:

The error messages caused by "UseRegDeleteV2=y" (not by "UseFileDeleteV2=y") are only triggered if the application is forced into the sandbox and the sandbox is cleaned automatically.

This way I can reliably reproduce the error messages:
- Install the latest Firefox (102.0.1, 64-bit) into a clean VM running Windows 11.
- Install the latest version of Sandboxie (v1.2.3, 64-bit).
- In Sandboxie.ini, add "UseRegDeleteV2=y" under [GlobalSettings], "AutoDelete=y" and "ForceProcess=firefox.exe" under [DefaultBox].
- Start Firefox and open a PDF via CTRL+O.

 

One more question though. After I've learned about these new settings it has turned out that with a scaling of 125% things are a bit too small, still. However applying 150% (which I've applied now) shows things one tick too large. Is it therefore possible to declare some individual numeric value (like e.g. 140%) for that scaling-factor by the user? Perhaps directly at some proper location in the ".ini"-file?

 

Have you played with DPI Scaling #79. For example: for "Qt"...I'm 100%. For "Native"...I'm 150%.
For Scaling -> Apply -> Exit tray icon -> call SandMan.
For resize window -> resize window -> X close window -> Exit tray icon -> call SandMan.
.
My preference in Vintage View. Have you played with "View"...just to see.

Spoiler: Vintage View

~ look in AppData\Local\Sandboxie-Plus\Sandboxie-Plus.ini
I've not played as you suggest. IDK if 140 works from Sandboxie-Plus.ini

Spoiler: Sandboxie-Plus.ini

 

I'm afraid I do not quite understand. Are you saying that High DPI can be scaled differently for "Native" and "Qt"? Cause I can see no difference with either setting, furthermore there is no scaling-factor to declare.

The only scaling factor I can see is for "Font scaling" and can only be chosen in fixed steps of 25%, regardless of whether the above DPI-scaling is for "Native" or "Qt". And as for "Font scaling" 100% is unreadably tiny, 125% still too small and 150% a tad too large. So 140% would seem to be about right and I will give it a try in Sbie-plus.ini. And thanks again for the helpful advice.

Addendum: Yes, it seems 140 as entry for FontScaling= in Sandboxie-plus.ini in my case does the trick!

 

@algol1 Yes, on my machine Qt varies vs. Native.
for example: Qt with 100% vs. Native with 100%

Yes, on my machine I run Qt with 100%. For Native I need 150%.
For Scaling -> opt change -> Apply -> X close SandMan windows -> Exit tray icon -> call SandMan.
For resize window -> resize window -> X close SandMan windows -> Exit tray icon -> call SandMan.
as always, your mileage may vary

Okay, Thanks

 

In build 1.2.4 you can enter any number in the font scaling field 75 up to 500