The FSLogix 2201 Public Preview is now available


FSLogix 2201 Public Preview Update 1 has been published to address the issue outlined below. Please read details here.


FSLogix 2201 is now available in Public Preview.  This public preview is not recommended for production workloads. Please leverage your standard Microsoft support channels to report issues with this public preview release.



We discovered an issue with the 2201 public preview that is impacting customers with session hosts configured to allow users to have more than one Windows session per user per host. In those situations, only that user's first session to a host will connect. Additional connections for that user to that host will fail to login.


Your environment is impacted by this bug if you have the "Restrict Remote Desktop Services users to a single Remote Desktop Services Session" group policy set to disabled or the HKLM:\Software\Policies\Microsoft\Windows NT\Terminal Services\fSingleSessionPerUser regkey value is set to 0.


We recommend impacted customers not install this public preview or revert back to the current generally available release. We are validating a fix for the issue and will publish an update to the public preview when it is available. Customers not impacted by this issue can continue validating this public preview release.


Preview Details

You can sign up here to participate in the Public Preview:


This release can be installed over all existing versions of FSLogix or you can perform a fresh install without a pre-existing FSLogix version.


Here's what's new in this release:

  • 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 now exclude it from FSLogix containers. Office files located outside this folder are not impacted by this update.
  • Windows Server 2019 version 1809, and newer versions of Windows Server, natively support per-user search indexes and we recommend you leverage 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]."
  • Resolved an issue where the DeleteLocalProfileWhenVHDShouldApply registry setting was sometimes ignored.
  • Fixed an issue where active user session settings where not retained if the FSLogix service was restarted. This was causing some logoffs to fail.
  • FSLogix will no longer attempt 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 blocksize was smaller than a cloud provider's. 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 blocksize size.
  • Fixed a Cloud Cache issue where a timed out read request (network outage, storage outage, etc.) was not 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 were not 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 did not apply if the Profile or ODFC container was not enabled for all users.
  • Resolved an issue where the Office container session configuration was not cleaned up if a profile fails to load.
  • Fixed an issue where HKCU App Masking rules leveraging wildcards would fail to apply.
  • Fixed an issue where FSLogix did not properly handle logoff 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 logoff related events will always occur if FSLogix loaded a container for the user.
  • Fixed an issue that caused some sessions configured with an ODFC container to fail to login.
  •  Resolved an issue where the rule editor would crash if there were no assignments configured.


81 Replies
I'm sorry I don't understand the machine specific bit. Surely that's the whole point. If I logon to a different multi-session machine from yesterday I am going to have to download my entire Office cache like my emails again!?
Thank you for making a fix for RefCount a year later.

Did you fix the problem with AppReadiness ?
Thanks for posting the Steve. Do you guys mean MultiSession around this statement?
"FSLogix search indexing is not available in Windows 10 or Windows 11.

I hope fix for RefCount work :) 

We revised that bullet to be more clear. This is related to a specific cache folder and you should not see an impact. That said, please test the public preview and let us know if you see any issues.
Let me know if you need clarification:
The OfficeFileCache folder located at %LOCALAPPDATA%\Microsoft\Office\16.0\OfficeFileCache is now machine specific and encrypted so we now exclude it from FSLogix containers. Office files located outside this folder are not impacted by this update.
Yes, sorry for the confusion. FSLogix Search is no longer available on Windows 10 or Windows 11 multi-session since those OSes have native support for per-user search and that's what should be used.
No problem Steve, Thank you for the clarification. Hope all is well sir.

Have you guys fixed the issue with logs redirection ?

We're not tracking an issue with log redirection. What are you seeing? Some customers have issues with log redirection because they apply the redirection via group policy or some other means that applies the redirection AFTER the FSLogix service starts. The reg key needs to be applied before the service starts. Also, you should consider using the FSLogix event logs instead of the log files.

That thread is long and loaded with incorrect info so I can't say what's been fixed. The thread starts with the suggestion that FSLogix is locking Credentials folders, but FSLogix only applies locks to the VHD/x containers. Something else is causing those locks. The thread also mentions the refCount issue, but that's incorrectly correlated with this issue. The refCount key value mentioned in that thread can be updated by MANY activities not related to FSLogix and FSLogix does not manipulate that value directly. The 2201 public preview implements a fix that cleans up the refCount value when it is left in an incorrect state. To be clear, FSLogix is not putting it in a bad state but that incorrect value is causing issues for FSLogix. For reference, that bad refCount value was also causing issues with non-FSLogix Windows profiles and we implemented the same fix in FSLogix.

The issue was happening when we were using the GPO setting indeed when the FSLogix service was restarted the logs were written properly. If I use the reg key via Group Policy Preference it works fine. If the GPO setting won't ever work, perhaps it should be removed from the ADMX template.

@Steve Downs So far so good, this version seems to be a huge stability improvement over the previous version running on Windows Server 2019.


I have found one issue so far.  For some reason, there are two app GUIDs associated with the installation of this version (I verified via registry too):


{06B996DB-0DF9-47C1-8149-8A506DC4D2DD} Microsoft FSLogix Apps
{C4A6234E-D6E3-45F8-B282-8B5C3DBBC289} Microsoft FSLogix Apps 
{5F779663-565D-4B04-A0B1-843BE78BDDFC} Microsoft FSLogix Apps RuleEditor



Thanks for reporting this, jshonk. That's expected behavior. One of those GUIDS maps to the FSLogix service and the other to our separate Cloud Cache service. That said, we opened a bug to rename the Cloud Cache entry.
Hello Steve,

Has the below FsLogix issue been resolved in this release?

