Ok, my "all clear"-statement has been short-lived. From out of nowhere both latest browsers (Chrome v.95 and Opera-Developer v.82) have stopped launching again after they WERE launching temporarily after latest Sandboxie-update to v0.8.9c. In between there has been neither another Sandboxie-update nor any update of those browsers affected nor one of display-drivers for Intel-Iris-Xe - as there is no newer graphics-driver, the very latest version is already installed. Of course I could wait now for the next graphics-driver release or blame the issue on those latest browser-upgrades which have introduced the issue. But there is also the fact that the problem only exists within Sandboxie while un-sandboxed both browsers will operate successfully. It could also be possible that this is another 11th-gen-Intel-machine problem - but the fact remains that there exists a Sandboxie-side of the problem, too, as without Sandboxie everything works fine still. I also have checked if the Sandboxie-ini-file might perhaps have changed in-between from right after the installation of Sbie v0.8.9c (when those browsers initially DID work) to the current state when they don't any longer. This is not the case. Sandboxie.ini has not changed for quite some time now. Also another over-the-top- installation of Sbie v0.8.9c didn't help to re-enable those browsers again as it initially has successfully done. From a layman's perspective this looks pretty much like an electric loose-contact-situation where some device would stop working simply at random. Strange - but this still is the current state of the play and I'm afraid - since Chrome-browser itself is affected - this cannot be ignored in the long run. Perhaps @DavidXanatos might want to check latest Chrome on his new Ryzen-machine although I have no idea which graphics-engine is active in there.