Share via

FSLogix Release Notes

  • Article

FSLogix has moved away from a two (2) release structure and going forward will provide standard releases. These releases follow a pattern of internal testing (self-host), early access, and general availability (GA). Early access is available to any customer with an active non-disclosure agreement (NDA) with Microsoft. You can opt in by joining our 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.02 (3.25.202.4223)

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 has retired various features from the product and will no longer support 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 won't 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.

    Note

    This 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

File information

Download the following package and follow the installation instructions

FSLogix 2210 hotfix 4 (2.9.8884.27471)

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>\ will automatically get created when an ODFC container is created (new or reset container).
  • Teams data located in %LocalAppData%\Publishers\8wekyb3d8bbwe\TeamsSharedConfig will now 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 woudn'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

FSLogix 2210 hotfix 3 (2.9.8784.63912)

Summary

This is a hotfix release with limited support for various versions of Windows and was provided to unblock customers running the latest versions of Windows 11 with New Teams in virtual desktop environments. All customers are urged to replace any installations of this version with FSLogix 2210 hotfix 4, which provides a complete set of changes and updates for New Teams.

Important

Do not use this version, instead download and install 2210 hotfix 4 (2.9.8884.27471).

Changes

  • Update: When new Teams is detected, the AppX package is registered for the user during sign-in using the family name.
  • Update: During user sign-out, Teams user data/cache located in %LocalAppData%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache will be saved in the container.
  • Fix: Resolved an issue where a virtual machine would reboot unexpectedly as a result of bug check (various stop codes) when a user's redirects were removed before sign-out.

FSLogix 2210 hotfix 2 (2.9.8612.60056)

Summary

This is a hotfix release to address known issues and other identified bugs.

Changes

  • Fix: Resolved an issue where a virtual machine would reboot unexpectedly as a result of bug check (various stop codes).
  • Fix: Cloud Cache no longer creates a race condition when multiple threads try accessing the same tracking file.
  • Fix: Cloud Cache thread timing has been adjusted to ensure proper file handling and sanitization.
  • Fix: Cloud Cache now writes an event log message when a storage provider is offline when the user signs in.
  • Fix: Cloud Cache no longer causes a user session to hang while processing I/O.
  • Fix: Resolved an issue which failed to detach an ODFC container.
  • Update: Group Policy templates have been updated and re-organized. Read about the changes in the Group Policy how-to article.

File information

Download the following package and follow the installation instructions

FSLogix 2210 hotfix 1 (2.9.8440.42104)

Summary

This is a hotfix release to address known issues and other identified bugs.

Changes

  • Setting: Added new configuration setting (RoamIdentity). Allows legacy roaming for credentials and tokens created by the Web Account Manager (WAM) system.
  • Fix: Resolved an issue where frxsvc.exe would crash when processing AppXPackages.
  • Fix: Resolved issues in handling FileIds associated with OneDrive.
  • Fix: Resolved an issue with orphaned meta files on Cloud Cache SMB providers.
  • Fix: Resolved an issue where a pending rename operation would fail because the target filename was invalid.
  • Fix: Resolved an issue where user sessions were cleaned up before a proper sign out.
  • Fix: Resolved an issue where ODFC incorrectly handled multiple VHDLocations.
  • Fix: Resolved an issue in how settings are applied for ObjectSpecific configurations.
  • Fix: Resolved an issue where an ODFC container wouldn't correctly detach during sign out.
  • Fix: Resolved an issue where VHD Disk Compaction would fail to cancel correctly when using Cloud Cache.
  • Fix: Resolved an issue where ODFC VHD Disk Compaction would fail when RoamSearch was enabled.
  • Fix: Resolved an issue where users would be stuck at a black screen as a result of attempting to empty the Recycle Bin prior to roaming.
  • Update: Added policy for new RoamIdentity setting.

FSLogix 2210 (2.9.8361.52326)

Summary

This release is focused on three (3) core features, six (6) major bug fixes, and two (2) updates.

Changes

  • Feature: Added the ability to compact the user's container during the sign out phase. For more information, see VHD Disk Compaction.

  • Feature: Added a new process during the sign out phase, which creates an AppX package manifest for the user. This manifest is used at sign-in to re-register the AppX applications for an improved user experience. This work is on-going as AppX packages and applications continue to evolve. The focus for this work has been on the built-in Windows apps (inbox apps).

  • Feature: FSLogix now roams the users Recycle Bin within the user's container.

    Important

    All three (3) of our new features are enabled by default, but have the option to be disabled.

  • Fix: Added recursive checks as part of search clean-up activities.

  • Fix: Registers all provisioned packages when AppxManifest.xml doesn't exist.

  • Fix: When OneDrive data is stored outside the user's profile, FSLogix correctly impersonates OneDrive for setting permissions.

  • Fix: Resolved junction point compatibility issues with App-V.

  • Fix: RW differencing disks correctly handle disk expansion when SizeInMBs is increased from a smaller value.

  • Fix: Cloud Cache now properly honors lock retry count and intervals.

  • Update: Group Policy templates have new names that align with their registry settings. New help information indicates where in the registry Group Policy makes the change. Added version history for newly added settings.

  • Update: Ensure Azure Storage Account Blob container names correctly adhere to Azure naming requirements.

Next steps

Download and install FSLogix

Configuration examples

Configure profile containers