Lesson 6/9
New Teams stuck? Repairing it in 5 minutesTeams does not get repaired the way it used to! A new machine-wide MSI architecture, clearing WAM tokens, conflicting identities... Here are the real commands to repair the new Teams in a few minutes.
☰
Contents
19
▾
0:00 Introduction: why Teams is hard to repair 0:17 The old Teams and its MSI architecture problems 0:45 The new Teams architecture (machine-wide MSI + WebView2) 1:13 Common problems: expired tokens and identity conflicts 1:52 The key command: dsregcmd /status to diagnose the domain join 2:38 Advanced options: clean account and listing known accounts 3:09 The full identity repair procedure (WAM, Identity Cache, AD Broker) 3:38 SSO tip: use two separate browser profiles 4:22 Demo: installing and uninstalling Teams 5:31 Why reinstalling Teams gets you nowhere 5:56 Advanced options: reset and repair from Windows settings 6:28 Running the reset from PowerShell 6:44 Live demo of the Teams identity reset 7:33 Clearing identities with the four PowerShell commands 8:01 Result: Teams restarted with the main identity only 8:30 Managing organisations in My Account (leaving an organisation) 8:57 Recap: identity reset vs application reset 9:06 Collecting the support files and analysing the logs with AI 10:28 Conclusion and call to action
