Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
These releases follow a pattern of internal testing (self-host), early access, and general availability (GA). You can opt into early access by joining the Microsoft Management Customer Connection Program. When necessary, a critical update might be released quickly following a GA release.
Important
Customers are required to install and use the latest version. For more information, see FSLogix product support.
FSLogix 25.06
- Version: 3.25.626.21064
- Date published: July 8, 2025
Summary
This release provides compatibility and support for Microsoft Outlook for Windows (MSIX version).
What's new
- Support, data roaming, and application registration for Microsoft Outlook for Windows (MSIX version).
- Enabled special handling for the registration of the MSIX package family in both Profiles and ODFC.
- Supports redirections of the application data for ODFC containers.
- Allows coexistence between classic and Outlook for Windows under a single configuration setting.
Fixed issues
- Fixed an issue where FSLogix attempted to look up a user token before it was initialized during profile load.
File information
Download the following package and follow the installation instructions
FSLogix 25.04
- Version: 3.25.401.15305
- Date published: April 8, 2025
Summary
This release provides updates to address five known issues introduced in 25.02.
Fixed issues
- FSLogix containers don't detach and prevent users from signing into a new session.
- FSLogix Rules don't apply to users as expected.
- FRXShell rule fails clean-up and prevents all user sign ins.
- After signing in, user receives an error message that the Recycle Bin is corrupted.
- Searchindexer.exe (frx_usermode_x64.dll) crashing in Windows Server 2016.
File information
Download the following package and follow the installation instructions
FSLogix 25.02
- Version: 3.25.202.4223
- Date published: February 11, 2025
Summary
This release is a change in versioning and release structure. This update to v3 introduces a versioning that is date / time formatted and based on when the product was created. While not feature packed, we made significant updates and improvements to enhance overall stability. Additionally, this release retired various features from the product and no longer supports 32-bit operating systems.
What's new
- Major version change (2 → 3) and updated how FSLogix release names and build versions are defined. In future releases, major releases will increment the major version from 3 to 4 to 5, etc.
- Example:
- Release name: 25.02
- Build version: 3.25.202.4223 (3.YY.MMDD.HHMMS, Single digit months don't have a leading 0)
- Example:
- Cloud Cache no longer assumes some failure states are a bad configuration and now allows customers to test and validate their configurations for redundancy through any method they choose.
- Microsoft.FSLogix PowerShell module used for Cloud Cache investigation and troubleshooting.
- When
RedirXMLSourceFolder
is removed or 'not configured' in Group Policy, the redirections.xml file is now removed from within the user's profile container at the next sign-in.
Fixed issues
LocalCache and TempState folders for MSIX packages are now properly cleaned up during sign out.
Fixed an issue related to symlink reparse points affecting App-V and other components that have similar calls.
VHD disk compaction for differencing disks now works the same as disks without a differencing disk.
Note
Compaction results are based on each disk and what space is able to be reclaimed during the optimization.
ADMX templates were updated to allow settings that are enabled by default to be disabled.
Sign-in and sign out optimizations to ensure MSIX settings are properly handled before and after the Windows shell events.
Note
This optimization is most notable when reviewing text logs.
===== Begin Session: Post Profiles Logon ===== End Session: Post Profiles Logon ===== Begin Session: Pre Profiles Logoff ===== End Session: Pre Profiles Logoff
Feature retirement
- Support for Windows Server 2012 R2
- Support for 32-bit operating systems
- Cloud Cache CcdMaxCacheSizeInMBs (limited cache)
- Profiles Configuration Tool
- App Container Rules
- Internet Explorer browser plug-in
- Application Rule Set license reporting
- Java Rule Editor and Java Rules
- FRXTray utility
File information
Download the following package and follow the installation instructions
FSLogix 2210 hotfix 4
- Version: 2.9.8884.27471
- Date published: May 14, 2024
Summary
This is a hotfix release to address known issues and other identified bugs. In addition, this release brings back the capability to roam a user's Group Policy state which provides asynchronous policy processing.
Important
This version provides a comprehensive set of changes to support new Microsoft Teams in virtual desktop environments.
What's new
2210 hotfix 4 includes the following updates:
- Group Policy processing can now occur asynchronously for users during sign-in.
- MSIX folders under
%LocalAppData%\Packages\<package-name>\
are automatically created when an ODFC container is created (new or reset container). - Teams data located in
%LocalAppData%\Publishers\8wekyb3d8bbwe\TeamsSharedConfig
will roam with the ODFC container.
Fixed issues
2210 hotfix 4 includes the following fixed issues:
- Windows Server 2019 would sometimes fail to query the provisioned AppX applications for the user during sign out.
- MSIX folders that shouldn't be backed up would be removed during sign out instead of only removing the contents of those folders.
- New Microsoft Teams crashes or fails to start in Windows Server 2019.
- New Microsoft Teams would display an error during launch with
The parameter is incorrect
. - New Microsoft Teams would display an error during launch with
Invalid function
. - New Microsoft Teams wouldn't on-demand register during sign-in when using the ODFC container.
- New Microsoft Teams wouldn't on-demand register during profile creation and wouldn't register during future sign-ins, despite being installed.
- User-based Group Policy settings would persist in the user's profile after the policy setting was removed or set to disabled.
File information
Download the following package and follow the installation instructions