Sandboxie-Plus v1.3.4

This build improves window class name handling, resolves issues with WinUI apps and windows 11 explorer , it also fixes various minor issues and adds some improvements.

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

Changelog
Added

• Added NoRenameWinClass to the Plus UI
• Added Windows.UI.* to the list of hardcoded well-known classes to resolve issues with WinUI apps #2109

Changed

• NoRenameWinClass now supports wildcards

Fixed

• fixed issue with default box not being detected on start #2195
• fixed move sandbox menu issue #2225 (thanks okrc)
• fixed issues with stale data in Sandboxie-Plus.ini #2234 (thanks okrc)
• fixed autostart issue #2219
• fixed firewall UI issue, all programs entries were missing *, prefix #2247
• fixed BlockPorts template with a missing *, prefix 4420ba4
• fixed issues with variosue electron apps #2217 #2235 #2201 #2166
  -- now the default behavioure is UseElectronWorkaround=n

Removed

• removed obsolete VPNTunnel template

 

Fixed! (on here) Thanks alot for this new build.

 

^^What she said

 

+1.

 

Same here.

 

I can confirm the fix as well. Thank you very much for this!

I can also confirm this new issue.

There is also an issue report on GitHub that David has already reacted to:
https://github.com/sandboxie-plus/Sandboxie/issues/2252

 

Labeled: ToDo ASAP.

 

FWIW ~ I'm not seeing SBIE2205 Service not implemented...issue.
v1.3.4 - Edge 105.0.1343.42 (Official build) (64-bit) - W10 Home 21H2 (19044.1826)

 

@bjm_ di you have PreferExternalManifest=y enabled? only then the issue manifests

 

No

 

Yeah, I found the switch after reading >
https://github.com/sandboxie-plus/Sandboxie/issues/583

 

The issue also seems to be triggered by the "Enable Microsoft Edge fix for Windows 11 KB5014019" template. If this is deactivated, the error messages no longer appear.

Here the following line seems to be the trigger: ExternalManifestHack=msedge.exe,y

 

I can reproduce the Edge issue with PreferExternalManifest=y

 

Edge - Set as default only when sbox'd ... feels new?

Edit: Set as default stopped with 105.0.1343.50

 

I, too, can confirm this new edge-issue although with a different error-number.


And after unticking "Enable Microsoft Edge fix for Windows 11 KB5014019'' in Options - global settings -compatability these error-messages will go away.

But now I get


as soon as I'm running a newly updated edge sandboxed. Again ticking the "Enable Microsoft Edge fix for Windows 11 KB5014019''-box will make the second (Profile-) error go away - but the initial "manifest - service not implemented"-error-messages will be back.

All this on Win10ProforWorkstations, latest 21H2, no Win11 here.

Oh, and I forgot to mention that I have no explicit entries about "ExternalManifest" whatsoever - neither in my Sandboxie.ini, nor in my Sandboxie-Plus.ini.

 

But you are saying that the Edge_Win11Fix is still required for edge to run properly?

 

It seems to be required to make those "manifest - service not implemented"-error-messages go away - but edge still won't run properly afterwards as that "fix" will trigger this new "profile-error" within edge as a result. In a manner of speaking I can choose between "Scylla and Charybdis" - well, it's not that bad of course, in particular since I don't use Edge on a regular basis anyway. Just a minor nuisance.

 

You are confused, it is the other way around. Without the "Edge_Win11Fix", the Manifest error messages disappear. In your previous post, you wrote it correctly.

I have never had the Profile error message, although I have always disabled the "Edge_Win11Fix" on Windows 10.

On my Windows 11 VM, the enabled "Edge_Win11Fix" now not only triggers the manifest error messages, but Edge also opens without GUI elements.

 

the issue wil be fixed in 1.3.5