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.
This is truly annoying!
"Restart your computer", really Microsoft?!?!
Is there not any REAL solution to this issue?
This issue has been ongoing for almost a year! My left and right arrow keys almost never work in the teams chat editor, so I have just given up trying to use them. Extremely annoying!
I have the same issue on a Dell Windows 10 notebook. It happens from time to time. I need to restart Microsoft Teams to make this Problem go away. Very annoying.
I have the same issue, it is very annoying.
This has to be the silliest workaround in the history of workarounds, but it WORKS!! :)