Conversations involving multiple participants, allowing collaboration and information sharing in Teams
I too have this issue on my work and home pc
i seemed to find a workaround by disabling GPU acceleration in the Teams settings
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.
Can Microsoft just fix the issue instead of repeating your Windows-95 era "Just restart your <<something>>" mantra?
Teams was obviously a rush job, but guys, we're 18 months into this pandemic now! If you haven't gotten your act together, maybe just admit that you don't know what you're doing and work on integration of Office365 with Zoom / Meet instead?
Open source, then we can fix it for you.
Good tip.
Holding Ctrl also works to move word by word. Backspace also works.
That combination works as a temporary measure to move cursor and correct text, at least for me.
But this is very annoying when this happens.
MS, pls fix this quick.
I am plagued by this issue as well. Restarting the application is an unacceptable solution, just a clunky workaround.
Where has the Microsoft Team acknowledged the bug, and when can we expect a proper fix?