D
D_Valentim
Hi all,
I have just come out of a 2 hours session with a remoted Microsoft tech trying to sort this issue. Essentially:
-@ and ' key do not work by only tapping, it only works when held down (like if Filter Keys is turned on) and once it appears, it has already spammed 3-4 characters;
-This occurs only on UK and UK extended keyboard, using the same key on any other keyboard language will work as usual but with a different character;
-Even after replacing the keyboard 3 different times from 2 different manufacturers, the same issue still occurred;
-When using the On Screen Keyboard, the same issue still happens, pretty much confirming this is a language keyboard issue. Not physical (despite how much the tech over the remote tried to insist);
Here is what was tried so far:
-Disabled everything on the Ease of Access > Keyboard options to make sure no keys were being messed with (even though every single other key is working fine);
-Removed UK keyboard lang and replaced it with something else, then brought UK back. Still having issue;
-Reinstalled all keyboard drivers. Still issue;
-Ran W10 some for of repair from a w10 iso (this was done by the tech, at this point I was making some coffee due to the boredom that I was not paying much attention at what was being done). Still have issues;
-Ran sfc scannow, found no integrity violations;
-Tried last used physical keyboard again just to be sure I was not going crazy, still had the same issue;
-Downloaded PassMark KeyboardTest and had a look, it does not recognise the key is being pressed unless it is held. When the kb language was changed to USA international when pressing the @ and ' key it selected the # and ~ key as the output;
In short it seems the keyboard language simply does not recognise that key unless it is being held.
I am going nuts at this point due to it being something so simple. And I can see someone else had the same problem a while back Windows 10 UK keyboard. @ only works when key pressed hard then I get @@@@@@@@! but found no conclusion.
Please advise.
Continue reading...
I have just come out of a 2 hours session with a remoted Microsoft tech trying to sort this issue. Essentially:
-@ and ' key do not work by only tapping, it only works when held down (like if Filter Keys is turned on) and once it appears, it has already spammed 3-4 characters;
-This occurs only on UK and UK extended keyboard, using the same key on any other keyboard language will work as usual but with a different character;
-Even after replacing the keyboard 3 different times from 2 different manufacturers, the same issue still occurred;
-When using the On Screen Keyboard, the same issue still happens, pretty much confirming this is a language keyboard issue. Not physical (despite how much the tech over the remote tried to insist);
Here is what was tried so far:
-Disabled everything on the Ease of Access > Keyboard options to make sure no keys were being messed with (even though every single other key is working fine);
-Removed UK keyboard lang and replaced it with something else, then brought UK back. Still having issue;
-Reinstalled all keyboard drivers. Still issue;
-Ran W10 some for of repair from a w10 iso (this was done by the tech, at this point I was making some coffee due to the boredom that I was not paying much attention at what was being done). Still have issues;
-Ran sfc scannow, found no integrity violations;
-Tried last used physical keyboard again just to be sure I was not going crazy, still had the same issue;
-Downloaded PassMark KeyboardTest and had a look, it does not recognise the key is being pressed unless it is held. When the kb language was changed to USA international when pressing the @ and ' key it selected the # and ~ key as the output;
In short it seems the keyboard language simply does not recognise that key unless it is being held.
I am going nuts at this point due to it being something so simple. And I can see someone else had the same problem a while back Windows 10 UK keyboard. @ only works when key pressed hard then I get @@@@@@@@! but found no conclusion.
Please advise.
Continue reading...