If you’ve ever had a user say:

“The dial pad is there, but I can’t click it.”
“Join meeting does nothing.”
“Teams opens, but it’s just broken.”

You already know what’s coming.

And no – it’s usually not licensing.

In many cases, it’s a corrupted local Teams client.

In this article, I’ll show you:

• Why Microsoft Teams breaks like this
• Which common error codes this reset resolves
• When the issue is client-side vs policy-side
• And a full PowerShell script to fix it properly

The Real Problem: Teams Is a Web App in Disguise

Microsoft Teams (especially New Teams) is essentially:

• WebView2
• Cached profile data
• AAD token storage
• Local state
• MSIX container

When something corrupts:

• WebView2 rendering
• Authentication tokens
• Local Teams cache
• SSO credentials
• Proxy configuration

The result is classic:

• Dial pad visible but not clickable
• Join meeting button does nothing
• Blank white screen
• Endless loading spinner
• Random sign-in prompts

Common Microsoft Teams Error Codes This Script Fixes

This reset script resolves a large number of client-side errors, including:

Authentication Errors

• CAA50021
• CAA50024
• CAA20002
• 0xCAA70004
• 0xCAA82EE2
• 0x80048823
• 0x800704CF

Meeting Join / UI Errors

• Join button unresponsive
• Dial pad not clickable
• Blank calendar view
• “We couldn’t connect you” error
• “Something went wrong” generic UI errors

WebView2 / Rendering Issues

• White screen on launch
• UI elements missing
• Buttons visible but not interactive

Network / Proxy Related

• 0x80072EFD
• 0x80072EE7
• 0x801901F7

If Teams Web works but the desktop client does not -> this script is almost always the fix.

When This Script Will NOT Help

If the dial pad is greyed out, the problem is not the client.

It’s usually:

• No Teams Phone license
• No OnlineVoiceRoutingPolicy
• No Calling Policy
• Enterprise Voice not enabled

Client reset won’t fix licensing.

Clickable but broken = client
Greyed out = policy

Important distinction.

What the Script Actually Does

This is not just a “delete cache” script.

It performs a full user-context reset:

1. Stops all Teams-related processes
2. Removes Classic Teams folders
3. Removes New Teams MSIX profile folders
4. Clears WebView2 cache
5. Optionally removes stored AAD/Office credentials
6. Optionally resets WinHTTP proxy
7. Relaunches Teams cleanly

It does NOT:

• Uninstall Teams
• Change licensing
• Affect other users
• Modify tenant configuration

Safe for enterprise usage.

Reset-TeamsClient.ps1 – https://github.com/ThomasMarcussen/assortedScripts/blob/master/Reset-TeamsClient.ps1