Sandboxie plus 0.9.0

OK makes sense somehow. I have to experiment a bit more. So far it is a bit tricky to see, all set to WPF but for devices still have the allow, and block with WPF and internal dev block.
So say all is based on WPF, dev block is still active, but then what means block with WPF, why don't I block then in the IPs. The mix is a bit confusing, however it could also give more flexibility, however the more rules the more complex. Even the WPF dialog if you look at all is crazy, depending on the rules you want to set, so let's see. Not sure if I have a better GUI solution at the moment.
Thanks for the input. Tested the new version, all good so far.

 

@DavidXanatos Could you please check the source-code for more similar "blunder-instructions" like those having caused the "CET/Stack Protection"-problems on "11th-gen-Intel"-machines as with the latest build I will again get some of those same kind of "SBIE2101 Object name not found"-error-messages on various unrelated occasions again with Opera, although not lethal at this time. But still it would appear to me that similar causes like those which have triggered that major "11th-gen-flaw" might still be present in the code.

And most importantly those very error-messages did not occur while the "reg-hack" turning off "CET/Stack Protection" for Opera had been active.

 

@algol1 I'll take a look but i find it unlikely, could you lease test with re enabling the reg hack to be sure

 

I did - and to tell the truth results came down with a bit of ambiguity. So the jury is still out on a final decision.

Having that said the good news is - until now (keeping my fingers crossed) - those "SBIE2101"-errors so far never once have re-occurred WITH the "reg-hack" on and after updating to v0.9.3!