Release v1.0.15 / 5.55.15

[DavidXanatos]

Note: A few SBIE2101 warnings were reported between v1.0.10 and v1.0.15 releases, for more info: #1743

This build fixed a couple of security issues and other bugs.

If you have issues with an update installation, just uninstall the previous version keeping the sandboxie.ini and reinstall the new build.

You can support the project through donations, any help will be greatly appreciated.

ChangeLog

[1.0.15 / 5.55.15] - 2022-03-24

Fixed

• fixed memory corruption introduced in the last build causing Chrome to crash sometimes
• FIXED SECURITY ISSUE: NtCreateSymbolicLinkObject was not filtered (thanks Diversenok)

[1.0.14 / 5.55.14] - 2022-03-23

Added

• added notification to warn that the default update checker is lagging behind the newest release on GitHub, to ensure that only bug-free builds are offered as updates #1682
• added main browsers to BlockSoftwareUpdaters template (by Dyras) #1630
• added a warning when Sandboxie-Plus.ini is not writeable #1681
• added clean-up for critical sections (by chunyou128) #1686

Changed

• improved command line handling for breakout processes #1655
• disabled SBIE2193 notification (by isaak654) #1690
• improved error message 6004 #1719

Fixed

• fixed dark mode issue with the new tray list
• fixed not showing a warning when Sandboxie-Plus.ini is not writeable #1681
• fixed issue with software compatibility checkbox (thanks MitchCapper) #1678
• fixed issue with events on box closure not always being executed #1658
• fixed memory leaks in key_merge.c
• fixed issue enumerating registry keys in privacy mode
• fixed settings issue introduced in 1.0.13 #1684
• fixed crash issue when parsing firewall port options
• FIXED SECURITY ISSUE: in certain cases a sandboxed process could obtain a handle on an unsandboxed thread with write privileges #1714

---

This discussion was created from the release Release v1.0.15 / 5.55.15.

[BilleBarrett]

installed this update on several computers
had to reboot and after that it seems to be running OK
Had an older laptop, that I had to do a clean uninstall and reboot then install
OK

[BilleBarrett]

Question where can I find the trace files that are enabled.

[isaak654]

In case you meant the trace log feature of SBIE Plus: TraceLog

[BilleBarrett]

The client sent me an email error from Sandboxie 5.55.15
SBIE 2111. The process is not accessible.$ explorer.exe call Open Process (C00000022) access =00000040 initialized =1
Not sure what to tell him or if there is box left un checked

[isaak654]

The error message SBIE 2111 was introduced in v5.55.17 / v1.0.17, I don't see how v5.55.15 could be involved.

[BilleBarrett]

Yes, he read my email about backing up 17 to 15 and he assumed he has 15. I just updated him back to 15 he’s ok now Remote Desktop Services 517 Miltwood Dr, Greensboro, NC 27455-2709 (336) 988-0891 ***@***.***> ***@***.*** Is your computer up to date and secure “NO” lets talk "Your operating system and Data are only as good as your last backup" Life is not a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside, thoroughly used up, totally worn out, and loudly proclaiming... 'Wow! What a ride!’ From: isaak654 ***@***.***> Sent: Thursday, April 7, 2022 3:23 PM To: sandboxie-plus/Sandboxie ***@***.***> Cc: BilleBarrett ***@***.***>; Comment ***@***.***> Subject: Re: [sandboxie-plus/Sandboxie] Release v1.0.15 / 5.55.15 (Discussion #1725) The error message SBIE 2111 was introduced in v5.55.17 / v1.0.17 <32132af#diff-d7d583c391d8b7aa28609e54893ae147b9720faa68f79bc13e9ff41f510cddec> , I don't see how v5.55.15 could be involved. — Reply to this email directly, view it on GitHub <#1725 (reply in thread)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJ3MQJLDJPEOZKTEDW7DFBTVD4YZ5ANCNFSM5RSHH22A> . You are receiving this because you commented. <https://github.com/notifications/beacon/AJ3MQJITXP7XUVF6WPRH5ODVD4YZ5A5CNFSM5RSHH22KYY3PNVWWK3TUL52HS4DFWFCGS43DOVZXG2LPNZBW63LNMVXHJKTDN5WW2ZLOORPWSZGOAATIX3Q.gif> Message ID: ***@***.*** ***@***.***> >