Blog Post

FSLogix Blog
2 MIN READ

Announcing general availability for FSLogix 2210 hotfix 4!

Jason_Parker's avatar
Jason_Parker
Icon for Microsoft rankMicrosoft
May 14, 2024

FSLogix 2210 hotfix 4

This hotfix, along with the updates from hotfix 3, address a wide range of issues associated with the new Microsoft Teams. We wish to express our gratitude to the 30+ customers and partners whose crucial involvement in our validation process has been essential for the discoveries and solutions provided in this release. Additionally, we are reintroducing a previously released and highly requested feature: Asynchronous Group Policy processing!

 

What's new

  • Group Policy processing can now occur asynchronously for users during sign-in.
  • MSIX folders under %LocalAppData%\Packages\<package-name>\ will automatically get created when an ODFC container is created (new or reset container).
  • New Microsoft Teams data located in %LocalAppData%\Publishers\8wekyb3d8bbwe\TeamsSharedConfig will now roam with the ODFC container.

Fixed issues

  • Windows Server 2019 would sometimes fail to query the provisioned AppX applications for the user during sign-out.
  • MSIX folders that should not be backed up, would be removed during sign-out instead of only removing the contents of those folders.
  • New Microsoft Teams crashes or fails to start in Windows Server 2019.
  • New Microsoft Teams would display an error during launch with The parameter is incorrect.
  • New Microsoft Teams would display an error during launch with Invalid function.
  • New Microsoft Teams would not on-demand register during sign-in when using the ODFC container.
  • New Microsoft Teams would not on-demand register during profile creation and would not register during future sign-ins, despite being installed.
  • User-based Group Policy settings would persist in the user's profile after the policy setting was removed or set to disabled.

 

Release Notes | FSLogix 2210 hotfix 4 

 

Updated May 14, 2024
Version 1.0

42 Comments

Show More
  • frawil's avatar
    frawil
    Copper Contributor
    May 15, 2024

    Same problem with persistent rds (not citrix) ... 

     

    Registering the app does'nt work for me... 

     

    I hope we found a solution 

  • nick_ap's avatar
    nick_ap
    Copper Contributor
    May 14, 2024

    In a non-persistent VDI (Server 2019), you need to use a PowerShell script to register the TeamsV2 application. Once it's registered, FSLogix HF4 will be able to keep it registered in the user profile. We used a simple script at login that runs once for the user using Citrix WEM:

     

    if (-not (Get-AppxPackage -Name "*Teams*")) {
    Start-Job -Name RegisterTeams -ScriptBlock { Add-AppxPackage -RegisterByFamilyName -MainPackage MSTeams_8wekyb3d8bbwe -ErrorAction SilentlyContinue }
    Wait-Job -Name RegisterTeams
    Start-Process -FilePath C:\Windows\explorer.exe -ArgumentList "shell:AppsFolder\MSTeams_8wekyb3d8bbwe!MSTeams" -ErrorAction SilentlyContinue
}

     

     

  • The_Copernicus's avatar
    The_Copernicus
    Copper Contributor
    May 14, 2024

    Mark_Blackwood I can also confirm having installed FSLogix Hotfix 4 and still get the error, using non-persistent Citrix VDI machines in my case. I had been working around it by registering the app with powershell via a logon script. I took that out for this test.

     

    edit: I may have been to hasty. The other members of my team including myself had Teams open fine this morning. Looks promising, but the true test will be when we push it out to a group that has never had New Teams

  • Mark_Blackwood's avatar
    Mark_Blackwood
    Copper Contributor
    May 14, 2024

    We have tested this morning with 2210 HF4 installed on one of our Persistent Citrix VDI's and we are still randomly getting "The parameter is incorrect" error at logon.

     

    We currently do have a case open regarding this.

  • richardhughes-chen's avatar
    richardhughes-chen
    Copper Contributor
    May 14, 2024

    Does this resolve app not starting when layered on a Citrix App Layer? Citrix recently released a patch for the ELM which supports New Teams in its own layer but still have the issue with Teams not opening. Customer is using FSLogix ODDC containers as well as Profile containers.

     

     

  • Jason_Parker's avatar
    Jason_Parker
    Icon for Microsoft rankMicrosoft
    May 14, 2024

    Which image? The images with M365 apps are always delayed by 48 hours from patch Tuesday.

  • elliottpark_msft's avatar
    elliottpark_msft
    Icon for Microsoft rankMicrosoft
    May 14, 2024

    Will the new FSLogix hotfix 4 be included in the latest Windows 11 Multisession image in Azure marketplace? I have tried deploying the latest image about 30 minutes ago and it doesn't appear to have the latest hotfix version of FSLogix. Thank you.

  • mattnation's avatar
    mattnation
    Copper Contributor
    May 14, 2024

    I'm prompted to sign in to my msft account to try and download and then told i don't have permission to?