Clear the cache of the new Teams Client (V2)

For the cleanup of cached data in the Teams Classic Client (V1), Microsoft describes in the documentation which data must be deleted. These are primarily all files and folders in %appdata%\Microsoft\Teams  (Example C:\Users\<Username>\AppData\Roaming\Microsoft\Teams).

Local data from Teams Client V1
Local data from Teams Client V1

The documentation for the new Teams client has not yet been updated. The instructions for the V1 client do not help with the V2 client or delete the data of the wrong client.
The new Teams client uses %LocalAppData%\Packages\MSTeams_8wekyb3d8bbwe for the cache (Example C:\Users\<Username>\AppData\Local\Packages\MSTeams_8wekyb3d8bbwe).

Local data from Teams Client V2
Note before deleting

Deleting the folder cleans up some locally configured settings, such as the language of the Teams client, (if in use) accounts from other organizations in the Org Switcher, and others.

Deleting Teams V2 cache with Windows Explorer
  1. Close the Teams client completely via the Windows taskbar.
Close the Teams client
Close the Teams client
  1. Delete the entire folder MSTeams_8wekyb3d8bbwe under %LocalAppData%\Packages.
  2. Restart the new Teams client. Teams recreates the deleted folder. The Teams client can restart itself several times due to the deleted folder, and the client may want to update itself after the restart.

Addition from 6. December 2023:
When starting the Teams client manually, ensure you start the correct client. Windows often shows Teams Classic as the first option, depending on the search. Start the client with the “New” logo in the icon.

Ensure to start the new Teams
Ensure to start the new Teams

Deleting Teams V2 cache with PowerShell

The PowerShell commands can help. The new Teams client should be started.

PowerShell
# For the new Teams client (V2) 

$TeamsProcPath = (Get-Process ms-teams).Path
Get-Process ms-teams | Stop-Process

$TeamsV2CachePath = ($env:LOCALAPPDATA + "\Packages\MSTeams_8wekyb3d8bbwe")
if(Test-Path $TeamsV2CachePath)
{ Remove-Item $TeamsV2CachePath -Force -Recurse } else 
{ Write-Host "Path not available: $TeamsV2CachePath" -f red }

Start-Process -FilePath $TeamsProcPath


Teams recreates the deleted folder. The Teams client can restart itself several times due to the deleted folder, and the client may want to update itself after the restart.

Share
Avatar photo

Tobias Asböck

Tobias is a Senior System Engineer with around ten years of professional experience with Microsoft 365 products such as SharePoint Online, OneDrive for Business, Teams Collaboration, Entra ID, Information Protection, Universal Print, and Microsoft 365 Licensing. He also has 15+ years of experience planning, administering, and operating SharePoint Server environments. Tobias is a PowerShell Scripter with certifications for Microsoft 365 products. In his spare time, Tobias is busy with updates in the Microsoft 365 world or on the road with his road bike and other sports activities. If you have additional questions, please contact me via LinkedIn or [email protected].

Leave a Reply

Your email address will not be published. Required fields are marked *