Teams crashes on Windows 11 + VM ARM64

Pierre Cogné 0 Reputation points
2026-09-10T19:39:27.6033333+00:00

Hi,
I am running Windows 11 (fully uptodate) on a Macbook pro M3 (fully up to date) using Parralels Desktop (up to date as well).
Teams is installed on the Windows 11 VM and has been working fine for years.
Recently, for a couple months now, I've been unable to start it anymore.
Evry time I try it first create a window with the teams logo appairing briefly in the middle and then the windows disappears straight away.
It does not crash completly as Teams then appears in the system tray, but neither the double click or the "right click + open" does anything at all.

I already tried desktop app, windows stord app, tried to reinstall, tried to repair, reset, and tried to delete the appdata folder content.

I start to run out of ideas, and any help would be much appreciated :-)

Thanks in advance

Pierre

Microsoft Teams | Microsoft Teams for business | Other
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Lin v 1,205 Reputation points Independent Advisor
    2026-09-10T20:08:48.51+00:00

    Hi Pierre,

    The behavior you described is quite similar to a recently documented issue affecting some ARM-based Windows 11 devices, where Teams may fail to launch after briefly displaying the splash screen. (KB5124008)

    However, from what you've shared, it seems the issue persists after you've tried the Microsoft-documented workaround. If you are using a work or school account, and given that you have already tried several common troubleshooting steps without success, you may wish to contact your IT administrator to open a support case with Microsoft for further investigation, as additional diagnostics or product-specific troubleshooting may be required to determine the underlying cause.

    If you are unsure who your IT administrator is, you can refer to this official Microsoft guide for assistance: How do I find my Microsoft 365 admin? - Microsoft Support.

    A technical support engineer can then initiate a remote session, review backend settings, and run diagnostics. If needed, they can escalate the case to specialized engineering teams who are well-equipped to perform advanced troubleshooting and provide targeted solutions.

    I hope everything gets sorted out soon. Feel free to let me know if you have any questions.

    Was this answer helpful?

    0 comments
  2. Pierre Cogné 0 Reputation points
    2026-09-10T19:59:36.6233333+00:00

    The below did not seem to work either:

    This matches a documented issue on ARM-based Windows 11 devices where Microsoft Teams and the new Outlook for Windows might fail to launch or close unexpectedly after Windows security updates released on or after August 11, 2026. It is reported on devices such as Surface Pro 11 and Surface Laptop 7, and is most likely on new or freshly imaged PCs that have not yet installed Microsoft Store updates.

    The documented fix is:

    1. Install the latest Windows update for the VM.
      • For Windows 11 24H2/25H2, the issue was resolved in updates released September 8, 2026 or later, including KB5124008.
        • For Windows 11 26H1, the issue was resolved in updates released September 8, 2026 or later, including KB5124012.
        1. If the VM is on an update before September 8, 2026, apply the workaround:
          • Open Microsoft Store.
            • Select Downloads > Check for updates.
              • Install the latest update for the Auto Super Resolution Package to version 1.0.19.0 or later.

    Because repair, reset, reinstall, and deleting AppData were already tried, those are unlikely to help if this is the ARM launch issue.

    If Teams still does not open after the Windows update and Store package update, two additional documented checks are relevant for launch failures:

    1. Verify that TEMP and TMP do not point to a reparse point. Use:

    PowerShell

    gci env:* | ?{@("TEMP", "TMP").Contains($.Name)} | %{$.Value+" - "+((gp $_.Value).Attributes -match 'ReparsePoint')}

    If the command returns True for either variable, set that environment variable to a location that is not a reparse point.

    2.                 Verify the account has Read permission to the required AppData paths under:

      - %USERPROFILE%\AppData\Local
  
     - %USERPROFILE%\AppData\Local\Microsoft
     
        - %USERPROFILE%\AppData\Local\Microsoft\Windows
        
           - related subfolders such as __Explorer__, __History__, __INetCache__, and __INetCookies__

    Also check whether the Windows user profile uses a symlink or mapped drive for C:\Users. A documented Teams startup issue can show a white screen or prevent normal startup when a Unix symlink or mapped drive is used. In that case, Teams should be installed in the default location under user\Appdata. If the mapping must remain, the documented alternative is to use the web version of Microsoft Teams.

    AI-generated content may be incorrect. Read our transparency notes for more information.

     

    This matches a documented issue on ARM-based Windows 11 devices where Microsoft Teams and the new Outlook for Windows might fail to launch or close unexpectedly after Windows security updates released on or after August 11, 2026. It is reported on devices such as Surface Pro 11 and Surface Laptop 7, and is most likely on new or freshly imaged PCs that have not yet installed Microsoft Store updates.

    The documented fix is:

    1. Install the latest Windows update for the VM.
      • For Windows 11 24H2/25H2, the issue was resolved in updates released September 8, 2026 or later, including KB5124008.
        • For Windows 11 26H1, the issue was resolved in updates released September 8, 2026 or later, including KB5124012.
        1. If the VM is on an update before September 8, 2026, apply the workaround:
          • Open Microsoft Store.
            • Select Downloads > Check for updates.
              • Install the latest update for the Auto Super Resolution Package to version 1.0.19.0 or later.

    Because repair, reset, reinstall, and deleting AppData were already tried, those are unlikely to help if this is the ARM launch issue.

    If Teams still does not open after the Windows update and Store package update, two additional documented checks are relevant for launch failures:

    1. Verify that TEMP and TMP do not point to a reparse point. Use:

    PowerShell

    gci env:* | ?{@("TEMP", "TMP").Contains($.Name)} | %{$.Value+" - "+((gp $_.Value).Attributes -match 'ReparsePoint')}

    If the command returns True for either variable, set that environment variable to a location that is not a reparse point.

    2.                 Verify the account has Read permission to the required AppData paths under:

      - %USERPROFILE%\AppData\Local
  
     - %USERPROFILE%\AppData\Local\Microsoft
     
        - %USERPROFILE%\AppData\Local\Microsoft\Windows
        
           - related subfolders such       as __Explorer__, __History__, __INetCache__,       and __INetCookies__

    Also check whether the Windows user profile uses a symlink or mapped drive for C:\Users. A documented Teams startup issue can show a white screen or prevent normal startup when a Unix symlink or mapped drive is used. In that case, Teams should be installed in the default location under user\Appdata. If the mapping must remain, the documented alternative is to use the web version of Microsoft Teams.

    AI-generated content may be incorrect. Read our transparency notes for more information.

     

    Was this answer helpful?

    0 comments

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.