Blog Post

FSLogix Blog
2 MIN READ

Announcing FSLogix 2210 hotfix 3 Preview (2.9.8716.30241)

Jason_Parker's avatar
Jason_Parker
Icon for Microsoft rankMicrosoft
Dec 05, 2023

Hello FSLogix nation!

 

Microsoft is pleased to announce the availability of FSLogix 2210 hotfix 3 Preview (2.9.8716.30241).

 

This is a PREVIEW version, and we recommend first running in your non-production environments to fully test and understand the new updates and fix.

 

We've updated several new articles in our documentation and updated the release notes page.

 

Release Notes:

  • Update: When new Teams is detected, the AppX package is registered for the user during sign-in.
  • 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

[UPDATE] January 9th, 2024:

 

First of all, I want to say "THANK YOU" to all of those who've been testing and validating this hotfix preview release. Based on the testing and feedback I'd like to report on the current status:

 

All:

  • Potential anti-virus conflicts. Teams 2.1 paths have changed, and some anti-virus products have prevented the Teams executables from launching correctly.  Confirm with your vendor if any changes are needed to be compatible with Teams 2.1.

Windows 10 and 11 (Enterprise and Multi-session):

  • Operating systems have the correct API(s) for proper discovery and registration for UWP / AppX packages.
  • Profile only, Profile and ODFC, and ODFC only configurations working as intended.
  • Preservation of Teams user data in %LocalAppData%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache working as intended.

Windows Server 2022:

  • [Unable to reproduce] Teams 2.1 fails to launch / start with a message, "msteams_autostarter.exe 'The parameter is incorrect'" (Looking for customers to help investigate and reproduce).

Windows Server 2019:

  • [Confirmed] Missing API for UWP / AppX packages preventing discovery and registration (under investigation).
  • [Unable to reproduce] Failure to instantiate storage folder C:\Users\%username%\AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache for package MSTeams_8wekyb3d8bbwe with Error Code: -2147024809 (Looking for customers to help investigate and reproduce).

Once we can confirm we've addressed the issue above, we will plan for an updated release for hotfix 3 (updated version).

 

 

 

Cheers,

Jason Parker, Sr. Program Manager for FSLogix

Windows Cloud Experiences at Microsoft

Updated Jan 09, 2024
Version 3.0

66 Comments

  • Mark_Blackwood's avatar
    Mark_Blackwood
    Copper Contributor
    Feb 12, 2024

    I just saw this link today for those who have access to view it. (If not Screenshot below)

    Trying to work out how the NEW Teams can be pushing on to us when FSLogix is still in "Preview" and clearly with issues still. We are install having intermittent issues with it in our environment.
    https://admin.microsoft.com/AdminPortal/home?#/MessageCenter/:/messages/MC713033


     

  • martinss's avatar
    martinss
    Copper Contributor
    Feb 12, 2024

    We're running Windows 11 23h2 multi-session (AVD) with FSLogix hotfix 3 (2.9.8716.30241), new Teams, auto update disabled, and test group of users all with a new profile (using new path) from start (so no classic Teams). We've seen a lot of error 26 (Failed to acquired logoff lock for user & Failed to acquired check session lock for user & Error exporting profile registry information) and error 53 (Failed to acquire mutex for user).

     

    Once we get the users logged in, they do work fine and new Teams seems to work as expected.

     

    In hotfix 2, we previously had similar issues, and setting 'InstallAppxPackages' to 0 (disabled) seemed to resolve it. However, with new Teams being an Appx package, I'm not sure how this works in coordination with new Teams? We've got 'InstallAppxPackages' set to 1 (enabled) on the test deployment running hotfix 3. If it is possible we can safely disable it again, I'm happy to give that some testing?

  • jasveith's avatar
    jasveith
    Copper Contributor
    Feb 09, 2024

    pichpich - We haven't see a blackscreen for that long, be we are currently suffering from a 45-75 second backscreen.  It doesn't happen every time.  We've narrowed it down to svchost.exe (AppXSvc) using up a LARGE amount of memory doing something.  We've seen this process chew up 6GB before it finally finishes what ever it is doing, and then releases all that memory.

     

    We have a current case open with MS to figure out why this is happening.

    Stats:

    Win11 22H2  Multi-session AVD