During periods of CPU spikes within user sessions, the environment experiences:

• Abrupt logoff behavior – sessions terminate unexpectedly without a graceful logoff

• Repeated session drops – sessions reconnect and drop repeatedly during recurring CPU spikes

• Improper session cleanup – user sessions do not terminate cleanly, which leads to residual processes and potential resource leaks

During normal user activity or application startup, temporary CPU spikes are expected and are considered normal. However, when WEM Basic Settings are enabled, WEM interprets these transient CPU spikes as policy violations. As a result, it aggressively restricts CPU core allocation to the affected session.

This intervention, although intended to protect overall system resources, destabilizes the user session and causes abrupt logoffs.

The specific WEM setting that triggers this behavior is enabled as part of earlier troubleshooting efforts to mitigate CPU spikes that previously cause sessions to terminate unexpectedly. Ironically, this same setting now introduces session instability because normal, short-lived CPU spikes are treated as critical violations.

Enable below WEM settings:

          "enableLimitCpuCoreUsage": true

          "cpuCoreLimitOfSpikeProtection": 2

These settings are often configured via group policy or directly in the WEM agent cache/configuration file (C:\Program Files (x86)\Citrix\Workspace Environment Management Agent\). 

Note: WEM actively monitors CPU usage and enforces a hard limit of 2 CPU cores on any process that it detects to be spiking. While this is intended to protect the system from sustained high CPU usage, this configuration misinterprets normal, short-lived CPU spikes (such as during application startup or normal user activity) as violations.

The Virtual Machines are not receiving the expected performance optimizations from Citrix WEM Basic Settings.

During periods of high CPU utilization within user sessions, the environment experiences the following impact:

• Abrupt logoff behavior

• Repeated session drops when CPU spikes reoccurred

• Improper session cleanup due to non-graceful session termination

https://docs.citrix.com/en-us/workspace-environment-management/2407/user-interface-description/system-optimization/cpu-management.html