WSA, Exploitshield, SBIE conflict

Testing the new ES 0.9.1 beta, came across this interesting conflict.
WSA and ES play nice as long as SBIE isn't thrown in the mix.
Using latest WSA, ES 0.9.1 beta, SBIE 3.76 opening firefox default sbie box shows nothing on monitor(i.e.does not render FF onto monitor), all sbie and FF processes are looking normal from process explorer(except ES.dll is blocked) , sbie window shows all processes normal except FF icon shows a folder icon instead, shut down protection WSA solves issue( tried disabling all shields one at a time, no luck), like wise with ES not installed everything is normal.

Just a heads up for anyone interested.
Edit: To add ,tested on W7pro x64

 

the latest Sbie v4 beta works bad with WSA's browser protection (in ID shield), it block much of WSA hooks , so you have to set the Browser on "Allowed" only and not "Protected"

 

Yes. Sandboxie functions in a way that blocks communication outside of the sandbox (which is the whole purpose of Sandboxie). Therefore the sandboxed browser must be "allowed" instead of "protected" in WSA.