Share via

After the April updates, my keyboard is not working. Special characters not displaying properly.

Anonymous
2023-04-12T09:02:55+00:00

Prior to installing the Microsoft April updates, (Cumulative Update for Windows 10 version 21H2 for x64 based systems KB5025221) and (.NET 6.0.16 Security Update for x64 Client) KB5025915 my keyboard was working properly. Now some of the upper-case characters in the number row are displaying the wrong character.

I.e.

  • the uppercase 2 displays the double quote instead of the @ (I found the @ sign where the double quote sign should be.
  • The uppercase 3 displays £, (the symbol for the British pound) instead of the pound sign. I have no idea where the pound sign is. Probably had to get it from the special characters.

I am using a Microsoft wired keyboard. I exchanged the keyboard with a Logitech wireless keyboard, and it does the same thing.

Any suggestions will be greatly appreciated.

Thank you,

Bob

Windows for home | Windows 10 | Devices and drivers

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.

0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-04-12T09:14:21+00:00

    I resolved this problem. Evidently the setting for the default language was changed from US English to United Kingdom English by one of today’s updates. Overriding the default language fixed it.

    Bob

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2023-04-20T05:24:07+00:00

    Thanks for your comments I remember several years ago when it was a regular happening that MS updates caused problems. It got to the point that I delayed installing them for several weeks until I heard from other tech sources that the updates were clean or how to work around them. Or at times when not to install an update until MS fixed it. Thought those days were over. Thanks for your comments, Jack.

    I remember decades ago before multi-processing and disc drives were even thought of and limited memory; some systems ran on only 4k of core memory. I know, unbelievable, but true. The only input to these ancient systems was a card reader, tape drives, and the manual control panel mounted on one of the cabinets; yes, even prior to keyboards. The only output was a card punch, a printer, and again, the tape drives. Most programs had to be loaded by a card deck. Some programmers got smart and figured out how to input programs with the tape drives. Even with that the files were basically images of the card decks. Also, programming languages like COBOL and FORTRAN didn't exist. The programming was done in machine language, you know, almost ones and zeroes. I'm talking about many decades ago, like in the 1960s when I first started as a computer service tech.

    When a program stopped working, the first thing to blame was the hardware. More often than not that was true. But many times, after talking to the programmer he said all he did was make a few simple changes. A common problem was that the card deck would get out or order, or a new card was inserted into the wrong place. When each card was a single command, you can see how that would screw things up.

    Anyway, now things are a lot different, but with all the new technology, the old problems still abound, only with more technological causes.

    Bob

    Was this answer helpful?

    0 comments
  3. Anonymous
    2023-04-19T19:01:39+00:00

    This update caused issues with my brand-new Dell Inspiron laptop:

    1. Turned off the backlight on the keyboard via BIOS. I had to restart/F2 into the BIOS in order to turn it back on.
    2. Screwed up my audio settings and I only found out because I could not function in my Teams meeting with no speakers or microphone. After a lot of troubleshooting and restarts, the audio is back to normal now. But I'm not entirely sure what it was. Device manager events tab said my audio driver did not start on last reboot. But whatever I did between multiple restarts got everything back to what it was.

    I am going to start creating a restore point once per week so I can recover from these senseless issues I encounter from Windows Update.

    Was this answer helpful?

    0 comments