Forum Discussion
Right-Clicking Chat Field & Spell Checking Not Working
We are encountering an issue with the last few revisions of Teams. When right-clicking a chat field to receive a spell-checking suggestion or right-clicking to paste, no right-click menu appears.
If you close and clear the Teams cache in %appdata%\Microsoft\Teams and restart the client, it will work fine. However, if you close the client again, right-click functions no longer work. What is interesting is that this only happens on the Chats with groups or individuals. You can right-click fine if chatting within a Teams channel or if you pop-out the individual chat. You can right-click a chat that is occurring within the window showing all of the avatars during a live meeting, however if you navigate to the same chat within the Chat listings, the right-click does not work.
Upon troubleshooting, I found that the SETTINGS.JSON file is being changed after the initial closing of the client. The paths within the file are totally different with extra slashes than from the initial file. Not sure if this is causing the problem, however deleting the SETTINGS.JSON file and restarting the client will work for that session until of course you close it again, where the file is changed again upon closing.
Can someone at Microsoft look further into this? This seems like a bug that is now occurring in the last few releases. While there are workarounds, it is something that is causing issues with staff. I have been able to duplicate this on other clients as well. I am currently running Microsoft Teams Version 1.5.00.11163 (64-bit). We are also in the GCC if that helps so not sure if it is isolated to only GCC users.
Thank you!
Los
47 Replies
Looks like it's now been resolved!
I'm now on Version 1.6.00.26959 and all is well with the world.
If you're lurking, thanks dev team!
- Thanks for your post that we have it fixed in newer version now
I like to confirm it works also for 1.6.00.26909
And just one more comment on preview builds, shouldn't those preview build rely on latest production build base!
Looks like this time an issue which was already fixed/improved in production keeps active in preview version.
Let's assume it is fixed now in both latest production and preview builds.
Time to mark that thread as Solved with newer version. - What was fixed for you? I don't see that update yet
- My issue was the same as the OP; when I right clicked on a misspelled word I was not getting suggestions for the correct spellings unless I popped out the chat window. I'm now seeing the spellcheck suggestions in all areas of Teams without having to pop out the window.
I'm glad I found this thread, no one else in my org can reproduce the issue and I thought I was going crazy!
To highlight the consistent behavior other have mentioned:- I see the red line telling me a word is misspelled but when I right click nothing happens
- If I clear my Team's cache spellcheck works for a bit, then it stops working
- If I pop out a window spellcheck works fine, but this is not a convenient work around
I'm running Teams Version 1.6.00.26163 (64-bit), please fix this MSTlTUS You are running the latest PREVIEW build... if you dont want to have issues.. run the latest production build.
there are 4 builds of teams
1)Daily builds
2)Experimental Builds
3)Preview builds
4)Production buildsThe Production build is the only one that is supported!
Again if you are not happy with the preview build and the bugs it has.. don't run it!
the latest production ready build 1.6.00.24078
you can track the versions here:
MicrosoftTeams-msinternal/defconfig at master · ItzLevvie/MicrosoftTeams-msinternal · GitHub- This happens outside the preview builds as well. We see it on multiple users none of which are on any of the preview builds (And on mine its build 1.6.00.24078 as of today) and its been going on for years now. Some builds will fix it for a bit then it will come roaring its ulgy head back up. And to confirm this is also the regular version of Teams not "New Teams" which is even more broken with all its video issues.
This is super frustrating. I am close to reimaging my laptop and starting fresh.
I've uninstalled Office and Teams and reinstalled and the issue keeps coming back.
I renamed the Teams folder in \AppData\Roaming\Microsoft and it works for a few hours and the settings.json seems to keeps not allowing the right click autocorrect.
I don't mind the new Teams, but then I don't get the green microphone icon to show up when I am on a call. Only the regular Teams does it.
I just want Teams to work properly.
As you said using the "new" teams I am assuming (I know shouldn't assume but hey) you are using the preview version? (as you can only get to the non-proton "New version of Teams" if your running preview)
Like all preview version they wont acknowledge anything.. you can only report it.If this is the case then like I said above.. if you want it "to just work".. then don't run the preview or dev branch...
If you are being forced onto the preview then you need to talk to an admin in your organisation to change the Teams update policy in office 365 to stop forcing you onto preview version.Hope this helps and I have not assumed to much 😄
Yeah the new teams preview. It isn't pushed to us. I select that option. I only did because the right click spell check doesn't work on regular teams. I don't mind new teams, but then I get that other issue with the microphone icon. I want to do a full uninstall. I am wondering what other files I would need to do in order to fix this
- We are seeing in our environment too now.
trandall K-BASH Meg Magruder are your users that are experience this issue enrolled in Teams Public Preview
I noticed that I was only one in our business having issues and I could not find version 1.6.00.24815 official listed anywhere.. in fact the latest official release is "1.6.00.22378"
I reinstalled without public preview and that was the most up-to-date version.. problem solved
re-enabled public previews and it updated me to the problematic 1.6.00.24815
I think the resolution here is to disable public preview for your users and down grade them back to latest stable release "1.6.00.22378"Unfortunately there is no way to do this in Teams itself. and opting out of public preview just opts you out from FUTURE updates... it wont downgrade you back to standard release version..
To do this you will need to uninstall the current version of teams.. and re-install it.
depending on how that deployed in your environment this process will very.
for me I have to uninstall it from Apps and Features then delete my "Teams" folder in %appData%
I then have to run the latest "work or school" installer from the Teams website.Hope this helps
thanks for suggestion which sounds plausible, even that there is no Developer nor Public Preview listed for my account
anyway uninstall/cleanup/re-install, means downgrade to "work or school 1.6.00.22378" version gives same faulty result to me
it works fine for the very first start, but after closing and restarting teams issue is present again.
only workaround as delete settings.json before restart
the bad is even after hibernate the issue appears and user have to re-run the workaround
I don't see this solved - unfortunately I don't remember which version it was that worked without issue for the past two or three weeks
if account specific - any online account cache known that can be cleaned up?
- FYI - Just an updated. It seems Microsoft has pushed through a change. The feature is working again - at least for people where I work - both Windows and Mac OS!
- I can confirm it was working for some weeks (assume some Teams upgrade in Aug 2023)
Unfortunately it appears again now - I'm on 1.6.00.24815 (64-bit)-E in Windows11 (Teams was last updated on 9/7/2023)
even disable spell check/restart/enable spell check/restart Tipp is not working for me
bad or even alarming to see that such a nasty bug is living that long in a daily used MS program
- Me too, on a M1 Max Macbook Pro. Logoff and on fixes it for a day or two. I can not express how disruptive this is. I am a byproduct of the US-Florida school system, I cant not spell. This causes me to have to cut and paste just about every 20th word out of what I write to google and back into teams. Its having a real world cost on my output.
- You cant one of the tested workarounds (till MS addresses the issue),
- 'Pop-out' the chat window
The other workaround works as well,
- Delete 'settings.json' before launching MS Teams
- Location: ~/Library/Application\ Support/Microsoft/Teams/settings.json
This post has been very helpful. I am on MacBook. Also had a look at settings.json, located in '~/
/Library/Application Support/Microsoft/Teams' folder. We are using Microsoft Teams Version 1.6.00.19562. On deleting settings.json, Teams generates a new one that is 171K in size. When you open Teams again, this goes up to 188K in size.
cat settings.json | jq '.settings | keys'
[ "ConfigIds", "ETag", "baseSettings", "cloudEnvironment", "environment", "initializedSettings", "preauthSettings", "region", "ring", "settings", "settingsOverride", "version" ]cat settings.json | jq '.initializedSettings | keys' | wc -l
763
cat settings.json.working | jq '.initializedSettings | keys' | wc -l
459
One of the areas that is changing is the initializedSettings key.
Not got to the bottom of which setting is causing the issue, but seems looking at the JSON via jq can provide some interesting insights - for the technically oriented.
Yes and Now this issue started.
I deleted setting.json file then it work but after some time started same issue again
I just eresed all the content of teams in the path %appdata%\Microsoft\Teams.
Relaunched the app and it worked.
The personalisations where erased to but at least i got the spelling check available to select the suggestions.
Version 1.6.00.1381 (64 bits)- I had the same issue for the last 2-3 days.
To fix it I have:
- disabled spell check in settings
- restarted Teams
- enabled the spell check
- restarted Teams.
Version 1.6.00.4472 (64-bit). Last updated on 09/03/2023- This worked for me also! Thank you!
- MS now has a service health advisory out for this issue - TM390278.
Title: Users' right-click context menu isn't working as expected in the Microsoft Teams desktop client
User Impact: Users' right-click context menu isn't working as expected in the Microsoft Teams desktop client.
Current status: We've received reports from affected users that users' right click context menu isn't working as expected within the Microsoft Teams desktop client. Our analysis thus far indicates that a recent feature update may be responsible for impact. We're disabling this update in our test environment to validate that impact is remediated before proceeding with our broader revert plan. In parallel, we're gathering additional logs and data from users who can reproduce the issue so we can determine what exactly is occurring. We're also requesting that users attempt to access the context menu through the web app to see if the issue is isolated to the desktop client only, which should narrow our investigative path.
Scope of impact: This issue could potentially affect any user who's attempting to access the context menu within the Microsoft Teams desktop client.
Next update by: Friday, June 10, 2022, 1:00 PM (5:00 PM UTC)Thanks for the reply!
We are on GCC as well. I will say that the Teams Machine-Wide client is the culprit for us. If we remove the Machine-Wide client and reinstall the client from the Teams site, it will correct the issue. This is a workaround for now as we would like to continue using the Teams Machine-Wide client.
Can you share a direct link to this advisory? I'm having trouble locating it for whatever reason. Thanks!EDIT: Actually, nevermind. I didn't realize this was checked from our own portal. Thanks!
URL for 365 admins: "https://portal.office.com/adminportal/home?ref=/servicehealth"
StephenWM I appreciate the response. I did find out these features still work in the following chat options:
- Pop out chat
- Live call/meeting chat
- Team group chat
- Web version of Teams chat
I also found if you delete the settings. json file before you start TEAMS that it works as expected. If Teams is already started just quit Teams, delete the file and start Teams. Of course you will need to do this each time you log on. I hope this help others.
