Known Issues

FSLogix can be used in various solutions and environments. Through customer feedback, ongoing support cases, or direct testing, there are identified issues which might affect your environments. This article outlines these items as they're discovered. Some known issues have workarounds, while others require a code change in the product.

Note

Not all known issues will be addressed through product changes as some cases are dependent on other products or organizations.

Devices that are only Entra joined will see an increase in Event Log errors (EventID 26)

• Updated: July 8, 2025
• Affected version(s): All versions
• State: In progress

FSLogix application rule sets rely on the ability to query a Domain Controller using LDAP. When a device is only Microsoft Entra joined (and not domain joined or Microsoft Entra hybrid joined), this check fails, resulting in two Event ID 26 errors. These errors are expected even when you've not implemented any rule sets; they can be safely ignored.

Log Name:      Microsoft-FSLogix-Apps/Operational
Source:        Microsoft-FSLogix-Apps
Date:          6/10/2025 10:37:03 PM
Event ID:      26
Task Category: None
Level:         Error
Keywords:
User:          SYSTEM
Computer:      WIN-HOSJ27GHJ33
Description:
Failed to get computer's group SIDs

Log Name:      Microsoft-FSLogix-Apps/Operational
Source:        Microsoft-FSLogix-Apps
Date:          6/10/2025 10:37:02 PM
Event ID:      26
Task Category: None
Level:         Error
Keywords:      
User:          SYSTEM
Computer:      WIN-HOSJ27GHJ33
Description:
Querying computer's fully qualified distinguished name failed. (Configuration information could not be read from the domain controller, either because the machine is unavailable, or access has been denied.)

Resolution

We plan to address this in a future release.

When signing into the same virtual machine between sessions, 'Resultant Set of Policy' (RSOP) or GPResult /R fails to find any data

• Updated: February 11, 2025
• Affected version(s): 2210 hotfix 4 (2.9.8884.27471) or later
• State: In progress

In 2210 hotfix 4, we reintroduced the asynchronous Group Policy processing feature. We've identified some cases when a user is signing into the same virtual machine between their sessions, the Resultant Set of Policy (RSOP) or Group Policy Results commands fail to find any data to determine the result of the policy processing. The user-based policies are still processed and applied, but aren't able to be rendered by these tools. However, signing into a different virtual machine between sessions will properly find the policy processing data.

Resolution

We plan to address this in a future release.

OneDrive is intermittently stuck at signing in on Windows Server 2019

• Updated: February 11, 2025
• Affected version(s): 2210 hotfix 4 (2.9.8884.27471) or later
• State: In progress

When signing into Windows Server 2019, the OneDrive sync client will intermittently get stuck at signing in and eventually will fail to complete the sign in process.

Resolution

We plan to address this in a future release.

ODFC settings applied to systems after ProfileLoad during sign in aren't applied to the user

• Updated: July 8, 2025
• Affected version(s): 25.02 (3.25.202.4223), 25.04 (3.25.401.15305)
• State: Fixed

In order to address issues affecting New Teams during sign out, ODFC settings were moved out of StartShell and EndShell. When using a third-party profile solution and the ODFC settings are applied as part of the sign in flow, the ODFC settings are read and applied prior to StartShell and won't be applied to the signed in user.

Resolution

Install the latest FSLogix version.

FSLogix containers don't detach and prevent users from signing into a new session

• Updated: April 8, 2025
• Affected version(s): 25.02 (3.25.202.4223)
• State: Fixed

Users were unable to sign into a new session because FSLogix containers didn't detach properly. Unhandled exceptions were causing a break in code flow that would normally continue and correctly detach a FSLogix container.

Resolution

Install the latest FSLogix version.

FSLogix Rules don't apply to users as expected

• Updated: April 8, 2025
• Affected version(s): 25.02 (3.25.202.4223)
• State: Fixed

Users weren't correctly assigned to rules resulting in rules not working as expected. Prior to 25.02, we saw issues with new Teams and ODFC where some settings aren't saved when the user signs out. New in 25.02 were changes to improve how these settings are captured prior to user sign out.

Resolution

Install the latest FSLogix version.

FRXShell rule fails clean up and prevents all user sign ins

• Updated: April 8, 2025
• Affected version(s): 25.02 (3.25.202.4223)
• State: Fixed

