Conversations involving multiple participants, allowing collaboration and information sharing in Teams
be sure to try the 'click on the three dots (more options) menu, then use ESC to back out of it' workaround!
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
ft and right arrow keys have no effect in TEAMS BUT left-arrow + CTRL moves left one word, and right-arrow + CTRL moves right one word. So it is clear the arrow keys on the keyboard are functioning and sending signals to the computer. I also tried my laptop built in keyboard & the number pad. All have the same effect. What could be making the arrows by themselves not work? (Up and Down arrows work normally.)
1. Is it a laptop or desktop computer?
Laptop
2. What is the make and model of the keyboard?
HP laptop keyboard & logitech external
3. Was it working fine earlier?
Yes at most an hour before
4. Were there any recent changes made on the computer prior to the issue?
No. Maybe I inadvertently hit some hot key?
Conversations involving multiple participants, allowing collaboration and information sharing in Teams
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.
be sure to try the 'click on the three dots (more options) menu, then use ESC to back out of it' workaround!
Selecting the Team's react 3 dots to a comment and escape worked for me however, not sure for how long it will last as I have tried most of the options suggested and each works for a short time.
I have the issue on 2 separate PCs and was able to test the react 3dots then escape on one of them today,
I have noticed - as have others - that when holding down Shift + left or right the cursor moves as well as Control + left or right.
Left or right on their own did not. they work for all other applications.
Same issue here. Arrow keys non responsive out of the blue. The problem resolves easily by quitting Teams and re-starting it. But why does it have to happen in the first place. True nuisance.
I mean... I appreciate your post as trying to help, but it's stupidity squared if you have a community forum where people post issues and you then put on blinders and sing "la la la", while insisting you'll only look at some other channel for bug reports. Particularly when that other "channel" appears as a black hole for users to throw in their issues and never hear back.
That would be great news, if I had not already followed the in-Teams feedback route multiple times over the past year+. When it's all -some day- realistically assessed by MS, they will find- like the real world has- that the fantasy of throwing all content into webs of funky and ephemeral links just does NOT work. Certainly, not anywhere near as effectively as direct content transfers. The proliferation of sharepoint, url, teams-specific complaints across umpteen+ 'support communities' and crowd-sourced volunteers is a failure worsening by the day. Today it is left and right arrow fails. Tomorrow it will be self-driving off of piers.