This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Spell checking in multiple languages is not working in Microsoft Teams as described here:
https://support.microsoft.com/en-us/office/check-your-spelling-in-multiple-languages-in-microsoft-teams-0e269374-0cac-4a22-a377-53f01e05a6d4
It has happened after the installing new Teams desktop app on my Windows 11 (details below). Setting in Teams -> Settings -> General -> Enable spell check (requires restarting Teams) is enabled and Teams was restarted.
Unfortunately clearing following directories did not solve the issue:
%temp%,
%appdata%\Microsoft\Teams
%localappdata%\SquirrelTemp,
My Teams version is:
You have Microsoft Teams version 23257.2620.2442.7817.
You've got the latest version. It was last updated on 10/17/2023.
The client version is 49/23092912307.
Additional features, settings, or issues not covered by specific Microsoft Teams categories
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.
Hello Umar.
This is actually a Known issue for the New Teams : Language-aware spell checking is currently not available in the new Teams. The team is focusing on this issue with a high priority.
Known issues in the new Microsoft Teams desktop client - Microsoft Teams | Microsoft Learn
appears to be working ok for me now -
Okay, so this issue was noticed in October of 2023, then replied in December 2023 that this is a known issue and "The team is focusing on this issue with a high priority. "
It is now February 2024, and the issue is still there.
What the ****, MS? You push "New Teams" on us in a buggy state and then drag your feet on fixing a bug that should have never been present upon release. Did you put your new Activision-Blizzard employees onto this development?
Thanks for the info, but I'm surprised this wasn't picked up during user acceptance testing before it was released! So when will this simple fix be reconciled?
Yes, but classic Teams is being retired in 2 months... So that workaround is not for long!