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 ...
tk093 Hello Christopher. Could you please let me know if spell check ever worked on new teams. As far as my understanding goes it never worked as it is listed as a known issue in their page.
Please refer to the page https://learn.microsoft.com/en-us/microsoftteams/new-teams-known-issues.
- Language-aware spell checking is currently not available in the new Teams. The team is focusing on this issue with a high priority. Check back for updates.
- On Windows, spell checking is limited to English (United States) dictionaries. Until this feature is fixed, users can disable spell checking from the settings page.
- Some spell checker suggestions for English can be inaccurate. A Windows fix is pending, with an estimated rollout date of January. Users can choose to disable spell checking from the settings page until then.
Are you using windows 10 or 11? Can you let me know what is the current webview version you have?
Please go to setting -> Add or remove programs -> search for webview. It has to be version 120 or above.
Please check and get back to me.
I can confirm that spell check feature was functional in "New" Teams for our organization late last week. The functionality was slow (5-10 second delay before red-underlines) in the "New" app, but it was working.
Over the last few days, most users utilizing the "New" desktop app have reported a total loss of spell check functionality. Spell check still works in the "Classic" desktop app and in the "New" browser app, but those both likely used different reference dictionaries?Windows 10
WebView2 121.0.2277.83
Microsoft Teams version 23335.232.2637.4844.
Client version is 49/23113028724.
- It doesn't look like it's working for en-US dictionaries either.
- Tried many tricks online (bringing over Chrome's dictionary, ect) but still no luck. Such a simple feature to not have working. Reverted back to the classic one for now.
