Teams & cursor annoyance

[Mr Pointy]

I have a weird situation when typing into Teams chat: the cursor left & right keys don't work which makes it a right pain when I need to correct a spelling error. The Backspace & Delete keys work, just not cursor left & right. It's not just me as I've checked with a colleague & it happens for them as well (both on Windows PCs running Win 10). Other programs are fine, I can cursor away no problem.

Anyone else have this or managed to resolve the issue?

[xeny]

They work OK for me on two windows 10 machines.

Do you and your colleague have any odd software in common? Is the problem also present in the web version?

[Bollah]

Mr Pointy said:

I have a weird situation when typing into Teams chat: the cursor left & right keys don't work which makes it a right pain when I need to correct a spelling error. The Backspace & Delete keys work, just not cursor left & right. It's not just me as I've checked with a colleague & it happens for them as well (both on Windows PCs running Win 10). Other programs are fine, I can cursor away no problem.

Anyone else have this or managed to resolve the issue?

I had it as well a while back and as you say it was a pain, but it seems to have resolved itself without any intervention from me. Only thing that I think might have fixed it is an update to Teams, as my organisation like to keep on top of Teams updates.

[Red9zero]

Apologies for thread hijacking, but has anyone found a method of altering the time it takes to switch you to idle ? I work between two laptops and the one with Teams seems very keen to update me as Idle and then very slow to put me back to Busy. I have checked, but I can't see anything, unless my company have locked it.

[Mr Pointy]

xeny said:

They work OK for me on two windows 10 machines.

Do you and your colleague have any odd software in common? Is the problem also present in the web version?

I shut down all other programs & was still having problems so I told Teams to look for updates & finally re-booted my PC - usually I just put it into sleep it at night. It's back working fine now so something's got reset in the process.

I should have just turned it off & on again in the first place.