Conversations involving multiple participants, allowing collaboration and information sharing in Teams
I've had this problem for a few months now. Super annoying as I have to kill/restart multiple times per day. Microsoft please fix!
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've had this problem for a few months now. Super annoying as I have to kill/restart multiple times per day. Microsoft please fix!
Right click on Teams Icon and select "X Quit" and that fixed it next time you open up
This is not a solution its just restarting the application. Stop suggesting that you need to restart a messaging application to make the user input work properly. restarting the application MAY re-enable the functionality but the issue needs to be resolved
Thank you Hummelmose, that is wonderful, and has fixed the problem! I'm not bothered why, as it is most likely an accidental key press (probably alt and something) but at least I now know how to fix it.
As I already wrote earlier, it's most probably print screen key and disabling it fixes the issue. It never happened to me again, after disabling print screen.