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.
The thing that sometimes triggers this problem (for me) is when i used the shortcut ^ (up arrow ) to initiate editing the last comment i entered. after editing, the cursor sometimes lock up and not move left and right
This is not a solution its just restarting the application.
Actually restarting causes a larger issue for many people. Specifically: https://techcommunity.microsoft.com/t5/microsoft-teams/user-stuck-in-a-boot-loop-crash-in-teams/m-p/1313046
&tldr; Many users have to reinstall teams after shutting it down.
The cause/fix for this other problem is also understood by the community.
December ends, and there's no fix. Maybe they are waiting until Christmas Eve - they will jump into your computer (via CPU fan), force it to say Ho, Ho, Ho.... and fix will be installed. Or maybe not Christmas, because now it's 'passe'. New year will be more 'neutral'. When the 00:00 will appear on the screen, computer will show the pop-up with fireworks and then fix will be installed...
The same problem here. The issue keeps coming back after working a bit when Team or computer is restarted.
What a useless response. And always the same response with you guys - ignore the actual issue and tell everyone to reboot. Rebooting your computer everyday because of a bug in Teams that MS refuses to acknowledge or fix is not a "solution".
If you don't have anything of value to add don't even bother responding.