This message was deleted.

It's really around when the Citrix API hooks latch to the exe and the process floors the CPU and the application doesn't work. By added the disable part it does hook into the app, there for allow it to work as it would in a non Citrix setup for example.

troubleshooting that leads to this usually is, "App or App behavior works when I RDP but can't launch from Citrix" or "App looks funny/cant be resized/only gives a black screen in specific windows in Citrix"

^--- this is a great description.

oh

Yea Jon is spot on. I was trying to explain this. But found the link where @James Kindon explained a scenario. If you do this, Don't do it via GPO. I learned the hard way many years ago. https://support.citrix.com/article/CTX321177/grey-screen-issue-after-changes-were-made-under-ctxuvi-and-ctxhook https://jkindon.com/deploying-brave-and-microsoft-edge-dev-browsers-in-citrix-cvad-environments/