I'm using this on a work computer so I'm not able to create a new local user for the cleanboot test
If memory serves, this is also common to the reports - being in a corp environment.
Are either of you using 'Websense' in your environment - if so, you should have a service running for it. If you are not admins, please ask your IT people. They wont let you shut that off but it will go a long way to confirming it as a culprit (just does not like how Fences runs in the WinExplorer process).
perhaps chamelespoon might be able to help with this part of the troubleshooting?
We are not convinced it is Fences itself but an interaction with an app, setting, policy, etc. That is why a clean boot is so important for us to help diagnose the issue. With near certainty, under a clean boot, Feces would likely work for each of you. Then would be the personal process of the process of elimination to figure out what app, setting, etc - when re-enabled - is causing the conflict.