Share via

Get-AppxPackage returns empty for affected users after logon

Lidis Scarlenza 20 Reputation points
2026-05-01T06:45:38.4666667+00:00

We are currently deploying the new Microsoft Teams client in a non-persistent env using teamsbootstrapper.exe -p, and the optimization registry keys

New-Item -Path "HKLM:\SOFTWARE\Microsoft\Teams" -ForceNew-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Teams" -Name "disableAutoUpdate" -Value 1 -PropertyType DWORD -Force
New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Teams" -Name "IsWVDEnvironment" -Value 1 -PropertyType DWORD -Force

However, after user logon, Teams intermittently fails to register correctly for existing FSLogix profiles. Get-AppxPackage -Name MsTeams returns empty for affected users, while Get-AppxPackage -Name MsTeams -AllUsers shows the package staged correctly on the machine.

Need the guidance pls

Microsoft Teams | Development
Microsoft Teams | Development

Building, integrating, or customizing apps and workflows within Microsoft Teams using developer tools and APIs

0 comments

Answer accepted by question author

  1. Vergil-V 12,530 Reputation points Microsoft External Staff Moderator
    2026-05-01T07:29:55.8733333+00:00

    Hi @Lidis Scarlenza 

    To ensure I have a clear understanding of the situation, I would like to clarify the following point.

    Could you please confirm which version of FSLogix is currently in use? 

    It is recommended to install the latest FSLogix version, specifically FSLogix 2210 hotfix 4 (2.9.8884.27471) or later. This version includes the most recent updates and fixes, and it aligns with the recommendation provided by the Q&A Assist. 

    For further troubleshooting, you may also review the related event logs as outlined below. 

    1/ Open Event Viewer on the affected machine > Applications and Services Logs > Microsoft > Windows. 

    2/ Check the logs available under the following categories. 

    • AppxPackagingOM > Microsoft-Windows-AppxPackaging/Operational
    • AppXDeployment-Server > Microsoft-Windows-AppXDeploymentServer/Operational

    3/ Review logs under AppXDeployment-Server. 

    If you observe any specific error codes, you can refer to the documentation at the link below for detailed explanations of each code: https://learn.microsoft.com/en-us/windows/win32/appxpkg/troubleshooting#common-error-codes 

    I hope these steps provide additional clarity and help move the investigation forward.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    1 person found this answer helpful.
    0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Q&A Assist
    2026-05-01T06:45:57.3766667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The behavior matches a known issue with new Microsoft Teams (MSIX) in VDI when profile management tools (including FSLogix before 2210 Hotfix 4) fail to register the package at user level, even though the package is correctly staged on the machine.

    In this failure mode:

    • Get-AppxPackage -Name MsTeams for the affected user returns no output.
    • Get-AppxPackage -Name MsTeams -AllUsers from an elevated prompt shows the package with Status OK.

    The documented resolution is:

    1. Update FSLogix to a fixed build
      • Install or upgrade to FSLogix 2210 Hotfix 4 (2.9.8884.27471) or later on the VDI image. This build includes special handling for the new Teams MSIX in virtual desktops and fixes the intermittent user-level registration failures after logon.
    2. Ensure Teams is installed system-wide for all users
      • New Teams must be installed as an MSIX for all users (system-wide), not per-user. If users previously installed Teams in their own context, those per-user MSIX registrations are not preserved across non-persistent sessions and can be cleaned up by FSLogix at sign-out, causing Teams to appear missing or fail to register on next logon.
      • Review and follow the guidance in “Upgrade to new Teams for Virtualized Desktop Infrastructure (VDI)” to ensure the deployment is done system-wide before enabling users to switch to the new Teams experience.
    3. Re-test affected profiles after FSLogix upgrade
      • After updating FSLogix and confirming Teams is installed system-wide, test with existing FSLogix profiles:
        • Log on with an affected user.
        • Run Get-AppxPackage -Name MsTeams in a non-elevated PowerShell session.
        • Teams should now be registered for the user and launch correctly.

    If the issue persists after upgrading FSLogix to 2210 Hotfix 4 or later and confirming system-wide Teams installation, collect logs and engage Microsoft Support, as the documented VDI registration issue should be resolved by that FSLogix version.

    References:

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.