Error removing Rule at logoff

Yes, this is a known behavior in FSLogix around that version. The error occurs because the exclusion rule points to a folder that doesn’t exist at logoff, so FSLogix logs it as an error even though the profile cleanup proceeds fine. It’s harmless but can clutter logs.

A few ways to handle it:

1. Suppress logging for missing exclusions: Check if your FSLogix version supports LogMissingExclusions=false in frx.ini.
2. Verify exclusions: Make sure the folder paths in Redirections.xml exist or adjust them if they might not be present for all users.
3. Update FSLogix: Later builds have improved logging behavior for missing folders. If feasible, upgrading can reduce spam in logs.

Basically, it’s more of a cosmetic log issue than a functional problem.