Blog Post

FSLogix Blog
2 MIN READ

FSLogix v3 Release 25.02 is now generally available!

Jason_Parker's avatar
Jason_Parker
Icon for Microsoft rankMicrosoft
Feb 12, 2025

Another long journey getting version 3 out to the public. We've been testing this version in our Early Access program since November 2024. Huge thank you to all the contributors for their feedback and validation.

FSLogix Release Notes - FSLogix | Microsoft Learn

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 will not have a leading 0)
  • Cloud Cache no longer assumes some failure states are a bad configuration and will now allow 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 will still be based on each disk and what space is able to be reclaimed during the optimization.
  • ADMX templates have been 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.

Feature retirement

Updated Feb 12, 2025
Version 2.0

32 Comments

Show More
  • Quentin Gerlach's avatar
    Quentin Gerlach
    MCT
    Feb 12, 2025

    The removal of the FRXTray tool seems counterintuitive — that tool was extremely helpful at times troubleshooting profile issues.  What’s the replacement for it?

    • Jason_Parker's avatar
      Jason_Parker
      Icon for Microsoft rankMicrosoft
      Feb 12, 2025

      The FRXTray tool had a number of issues (accessibility, inaccurate disk space reporting, resource utilization, etc). We chose to remove this tool as there are a number of other ways to get the same information. For example:

      • frx.exe list-redirects
        • This will show any active redirects and validate the users VHD is connected and redirected via FSLogix.
      • Event Viewer
        • Event ID 25 (Profile load: Status: 100  Reason: 0  Error: 0  Username: %username%  SID: S-1-5-21-0000000000-0000000000-0000000000-1110
      • Profile logs (%ProgramData%\FSLogix\Logs\Profile)
        • [15:14:14.517][tid:00000238.00001598][INFO]             LoadProfile successful. Version: 3.25.202.4223 User: %username%. SID: S-1-5-21-0000000000-0000000000-0000000000-1110. SessionId: 3
      • Powershell
        • Get-Disk | Where-Object {$_.Location -match '<file-server-name>'} | Select-Object Number,HealthStatus, Location
        • Get-Volume -FriendlyName Profile*

       

      All of these methods do not require administrator rights. We had hoped to integrate an alternative, but it didn't make the prioritization though we may consider it in the future.  Customer feedback is always the best indicator of what should be prioritized in the future.

      • iclay7's avatar
        iclay7
        Copper Contributor
        Mar 12, 2025

        I would agree with Quentin. Having to look in multiple places instead of the centralized tool is very counter-intuitive. We had a major issue when rolling out the new version recently via Intune. It took me forever to find the information about why user profiles were not being loaded, whereas with frxtray, I could've had those answers in just a few minutes. In the end, we had to manually uninstall and reinstall the new version to get it working.