Conversations involving multiple participants, allowing collaboration and information sharing in Teams
I had the same issue in my MAC M1 with wireless keyboard (plugged in). Command + K works for me too, weird stuff
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.
I had the same issue in my MAC M1 with wireless keyboard (plugged in). Command + K works for me too, weird stuff
I'm on that same version.
You have Microsoft Teams Version 1.5.00.11163 (64-bit). It was last updated on 5/10/2022.
Left and right arrows still don't work. I haven't rebooted yet.
Still same issue here. Unfortunately not reproducable, but really annyoing.
I have this issue often.
I think it is happening due to "FFSKSW (Fat Finger Small Key Syndrome) where I am pressing a combination of buttons, like Alt + something, but i have yet to figure out what that combo is.
Best solution I have seen on here so far is the Right click and quit method, which is certainly better than the full nuclear reboot or deleting every iota of background data that seems to have been suggested elsewhere in this thread!
If I have missed the actual solution (no shutting down anything type one) please let me know
Agreed. All the solutions work temporarily in any case - I am not sure what I am doing that triggers the issue, but I only need to type a few characters before if recurs.