A community member aimed to monitor FSLogix profile compression activity on shared desktops by creating a custom event log rule in ControlUp, cloned from an existing rule. Despite confirming the session hosts had relevant event log entries locally and that the ControlUp agent on those machines was active and sending other data, the new rule failed to pull in the FSLogix compression events.
Initial troubleshooting confirmed that all relevant ControlUp monitors and agents were updated to version 9.2.5.686. Since the setup appeared correct, the next step suggested was to open a support ticket for deeper investigation. However, another community member pointed out a similar known issue documented in a prior Slack thread, referencing an upcoming ControlUp software version (9.2.5.776) release scheduled for September 10, 2026, that reportedly addressed such event log collection problems.
Further clarification noted that while version 9.2.5.776 was available, the specific fix for this FSLogix event collection issue might not have been included in that release yet but expected in the next version update. To verify functionality, one member created a nearly identical event log collection rule targeting informational events with ID 57 (typical of FSLogix profile compression logs), derived from ControlUp’s built-in FSLogix rules. This rule successfully captured multiple events from the VDI event logs, indicating the method itself was functional and suggesting that upgrading to version 9.2.5.776 might resolve the issue.
The consensus recommendation was to attempt the upgrade to version 9.2.5.776 first, as this could potentially fix the event log collection problem. Users encountering similar difficulties with FSLogix event gathering should ensure their ControlUp agents and monitors are updated to this or a later version and may benefit from revisiting built-in FSLogix templates for rule creation. For unresolved cases, opening a support ticket with ControlUp is advised to facilitate a resolution.
For further reference on creating and managing event log rules, see the ControlUp documentation at https://docs.controlup.com or ControlUp Academy at https://cuacademy.controlup.com.
Read the entire ‘Troubleshooting FSLogix Profile Compression Event Log Collection in ControlUp Agents’ thread below:
Good evening,
I am working to create some event logs to see how often FSLogix profile compression runs on my shared desktops. Created this rule by cloning an ControlUp rule, but I’m not seeing anything pull in despite session hosts having the log in their local event viewer. Confirmed the machine’s agent is active and uploading other data. Did I do something wrong?
Your config seems good. Are all monitors and the related agents updated to a 9.2.5 build?
Yes – everything appears to be 9.2.5.686
Then I would create a support ticket to get this investigated
I think this looks similar to the problem had (). There is a new version available for download that should fix the issue (v9.2.5.776 – 10 September 2026).
It could be the same root cause as what you found. As far as I know that hasn’t been integrated in version.776 though. That should be made available in the next version we release.
As a test, I’ve created the same event log collection rule as, capturing informational events with ID 57 (I took a copy from the other builtin FSLogix rule and edited it). I can see multiple events 57 in the VDI event logs now. So not sure if it was included in version.776 or if it it something else, but it seems to work.
In that case I would indeed upgrade to.776 first.
Ok I will give that shot – thanks!
Continue reading and comment on the thread ‘Troubleshooting FSLogix Profile Compression Event Log Collection in ControlUp Agents’. Not a member? Join Here!
Categories: All Archives