Discover the known issues in our latest FSLogix 25.02 release and the steps we're taking to address them
Our primary goal with any release is to ensure quality and reliability. This is a key focus area of our early access program, which is part of the Microsoft Management Customer Connection Program (MM CCP). We have been closely monitoring social media posts, customer-submitted cases, and our telemetry data to identify five known issues in the latest release.
We have updates in the pipeline to address these issues. Internal testing has already begun, and we plan to release an updated version to early access by the end of this week (March 21, 2025).
FSLogix containers do not detach and prevent users from signing into a new session
Description: Users were unable to sign into a new session because FSLogix containers did not detach properly.
Cause: Unhandled exceptions were causing a break in code flow that would normally continue and correctly detach an FSLogix container.
FSLogix Rules do not apply to users as expected
Description: Users were not correctly assigned to rules resulting in rules not working as expected.
Cause: Prior to 25.02, we saw issues with new Teams and ODFC where some settings are not saved when the user signs out. New in 25.02 were changes to improve how these settings are captured prior to user sign out.
FRXShell rule fails clean up and prevents all user sign ins
Description: Under some situations, the FRXShell rule would apply to all users preventing sign in.
Cause: Due to the issue, "FSLogix Rules do not apply to users as expected", we fail to assign the FRXShell rule. Without the assignment, our cleanup task would not remove the rule and resulted in the FRXShell rule applying to all users.
After signing in, user receives an error message that the Recycle Bin is corrupted
Description: Users would intermittently receive a notification after signing in that the "Recycle Bin is corrupted".
Cause: We discovered an issue where users were unable to access the Recycle Bin within their profile VHD.
Searchindexer.exe (frx_usermode_x64.dll) crashing in Windows Server 2016
Description: Searchindexer.exe would crash on systems running Windows Server 2016.
Cause: We identified an issue where we implement functionality for Windows Search and Outlook Cached Mode. An updated call to these components would cause the Searchindexer.exe to crash.
Microsoft
