Forum Discussion
Spell check broken in new Teams 2.0 client
Greetings, we have about 100 users running Teams 2.0 and a handful of users, myself included, are seeing issues with the spell check. It will work for maybe 10 minutes, maybe a hour, maybe a day or ...
I fixed this by going to:
Installed apps > Microsoft Teams > Click the 3 dots on the right side and select "Advanced options"
Then at the bottom select "Reset"
This is the new way to clear the Teams cache as the old location is for the Classic Teams.
You wouldn't lose any data or have to sign back in. I have had to do this a few times already so it looks like it's a temporary fix for now.
Installed apps > Microsoft Teams > Click the 3 dots on the right side and select "Advanced options"
Then at the bottom select "Reset"
This is the new way to clear the Teams cache as the old location is for the Classic Teams.
You wouldn't lose any data or have to sign back in. I have had to do this a few times already so it looks like it's a temporary fix for now.
I followed the "reset" instructions from Installed Apps and it corrected the spellchecker. My New Teams now provides spell checking assistance as expected.
- FYI: The RIHelpDesk recommendation of resetting new Teams to fix spellcheck worked for me:
In the "Windows Settings" app, get to "Apps & features";
Select the "Microsoft Teams (work or school)" item and then click "Advanced options";
Click the "Reset" button and then confirm your selection.can confirm - worked for me
As mentioned earlier, resetting the app or renaming the folder is only a temporary fix.
Microsoft do have this listed on the Service Health page TM711150
More info: As a workaround, affected users may be able use the following steps to clear their cache:
- Close and quit the new Microsoft Teams application
- Delete the folder: %localappdata%\packages\msteams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams
- Start the new Microsoft Teams applicationCurrent status: We're initiating deployment of the previously mentioned fix to restore spell checking for affected users. We anticipate that the deployment will complete by our next scheduled update, at which time we'll monitor the service environment to confirm that the issue is resolved.