Under some situations, the FRXShell rule would apply to all users preventing sign in. Due to the FSLogix Rules do not apply to users as expected issue, we fail to assign the FRXShell rule. Without the assignment, our cleanup task wouldn't remove the rule and resulted in the FRXShell rule applying to all users.

Resolution

Install the latest FSLogix version.

After signing in, user receives an error message that the Recycle Bin is corrupted

• Updated: April 8, 2025
• Affected version(s): 25.02 (3.25.202.4223)
• State: Fixed

Users would intermittently receive a notification after signing in that the "Recycle Bin is corrupted". We discovered an issue where users were unable to access the Recycle Bin within their profile VHD.

Resolution

Install the latest FSLogix version.

Searchindexer.exe (frx_usermode_x64.dll) crashing in Windows Server 2016

• Updated: April 8, 2025
• Affected version(s): 25.02 (3.25.202.4223)
• State: Fixed

We identified an issue where we implement functionality for Windows Search and Outlook Cached Mode. An updated call to these components would cause the Searchindexer.exe to crash.

Resolution

Install the latest FSLogix version.

LocalCache and TempState folders aren't properly cleaned up during sign out

Note

Doesn't affect LocalCache for Microsoft Teams.

• Updated: February 11, 2025
• Affected version(s): 2210 hotfix 4 (2.9.8884.27471)
• State: Fixed

As stated in the FAQ, FSLogix deletes the contents of specific UWP folders inside the user's profile container. We discovered that the LocalCache and TempState folders aren't deleting and might have an adverse effect when roamed between virtual machines. Currently Microsoft Teams is affected by this issue due to roaming this data from the following packages:

• %LocalAppData%\Packages\Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy\TempState
• %LocalAppData%\Local\Packages\MicrosoftWindows.Client.CBS_cw5n1h2txyewy\TempState (Windows 11)
• %LocalAppData%\Local\Packages\Microsoft.Windows.Search_cw5n1h2txyewy\TempState (Windows 10)

Other applications or packages may also be affected and should be considered when troubleshooting issues.

Workaround

Create or update the redirections.xml to exclude the TempState folder.

<Exclude Copy="0">AppData\Local\Packages\**<insert-package-name-here>**\TempState</Exclude>

Resolution

Install the latest FSLogix version.

New Microsoft Teams for virtual desktops on Windows Server 2019

• Updated: May 14, 2024
• Affected version(s): 2210 hotfix 3 (2.9.8784.63912) and older
• State: Fixed

Users connecting to virtual desktops running on Windows Server 2019 are unable to launch or use new Microsoft Teams. Reviewing the application event log displays one or more errors.

1. Failure to instantiate storage folder C:\Users\%username%\AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache for package MSTeams_8wekyb3d8bbwe with Error Code: -2147024809

2. New Teams application crash:

   Faulting application name: ms-teams.exe, version: %msteams_version%, time stamp: 0x65719f33
   Faulting module name: ucrtbase.dll, version: %dll_version%, time stamp: 0x48ac8393
   Exception code: 0xc0000409
   Fault offset: 0x000000000006e77e
   Faulting process id: 0x1fc4
   Faulting application start time: 0x01da4d71abbfd06e
   Faulting application path: C:\Program Files\WindowsApps\MSTeams_%msteams_version%_x64__8wekyb3d8bbwe\ms-teams.exe
   Faulting module path: C:\Windows\System32\ucrtbase.dll
   Report Id: d0463b2e-8cc4-4bc6-96d9-f20c719fccd2
   Faulting package full name: MSTeams_%msteams_version%_x64__8wekyb3d8bbwe
   Faulting package-relative application ID: MSTeams
   

Resolution

Install the latest FSLogix version.

Enabled by default policies in the ADMX template can't be disabled using Group Policy

• Updated: February 11, 2025
• Affected version(s): 2210 hotfix 2 (2.9.8612.60056) through 2210 hotfix 4 (2.9.8884.27471)
• State: Fixed

FSLogix has several settings which are Enabled by default. When the ADMX templates were updated in the last feature release, a checkbox was removed from all of these settings to leverage the default Enabled and Disabled boolean from the policy. When Disabled is selected from the Group Policy template, the setting is removed instead of setting the registry value to 0 (Disabled).

List of impacted settings:

