Windows 10: At-sign/single-quote key becomes almost dead will only produce repeated outputs when...

I've been using an external US keyboard with my HP laptop running Windows 10 21H1 for some time. The laptop itself has a UK layout. I recently bought a UK layout keyboard and decided to switch over. The at-sign/single-quote key @/' works fine when US keyboard layout is selected, although it actually produces double- and single-quote "/'. However, when I switch to UK keyboard layout, the key doesn't respond to single presses, but will produce a string of at-signs or single-quotes if held down.Switching back to the US layout reverts to the key working normally again - single touch produces

:)

 

Problems with dead keys on MKLC

Hello,

I’m using the Keyboard Layout Creator 1.4 to create custom keyboard layouts that fit my typographic requirements. For the field that I study I need a lot of characters that aren’t available on the windows keyboard. I use dead keys to exploit a wider range
of characters, but some of theese don't work out the way I want. For example, I have a key with the label ‘9’ that produces small capital letters like ᴀ, ʙ, ᴄ…. In an earlyer version the label was simply ‘ᴀ’, but every time I pressed the key the output would
be ‘ᴀᴀ’, it was practically not a dead key but a zombie key.

Currently I’m rebuilding the greek polytonic keyboard, because I don’t like where the special characters are located in the original layout. Now the same problem occurs with nearly every diacritical mark.

When I press the keay for

• ´ (oxia, U+1ffd)
• ᾿ (psili, U+1fbf)

and so on, nothing happens but windows making a light tone. There a two exceptions:

1. ῏ (psili and perispomeni, U+1fcf) behaves like the small caps, which means the output is ‘῏῏’
2. ΄ (tonos, U+0384), ͺ (iota subscript, U+037a), ̄ (macron, U+00af) and ̆ (breve, U+02d8) behave normally.

Are there special constraints to the dead keys that I’m not aware of? I have no idea why for example ῏ (psili and perispomeni, U+1fcf) ῟ (dasia and preispomeni, U+1fdf) would behave differently.

Thanks in advance

[Moved from: Windows 10 / Install & upgrade]

 

MSI 5870 BIOS Update

Still can't reproduce. Could you please post the exact BIOSes that produce the issue?

 

Shift key produces wrong character and same with new keyboard

Shift key produces wrong character and same with new keyboard. Pound sign lost, Shift and @ or " produces the opposite