Can we install the preview of FSLogix 2210 hotfix 3 on Azure Virtual Desktop as it's required by the new Teams application?

Question

Note: Based on common issues that we have seen from customers and other sources, we are posting these questions to help the Azure community.

---

Can we install the FSLogix 2210 Hotfix 3 for compatibility with the new Teams application on Azure Virtual Desktop (AVD) multisession VMs? The blog notes that this is a preview version.

Answer 1

Note: Based on common issues that we have seen from customers and other sources, we are posting these questions to help the Azure community.

---

Yes, you need to install FSLogix 2210 hotfix 3 Preview (2.9.8716.30241) to ensure proper integration with the new Teams client in a Virtual Desktop Infrastructure (VDI) environment.

Since this hotfix version is still in preview, it is recommended to first deploy it in your non-production environments. This allows you to fully test and understand the new updates and fixes before rolling it out to your production workloads:

FSLogix Blog: Announcing general availability of FSLogix 2210 hotfix 3!

---

Initial reports have been promising:

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