Below is a similar issue that we have seen regarding this issue. If you are using the same Application and Device Control policy try removing it to see if it helps.
Problem: The client uses a non-default Application and Device Control (ADC) policy which has enabled Sysplant.
In SEP 11 RU5, when sysfer.dll loads it tries to load with a base image of 0x10000000 which is different than previous builds of sysplant and sysfer.dll. When the RU5 sysfer.dll attempts to inject into an application that is also using a base image of 0x10000000, this causes a conflict and the application fails to load.
Workarounds:
1. Create a new Application and Device Control Policy without any rule changes and apply it to the affected group. Update the policy on the client and restart the affected computers. (Note: Withdrawing the ADC policy should also work.)
2. Roll the client back to 11.0.4202.75. (this is obviously a temperary fix)
Thanks,
Grant