Known Issues

FSLogix can be used in various solutions and environments. Through customer feedback, on-going support cases, or direct testing, there are issues that have been identified which may affect your environment(s). This article outlines these items as they're discovered. Some known issues have listed 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 dependant on other products or organizations.

New Teams for virtual desktops on Windows Server 2019

• Updated: February 13th, 2024
• Affected version(s): All versions
• State: In Progress

Users connecting to virtual desktops running on Windows Server 2019 are unable to launch or use new Teams. Reviewing the application event log will display 1 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

This issue is currently under investigation with high prioritization. Depending on the fix, this may come in the next feature release or as another hotfix.

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

• Updated: February 13th, 2024
• Affected version(s): 2210 hotfix 2 (2.9.8612.60056) and later
• State: In Progress

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

We plan to address this issue in a future release or may release an updated ADMX template out of band of our normal product release.

Unexpected VHD disk compaction results

• Updated: March 31, 2023
• Affected version(s): 2210 (2.9.8361.52326) and later
• State: In Progress

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

We plan to address this issue in a future release.

Microsoft Entra ID Authentication for applications

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

Users may 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 Entra join device state. We recommend virtual machines are Entra joined or Hybrid Entra joined for the best user experience.

Virtual machines, which are Entra joined or Hybrid Entra joined create the user's primary refresh token (PRT) at sign-in. Primary refresh token(s) 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

Determining your device status

Running the dsregcmd command provides an output that displays the state of the virtual machine in Microsoft Entra ID.

Tip

Run the dsregcmd /status command as a Domain User.

dsregcmd /status

^{Figure 1: Results of a virtual machine in the problem state}

The following articles are provided to help determine whether or not your virtual machines are configured to use primary refresh tokens as part of an Entra ID sign-in process.

• Entra ID Integration Methods
• Device identity and desktop virtualization
• Troubleshoot devices by using the dsregcmd command

Note

When using non-persistent VDI, you need to prevent users from adding work or school accounts. Use the below registry entry to prevent adding these virtual machines to your Entra ID directory. Failure to do so will result in your directory having lots of stale Hybrid Entra joined devices that were registered from your non-persistent VDI platform resulting in increased pressure on your tenant quota and risk of service interruption because of running out of tenant quota.

HKLM\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin: "BlockAADWorkplaceJoin"=dword:00000001

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 may 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 may 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.

Warning

Does not 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.