Announcing general availability of FSLogix 2210 hotfix 3!

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

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?

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

Has anyone faced 9 minutes blackscreen after this Fslogix hotfix 3 upgrade? We are on Citrix Virtual Desktop with non-persistant machines. Also it get stuck on logging off we we logout, we must force the VM to restart.

Thank you

rjj85 according to official documentation you shouldnt have to use the Include switches.  The latest FSL preview specifically accounts for the LocalCache folder (usually this folder gets wiped out for MSIX/AppX packages) but for the new Teams they make a specific exception.

Also the second folder you specifically Include should be included by default as it isnt a folder that gets wiped out.  I guess I am saying you just might be making more work for yourself and complicating things LOL.

In my environment we have it working using just the exclusions you already have.

Karsten_Rechnagel Sounds like same behavior as myself and jasveith . I can confirm the customizations are saved in the app_settings.json file under AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams folder by examining the VHD after log off.

The only way can get Teams to not overwrite settings on next logon is by force closing Teams prior to log off.

1) Make changes in Teams
2) Right click on icon in systray and choose "quit"

On Server 2019 ( 1809 (OS Build 17763.5329) with FSLogix 2210 hotfix 3 Preview (2.9.8716.30241) installed, and Cirtix VDA 2311, the new Teams doesn't launch at all  for the users, on the Application Event logs, I get:

Failure to instantiate storage folder C:\Users\<user>\AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache for package MSTeams_8wekyb3d8bbwe with Error Code: -2147024809

Looking at the user's C:\Users\<user>\AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache folder, whilst the user is logged on, I can see that the folder is empty.

If I stop the FSLogix services, Teams works fine.

I have added the Registry entry:

Location: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Teams
Name: disableAutoUpdate
Type: DWORD
Value: 1

And I have tested removing the configuration for the redirections.xml to confirm that exclusions are not causing the issue.

The same setup works fine for classic Teams. Like many here, I'm concerned about the cut off date for classic Teams, when we don't have a stable version of FSLogix that will work with the new Teams.

For info, our anti-virus is Microsoft Defender.

Jason_Parker I'm happy to run tests if that helps.

I can confirm that even with FSLogix 2210 hotfix 3 Preview (2.9.8716.30241) installed, nothing is retained in the MSTeams_8wekyb3d8bbwe\LocalCache folder on a Windows Server 2022 using profile container. All the files are simply gone after a relog. The files are then recreated when starting Teams, and you get the new user experience each time Teams is started. If I make any changes, like changing the theme to dark mode, I can see this reflected in the app_settings.json file immediately, so the settings are saved just fine.

Just to be sure, I tried using <Include>AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache</Include> and set the IncludeTeams setting in GPO, even though it is an ODFC setting, but no luck.

rjj85  - A few things we discovered along the way

1) FSLogix 2210 hotfix 3 Preview (2.9.8716.30241) is a MUST.  We couldn't get any of our savings to save to the FSlogix profile without it.

2) The "New" Teams seems to need something to trigger it before it will write its settings to disk. Some things we found were:

     a: Quit Teams by right-clicking on the icon in the systray
     b:  Wait some length of time after making the settings.  I tested at 5 minutes and that seemed to work fine.
     c:  Sending a message to another user.  This didn't seem to work every time for everyone, but worked enough to think that it caused                    Teams to save out its settings

3) We also added to the redirections.xml file:

<Exclude Copy="0">AppData\Local\Publishers\8wekyb3d8bbwe\TeamsSharedConfig\meeting-addin</Exclude>
<Exclude Copy="0">AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\Logs</Exclude>
<Exclude Copy="0">AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\PerfLogs</Exclude>
<Exclude Copy="0">AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile_tfw\WebStorage</Exclude>

<Include>AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache</Include>
<Include>AppData\Local\Publishers\8wekyb3d8bbwe\TeamsSharedConfig</Include>    

Hope that helps!

We have the same issue as jasveith on Windows 10 and Server 2019, think its a Team issue specifically.

The only way we get Teams to save settings, and be stored in the FSLogix profile is to:
1) Make changes in Teams
2) Right click on icon in systray and choose "quit"
3) Logout so settings get saves to profile in FSLogix.