If you read the above article, there has been an active and long engagement with the Microsoft Technical Support escalation team and FsLogix product group on the issue and there was no fix nor any ETA defined. Is this fixed in this release and if not, what is the ETA for resolution? This is affecting a huge amount of FsLogix/MS customers worldwide. It had been identified as bug by Microsoft Support Team and has not been fixed for over a year now.

Kindly waiting on your update,

@Steve Downs When the user logs off the server, we get the following error that the local profile cannot be deleted. I do not know why. :)



[11:08:32.034][tid:00000ac4.0000292c][ERROR:00000091] RemoveDirectory failure C:\Users\da (Das Verzeichnis ist nicht leer.)


[11:08:32.034][tid:00000ac4.0000292c][ERROR:00000091] RemoveDirectory failure C:\Users\da (Das Verzeichnis ist nicht leer.)







@MarcoSues Thanks for the answer. After restart the server fslogix works fine.


frx list-redirections output

No redirections are currently active.
Operation completed successfully!


Redirections.xml File in the config

<?xml version="1.0" encoding="UTF-8"?>
<FrxProfileFolderRedirection ExcludeCommonFolders="###VALUE###">

<Exclude Copy="0">Videos</Exclude>
<Exclude Copy="0">Saved Games</Exclude>
<Exclude Copy="0">Contacts</Exclude>
<Exclude Copy="0">Searches</Exclude>
<Exclude Copy="0">Citrix</Exclude>
<Exclude Copy="0">Tracing</Exclude>
<Exclude Copy="0">Music</Exclude>
<Exclude Copy="0">$Recycle.Bin</Exclude>
<Exclude Copy="0">AppData\LocalLow</Exclude>
<Exclude Copy="0">AppData\Local\Apps</Exclude>
<Exclude Copy="0">AppData\Local\Downloaded Installations</Exclude>
<Exclude Copy="0">AppData\Local\assembly</Exclude>
<Exclude Copy="0">AppData\Local\CEF</Exclude>
<Exclude Copy="0">AppData\Local\Comms</Exclude>
<Exclude Copy="0">AppData\Local\Deployment</Exclude>
<Exclude Copy="0">AppData\Local\FSLogix</Exclude>
<Exclude Copy="0">AppData\Local\GroupPolicy</Exclude>
<Exclude Copy="0">AppData\Local\Packages</Exclude>
<Exclude Copy="0">AppData\Local\Sun</Exclude>
<Exclude Copy="0">AppData\Local\VirtualStore</Exclude>
<Exclude Copy="0">AppData\Local\CrashDumps</Exclude>
<Exclude Copy="0">AppData\Local\Package Cache</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\TokenBroker\Cache</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Notifications</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Internet Explorer\DOMStore</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Internet Explorer\Recovery</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\MSOIdentityCRL\Tracing</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Messenger</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Terminal Server Client</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\UEV</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\Application Shortcuts</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\Mail</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\WebCache</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\WebCache.old</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\AppCache</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\Explorer</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\DNTException</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\IECompatCache</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\iecompatuaCache</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\Notifications</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\PRICache</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\PrivacIE</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\RoamingTiles</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\SchCache</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\Temporary Internet Files</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\0030</Exclude>
<Exclude Copy="0">AppData\Roaming\com.adobe.formscentral.FormsCentralForAcrobat</Exclude>
<Exclude Copy="0">AppData\Roaming\Adobe\Acrobat\DC</Exclude>
<Exclude Copy="0">AppData\Roaming\Adobe\SLData</Exclude>
<Exclude Copy="0">AppData\Roaming\Microsoft\Document Building Blocks</Exclude>
<Exclude Copy="0">AppData\Roaming\Microsoft\Windows\Network Shortcuts</Exclude>
<Exclude Copy="0">AppData\Roaming\Microsoft\Windows\Printer Shortcuts</Exclude>
<Exclude Copy="0">AppData\Roaming\Sun\Java\Deployment\cache</Exclude>
<Exclude Copy="0">AppData\Roaming\Sun\Java\Deployment\log</Exclude>
<Exclude Copy="0">AppData\Roaming\Sun\Java\Deployment\tmp</Exclude>
<Exclude Copy="0">AppData\Roaming\Sun\Java\Deployment\tmp</Exclude>
<Exclude Copy="0">AppData\Roaming\ICAClient\Cache</Exclude>
<Exclude Copy="0">AppData\Roaming\Macromedia\Flash Player\\support\flashplayer\sys\</Exclude>
<Exclude Copy="0">AppData\Roaming\Macromedia\Flash Player\\support\flashplayer\flashplayer\#SharedObjects\</Exclude>
<Exclude Copy="0">AppData\Local\SquirrelTemp</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Teams\Current\Locales</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Teams\Packages\SquirrelTemp</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Teams\current\resources\locales</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Teams\Current\Locales</Exclude>
<Exclude Copy="0">AppData\Roaming\Microsoft\Teams\Service Worker\CacheStorage</Exclude>
<Exclude Copy="0">AppData\Roaming\Microsoft\Teams\Application Cache</Exclude>
<Exclude Copy="0">AppData\Roaming\Microsoft\Teams\Cache</Exclude>
<Exclude Copy="0">AppData\Roaming\Microsoft Teams\Logs</Exclude>
<Exclude Copy="0">AppData\Roaming\Microsoft\Teams\media-stack</Exclude>

<Include Copy="3">AppData\LocalLow\Sun\Java\Deployment\security</Include>


@Steve Downs I think we found another issue with this release of FSLogix.  This particular issue is a QA environment that FSLogix was upgraded to the TP release.  It's a Windows 2012 R2 shared environment (also Citrix 1912 LTSR CU4).


In the FS Logix Event Logs we are now seeing Event ID 26:

Injection failed. [OUTLOOK.EXE] (Access is denied.)


Sessions are now locking up/freezing as a result when affected users are using Outlook.