• Apps
  • RoamRecycleBin
  • VHDCompactDisk
• Profiles
  • CleanOutNotifications
  • InstallAppxPackages
  • IsDynamic
  • OutlookCachedMode
• ODFC
  • IncludeOfficeActivation
  • IncludeOneDrive
  • IncludeOutlook
  • IncludeOutlookPersonalization
  • IncludeSharepoint
  • IncludeSkype
  • IsDynamic
  • OutlookCachedMode

Workaround

Use a manual configuration option.

Resolution

Use the latest FSLogix ADMX / ADML files.

Unexpected VHD disk compaction results

• Updated: February 11, 2025
• Affected version(s): 2210 (2.9.8361.52326) through 2210 hotfix 4 (2.9.8884.27471)
• State: Fixed

Using ProfileType = 3 or VHDAccessMode = 1,2, or 3, differencing disks are used. This affects the VHD disk compaction process because the size of the differencing disk is used to evaluate the thresholds. Most often these differencing disks are small and never meet the thresholds.

Resolution

Install the latest FSLogix version.

Microsoft Entra ID Authentication for applications

• Updated: May 14, 2023
• Affected version(s): 2210 (2.9.8361.52326)
• State: Fixed

Users might be required to authenticate to their applications (for example, Microsoft 365 apps, Teams (work or school), OneDrive, etc.) at every sign-in. The repeated authentication prompts are due to the virtual machines Microsoft Entra join device state. We recommend virtual machines are Microsoft Entra joined or Hybrid Microsoft Entra joined for the best user experience.

Virtual machines, which are Microsoft Entra joined or Hybrid Microsoft Entra joined create the user's primary refresh token (PRT) at sign-in. Primary refresh tokens created at sign-in are used to authenticate to Microsoft Entra ID based applications. Standard Domain Joined (DJ) virtual machines don't create a PRT at sign-in, instead rely on the Microsoft Entra ID plugin.

Microsoft Entra ID broker directories and apps

Starting in FSLogix 2210 (2.9.8361.52326) and later versions, all content stored in following locations is no longer roamed as part of the user profile.

• %USERPROFILE%\AppData\Local\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy
• %USERPROFILE%\AppData\Local\Packages\Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy
• %USERPROFILE%\AppData\Local\Microsoft\TokenBroker

Resolution

Install the latest FSLogix version. Configure RoamIdentity by setting the registry value to 1 or enabling via Group Policy.

Black screen at sign-in or sihost.exe application hanging

• Updated: March 2, 2023
• Affected version(s): 2210 (2.9.8361.52326)
• State: Fixed

With the RoamRecycleBin setting enabled (enabled by default) and during the sign-in process, some users might experience a black screen instead of displaying the desktop. The black screen occurs when we configure the initial virtualization of the recycle bin. During the sign-in process, the recycle bin isn't empty on the virtual machine and our process attempts to empty it for all users.

Resolution

Install the latest FSLogix version.

Service Crash: User receives default or temporary profile (profile fails to load)

• Updated: March 2, 2023
• Affected version(s): 2210 (2.9.8361.52326)
• Status: Fixed

With the InstallAppxPackages setting enabled (enabled by default) and during the sign-in process, some users might receive a default or temporary profile as a result of the user's profile container failing to attach. The container failure occurs as a result of the frxsvc.exe crashing during sign-in.

Note

Doesn't cover all scenarios where a user's profile fails to load.

Resolution

Install the latest FSLogix version.

ODFC disk compaction fails with RoamSearch enabled

• Updated: March 2, 2023
• Affected version(s): 2210 (2.9.8361.52326)
• Status: Fixed

In some cases where RoamSearch and VHDCompactDisk¹ are enabled, disk compaction fails with the following error:

"[ERROR:00000000] Exception thrown during getSupportedSize, exception: D:\a\_work\1\s\packages\Microsoft.Windows.Wil.Internal.0.2.103\inc\wil\opensource\wil\result_macros.h(6159 )\frxsvc.exe!00007FF63B53EC53: (caller: 00007FF63B53FB0D) Exception(2) tid(39c) 800401F0 CoInitialize has not been called."

The result is the frxsvc.exe service crashes and the operation fails to succeed.

^{1 VHDCompactDisk is enabled by default.}

Resolution

Install the latest FSLogix version.