Conversations involving multiple participants, allowing collaboration and information sharing in Teams
I don't see any process or service on my system running ms-teamsupdate.exe. Can you please expand on your suggestion?
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
With the recent update to Teams the spellchecker is not working correctly. It will show the misspelled word but when you click on it there is no longer a suggested spelling popping up. We (Several in the company) have noticed this on the latest update to the following version, Microsoft Teams Version 1.6.00.21970 (64-bit).
I have already gone in and deleted the setting.json file, that will work for a short time 10-20 minutes then back to not given a suggestion.
I am seeing an old issue TM390278 https://answers.microsoft.com/en-us/msteams/forum/all/microsoft-teams-spell-check/337ee648-af60-4cf4-8336-a1c68f3a1d78
I tested if we use the pop out feature and chat in a seperate window spellchecker will work as intended it appear to be the same issue as posted before.
Conversations involving multiple participants, allowing collaboration and information sharing in Teams
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
I don't see any process or service on my system running ms-teamsupdate.exe. Can you please expand on your suggestion?
needs a mod to close down the teams updater
C:\Program Files\WindowsApps\MSTeams_23335.232.2637.4844_x64__8wekyb3d8bbwe
all the work arounds work!
BUT
WHY IS THIS STILL HAPPENING.
you shouldn't have to reset or restart teams every few days.
That's very impressive, and it's absurd you have to do that. But nice work.
I am now using this PowerShell code to fix my spell check. Rather than wiping out the entire directory which deletes custom backgrounds, I delete everything else in the folder.
To make it easier to run, I used the PS2EXE module to compile it to an EXE.
Get-Process -name ms-teams | Stop-Process
$User = $ENV:UserName
$TeamsFolder = "C:\Users$User\appdata\local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams"
Get-ChildItem -Path $TeamsFolder -File | Remove-item -Confirm:$false -Force
Remove-Item -Path $TeamsFolder\Logs -Recurse -Confirm:$false -Force
Remove-Item -Path $TeamsFolder\tmp -Recurse -Confirm:$false -Force