This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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 solved this by clicking the 3 dots (top right) and clicked on "Check for updates" - Teams did the update, closed and opened itself and the issue was fixed.
i found a solution on page 20, should sort it without having to exit the program
Yes, this does work.
So a strange bug with similar strange way to resolve it.
I've been experiencing the same issue, but in Mac OS. It only happens in chat, and not while on calls or in the search field.
This indeed seems to be a bug in Teams. However, this is a problematic bug because there doesn’t seem to be a consistent way to reproduce the problem. And without a consistent reproduction any fix will be experimental. Logging is also very limited around this area for privacy reasons.
It would be very helpful if anyone could remember and describe how they got into this state where left and right keys stopped responding.
There are ideas in this thread about GPU acceleration, print screen key, function key, accessibility keys, switching between editing and composing messages etc, but none can consistently reproduce the problem. The search continues.