Conversations involving multiple participants, allowing collaboration and information sharing in Teams
HA! I have to try that one next time this happens lol!
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.
HA! I have to try that one next time this happens lol!
That is a hell of a lot of steps to keep my arrow keys working in teams. Perhaps I'd be willing to press a button to fix it instead.
As it is good to know how to kill an app. Would it be better not to have problem with arrow keys in first place?
Issue occurred few times on my teams and it is quite disturbing to workflow.
I'm still experiencing the same issue where the left and right arrow keys stop working in a Teams chat on 9/26/2021. Strange that they work in all other applications, and the Ctrl + right or left arrow still works where they skip a word rather than just a character. The only work-a-round is to restart Teams, by right-clicking on the icon in the taskbar and selecting Quit. I hope that someone from Microsoft support is monitoring this thread and they share a fix that resolves the bug.