FSLogix Release Notes
FSLogix has two (2) types of releases, feature and hotfix. A feature release has new or changing functionality to the product, whereas a hotfix release is focused on specific issues. Depending on the type of issue, we may have multiple hotfixes before a feature release. Regardless of the of release type, customers are required to install and use the latest version. For more information, see FSLogix product support.
- How to: Download and install FSLogix
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\TeamsSharedConfigwill 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 should not 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 would not on-demand register during sign-in when using the ODFC container.
- New Microsoft Teams would not on-demand register during profile creation and would not 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\LocalCachewill 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.
FSLogix 2201 hotfix 2 (2.9.8228.50276)
Summary
This update for FSLogix 2201 includes fixes to multi-session VHD mounting, Cloud Cache meta tracking files, and registry cleanup operations.
Changes
- Resolved an issue that would cause a system crash while reading from meta tracking files in a Cloud Cache configuration.
- Resolved an issue where a sign in would succeed even if when the disk failed to attach. Most commonly occurs in multi-session environments.
- Resolved an issue during profile cleanup where user registry hives would be removed regardless of the FSLogix local group exclusions.
FSLogix 2201 hotfix 1 (2.9.8171.14983)
Summary
This update for FSLogix 2201 includes fixes to Cloud Cache and container redirection processes. No new features are included with this update.
Changes
- Resolved an issue with Cloud Cache where disk read / write blocking could potentially create a deadlock to the disk and cause the Virtual Machine to become unresponsive.
- Resolved an issue that would cause a Virtual Machine to crash while removing profile redirections during the sign out process.
FSLogix 2201 (2.9.8111.53415)
Summary
This update for FSLogix is the latest full featured release. In this version there are, over 30 accessibility related updates, new support for Windows Search in specific versions of Windows, better handling and tracking of locked VHD(x) containers, and resolved various issues.
Changes
- Fixed issue where the FSLogix Profile Service would crash if it was unable to communicate with the FSLogix Cloud Cache Service.
- The OfficeFileCache folder located at %LOCALAPPDATA%\Microsoft\Office\16.0\OfficeFileCache is now machine specific and encrypted so we exclude it from FSLogix containers. Office files located outside this folder aren't impacted in this update.
- Windows Server 2019 version 1809, and newer versions of Windows Server, natively support per-user search indexes and we recommend you use that native search index capability. FSLogix Search Indexing is no longer available on those versions of Windows Server.
- Windows 10 Enterprise Multi-session and Windows 11 Enterprise Multi-session natively support per-user search indexes and FSLogix Search Indexing is no longer available on those operating systems.
- FSLogix now correctly handles cases where the Windows Profile Service refCount registry value is set to an unexpected value.
- Over 30 accessibility related updates have been made to the FSLogix installer and App Rules Editor.
- A Windows event now records when a machine locks a container disk with a message that looks like "This machine '[HOSTNAME]' is using [USERNAME]'s (SID=[USER SID]) profile disk. VHD(x): [FILENAME]. This event is generated from the METADATA file created in the user's profile directory. This file can be ignored, but not deleted."
- Resolved an issue where the DeleteLocalProfileWhenVHDShouldApply registry setting was ignored in some cases.
- Fixed an issue where active user session settings weren't retained if the FSLogix service was restarted. This was causing some logoffs to fail.
- Fixed an issue where FSLogix didn't properly handle sign out events if Profile or ODFC containers were disabled during the session or per-user/per-group filters were applied mid-session that excluded the user from the feature. Now FSLogix sign out related events always occurs based off the FSLogix settings applied at sign in.
- FSLogix no longer attempts to reattach a container disk when the user session is locked.
- Fixed an issue that caused the FSLogix service to crash when reattaching container disks.
- Fixed a Cloud Cache issue that caused IO failures if the session host's storage block size was smaller than a cloud provider's block size. For optimal performance, we recommend the session host disk hosting the CCD proxy directory has a physical block size greater than or equal to the CCD storage provider with the largest block size.
- Fixed a Cloud Cache issue where a timed out read request (network outage, storage outage, etc.) wasn't handled properly and would eventually fail.
- Reduced the chance for a Cloud Cache container disk corruption if a provider is experiencing connection issues.
- Resolved an issue where temporary rule files weren't deleted if rule compilation failed.
- Previously, the Application masking folder was only created for the user who ran the installer. With this update, the rules folder is created when the Rules editor is launched.
- Resolved an interoperability issue with large OneDrive file downloads that was causing some operations to fail.
- Fixed an issue where per-user and per-group settings didn't apply if the Profile or ODFC container wasn't enabled for all users.
- Resolved an issue where the Office container session configuration wasn't cleaned up if a profile fails to load.
- Fixed an issue where HKCU App Masking rules using wildcards would fail to apply.
- Fixed an issue that caused some sessions configured with an ODFC container to fail to sign in.
- Resolved an issue where the App Rules editor would crash if no assignments were configured.