The new Teams app was rebuilt to be faster and lighter — and on most machines it is. But on your Arm64 laptop it crashes when you join meetings, freezes on the loading screen, or drops calls while chat hums along fine. When your workday runs through Teams, an unstable client is not a minor annoyance; it is missed standups, frozen presentations, and that awful moment when your video locks mid-sentence.

Teams on Arm64 has one critical requirement: you must run the native Arm64 build. The emulated x64 build technically launches, but its media engine — the part handling camera, microphone, and screen share — suffers disproportionately under emulation. Beyond architecture, Teams shares the familiar WebView2 rendering stack with Microsoft’s other modern apps, and its local cache corrupts often enough that clearing it is practically routine maintenance.

The fixes below move from architecture check to cache to deep repair, in the order a support engineer would try them. This diagnose-then-repair rhythm also settles other chat and dev apps on Arm hardware, from Telegram Desktop acting up on Arm Windows to Postman refusing to work on an Arm machine . And if Teams instability arrived alongside system crashes, consider the hardware layer: an NPU causing blue screens on Windows 11 can produce app crashes that look like Teams bugs but start in the driver stack.

Why this happens

  • Emulated x64 build installed: the wrong architecture build runs poorly, especially its media engine.
  • Corrupted Teams cache: stale local data breaks startup, chat loading, and meeting joins.
  • Damaged WebView2 runtime: the shared renderer behind Teams’ interface is broken or outdated.
  • Stale credentials: expired sign-in tokens cause silent failures in meetings and file access.
  • Permission faults: Windows privacy settings block the camera or microphone Teams needs.
  • Network interference: firewalls or VPNs block Teams’ media ports while chat still works.
  • Outdated client or Windows: old versions miss fixes for known Arm64-specific bugs.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Install the native Arm64 Teams build

This is the highest-impact step on a Snapdragon laptop. Open Task Manager’s Details tab while Teams runs and check the architecture column: Arm64 is correct, x64 means the emulated build. Uninstall it and download the native Arm64 installer from Microsoft’s official Teams download page. The native build transforms call quality and stability — many “Teams is broken on my Arm laptop” stories end here.

  1. Open Task Manager and check the Teams process architecture.
  2. If it shows x64, uninstall Teams from Installed apps.
  3. Download the native Arm64 Teams installer from Microsoft.
  4. Install it, sign in, and verify Task Manager shows Arm64.

Fix 2: Clear the Teams cache properly

The new Teams stores cache in folders that survive a casual reinstall, which is why reinstalling alone sometimes changes nothing. Fully quit Teams (including the system tray icon), then clear the documented cache directories for the new client. This wipes stale meeting artifacts and corrupted chat indexes without touching cloud data. When Teams hangs on the loading screen, this is the fix support reaches for first.

  1. Right-click the Teams tray icon and choose Quit.
  2. In File Explorer, open the Teams cache folders under AppData.
  3. Delete the contents of the cache and local storage folders.
  4. Restart Teams, sign in, and test joining a meeting.

Fix 3: Check camera, microphone, and permissions

When calls fail but chat works, suspect devices and permissions before the app. Open Settings, then Privacy and security, and confirm Teams may use the camera and microphone. Then test the devices in Teams settings under Devices with a test call. On AI PCs with NPU-enhanced cameras, also check the manufacturer’s camera utility, since its effects pipeline can conflict with Teams. Microsoft documents these permission paths in the official support hub .

  1. In Settings, Privacy and security, check Camera and Microphone permissions for Teams.
  2. In Teams settings, open Devices and run the test call.
  3. Disable third-party camera effects while testing.
  4. Retry a real meeting to confirm the fix.

Fix 4: Repair WebView2 and update everything

Teams renders its interface through WebView2, so a damaged runtime causes blank windows and UI freezes that look like Teams bugs. Reinstall the Evergreen WebView2 runtime from Microsoft, then update Teams itself and run Windows Update. These three — runtime, app, OS — should move together; a new Teams on an old runtime is a classic mismatch. Restart after updating so every component registers cleanly.

  1. Reinstall the WebView2 Evergreen Standalone Runtime from Microsoft.
  2. In Teams settings, check for and install client updates.
  3. Run Windows Update and install all pending updates, then restart.

Fix 5: Rule out network interference

Teams chat uses standard HTTPS, but calls need media ports that VPNs, strict firewalls, and some office networks block. If calls drop on one network but work on another, the network is guilty, not Teams. Disconnect the VPN and test a call; try a phone hotspot as a clean baseline. For persistent office-network issues, IT may need to allowlist Teams’ media endpoints.

  1. Disconnect the VPN and place a test Teams call.
  2. Try the same call on a mobile hotspot.
  3. If the hotspot works, the primary network is filtering media traffic.
  4. Ask IT to verify firewall rules for Teams media ports.

Fix 6: Full clean reinstall of Teams

When nothing else works, do the thorough version: quit Teams, uninstall it, manually clear leftover AppData folders, restart the machine, then install the native Arm64 build fresh. The restart between uninstall and reinstall matters — it releases file locks that let corrupted data survive. Sign in afterward and let the client fully sync before joining a meeting.

  1. Quit Teams fully and uninstall it from Installed apps.
  2. Delete the remaining Teams folders under AppData manually.
  3. Restart the laptop, then install the native Arm64 Teams build.
  4. Sign in, let sync complete, then test a meeting.

Closing

Teams on Arm64 lives or dies by three things: the native build, a clean cache, and unobstructed media traffic. Check the architecture first — it resolves more cases than everything else combined — then clear the cache and verify permissions before reaching for reinstalls. Keep Teams and Windows updating together afterward, since the client and its WebView2 runtime evolve as a pair. If calls still fail everywhere after a clean native install, the evidence points at the network or the account, and that is where Microsoft support can pick up the trail with backend logs you cannot see.

Frequently asked questions

Is there a native Arm64 version of the new Teams app?
Yes, Microsoft ships a native Arm64 build of the new Teams client, and it is the one you want on a Snapdragon laptop. The native build avoids the emulation layer entirely, which means better battery life, smoother calls, and fewer crashes. Verifying the architecture is the first thing to check.
Why do my Teams calls freeze but chat keeps working?
Calls use the media engine while chat uses simple web requests, so they fail independently. Frozen video or dropped audio usually points to camera, microphone, or network issues rather than a broken install. Check device permissions and try a call on a different network before reinstalling.
Will clearing the Teams cache delete my chats?
No. Your chats, teams, and files live in the Microsoft 365 cloud. Clearing the cache only removes local temporary data and forces a fresh download. It is one of the safest and most effective Teams repairs, and support engineers recommend it routinely.
Should I use Teams on the web instead of the app?
The web version at teams.microsoft.com is a fine fallback and an excellent diagnostic tool. If the web works but the app does not, the fault is local to the app installation. The desktop app offers better notifications and background effects when it is healthy.