
Get-Process -ProcessName Chrome| Stop-Process -Force Write-Host "Stopping Chrome Process" -ForegroundColor Yellow Write-Host "Teams Disk Cache Cleaned" -ForegroundColor Green Get-ChildItem -Path $env:APPDATA\"Microsoft\teams\tmp" | Remove-Item -Confirm:$false Get-ChildItem -Path $env:APPDATA\"Microsoft\teams\Local Storage" | Remove-Item -Confirm:$false

Get-ChildItem -Path $env:APPDATA\"Microsoft\teams\Indexeddb" | Remove-Item -Confirm:$false Get-ChildItem -Path $env:APPDATA\"Microsoft\teams\gpucache" | Remove-Item -Confirm:$false Get-ChildItem -Path $env:APPDATA\"Microsoft\teams\cache" | Remove-Item -Confirm:$false Get-ChildItem -Path $env:APPDATA\"Microsoft\teams\databases" | Remove-Item -Confirm:$false Get-ChildItem -Path $env:APPDATA\"Microsoft\teams\blob_storage" | Remove-Item -Confirm:$false Get-ChildItem -Path $env:APPDATA\"Microsoft\teams\application cache\cache" | Remove-Item -Confirm:$false Write-Host "Clearing Teams Disk Cache" -ForegroundColor Yellow

Write-Host "Teams Process Sucessfully Stopped" -ForegroundColor Green Get-Process -ProcessName Teams | Stop-Process -Force Write-Host "Stopping Teams Process" -ForegroundColor Yellow $challenge = Read-Host "Are you sure you want to delete Teams Cache (Y/N)?" Through pain of trial I have now given up and made a PowerShell script to do this for me, shared below. Only after clearing these locations is it considered a clean start for the Teams app.

Unlike Skype for Business Online where in-band policy changes took longest 30 minutes, with Teams we can be waiting days, and I mean that literally. One thing for sure is that if you are deploying Teams you’ll quickly find that your admin controlled policy settings take a random amount of time to come into effect on the target machines. Microsoft Teams cache behaviour is a lot to be desired if I am honest.
