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 have been experiencing this issue for months and I have tried all the suggestions. Most of them worked, for an hour or two, then it would break again. As a dyslexic who is currently working 100% remote, and using Teams as my primary communication channel, this is EXTREAMLY FRUSTRATING.
On a positive note, this afternoon I received a Teams update and spell check is now working. We will see how long it lasts.
Microsoft Teams version 24004.1307.2669.7070
Microsoft Teams Client version 49/24010419128
- How did you get that new version? MS doesn't show that version on their website.
The update was presented to me in Teams. A small notification was shown next to my picture in the top right corner of the client. I did not get a screenshot but marked the location here:
After the client restarted the spell check was working. So far it is still working (20 hours and two reboots later). This is the longest it has functioned for me in months.
I work in the IT department, so I am approved to get public preview versions of Teams, however I am currently not on a preview version.so does anyone know which of the following corresponds to a working version of Team 2.1 client for x64 with a consistently working spelling checker?
https://github.com/ItzLevvie/MicrosoftTeams-msinternal/blob/master/defconfig2the latest 2.1 seems to point to;
24045.1000.2697.7733 (win-x64) - published on Wednesday, February 14, 2024 at 11:55 AM with 168 MB: https://staticsint.teams.cdn.office.net/production-windows-x64/24045.1000.2697.7733/MSTeams-x64.msix
Just don't click on the "Update now" button otherwise in our case it reverts back to a problem release of
You have Microsoft Teams version 23335.232.2637.4844.
You've got the latest version. It was last updated on 15/02/2024.
The client version is 49/24010419128.The problem release appears to corresponds to the version to the latest Public (R4) build of Microsoft Team
where as the newer 24045 version (which so far hasn't had the same issue) corresponds to the latest Canary (R0) build of Microsoft Teams
- I suppose Teams is on an Auto Update process - I did not manually check for updates, but noticed it was updated today, 2/14
- How did you notice it was updated? I am not seeing any updates on my end when and if they do.
