Hello, Jay Eversman
Welcome to the Microsoft Community.
Thank you very much for your feedback. I have carefully read the information and problem description you provided. You mentioned that after updating to 24H2, your computer no longer works when connected to the keyboard.
I understand the trouble this problem causes you. I noticed that you have tried many methods, but the problem still persists, which is indeed frustrating.
I noticed that you have tried three ways to connect the keyboard and tried to reinstall Windows, but the keyboard still does not work. This may mean that you need to restore the system or uninstall the update to fix the problem. This may be a compatibility issue with the latest system version.
I suggest you try the following method to perform the above operations.
After three consecutive forced restarts (holding down the power button until the computer shuts down during Windows startup), the system will automatically enter WinRE.
After entering WinRE, you will see a selection screen.
Select the Troubleshoot option.
In the Troubleshoot interface, select Advanced options.
In Advanced options, select System Restore. This will start the system restore function.
The system restore tool will display the available restore points. Select a restore point with a date before the problem occurred.
Click Next and follow the prompts to complete the restore process.
At the same time, you can also try to uninstall the update to test whether the black screen problem still exists. The steps are as follows.
In Advanced Options, select Uninstall Updates.
You will see two options: Uninstall the latest quality update and Uninstall the latest feature update.
If you choose Uninstall the latest quality update, the system will roll back to the state before the last quality update was installed.
If you choose Uninstall the latest feature update, the system will roll back to the version before the feature update.
Best regards
Brian - Microsoft Community Support Specialist
Hello Brian,
I don't believe that anything from the users can help, as the problem is clearly due to a BUG in Win11 24H2 !
I use an old Microsoft Internet Keyboard (Standard PS/2 keyboard) connected with USB using Microsoft driver 10.0.26100.1882.
No problem since about 20 years in Windows 7/8/8.1/10/11, neither with standard keyboard layouts (DE-CH, FR-CH) nor with my own keyboard layout based on DE-CH with multiple additional symbols (Microsoft Keyboard Layout Creator Version 1.4).
Since Win11Pro×64 24H2, the first two standard keyboards still work, but the latter produces garbage when entering textboxes with the mouse, especially in the browser (Firefox) or in Microsoft Office 2019 Pro (Access). Garbage means that additional special characters appear when I type a first character into the textbox.
For example, after creating a new empty record in an Access form (only with mouse clicks and vba), the cursor being in the first textbox by default:
- when I type 'a' , I get 'Гa' (U+0413 U+00E1); Г is coded by typing [
- when I type 'v' , I get '↕' (U+2195); ↕ is coded by typing [
- and so on… (my modified keyboard layout uses
This suggests that at this point, the keyboard buffer contains some data (likely
Private Sub NewRecord_Click()
DoCmd.GoToRecord , , A_NEWREC
SendKeys "{BACKSPACE}"
End Sub
After the additional command SendKeys, I get correctly 'a' or 'v'.
This proves that the keyboard buffer is indeed not empty. Mouse clicks obviously affect the keyboard buffer.
Independently from what happens or not upon typing the first character, the next ones always follow normally.
Just in case this could help, please note that for my particular keyboard layout, GetKeyboardLayoutList returns the negative pointer value '-255850489' (Hex value FFFFFFFFF0C00807).
This makes it impossible to switch keyboard layout programatically as usual according to their Hex value; instead, I have to use the pointers themselves (what works perfectly for both positive and negative pointers):
Function Tastatur() As LongPtr
Tastatur = GetKeyboardLayout(ByVal 0&)
End Function
…
Call ActivateKeyboardLayout(Tastatur, True) ' e.g. Tastatur = -255850489
I suspect that the keyboard buffer is likely insufficiently protected in 24H2 – or maybe just not large enough for all keyboards. If you have any means to contact Microsoft, please forward this info to them.
Best regards, Henri
Please note that the keyboard bug is not related to the latest Office version: I use an Office version elder than Win11 24H2 because of the latest Office version's crazy bug that Form_MouseWheel() always returns 0. The keyboard bug also happens not only in Access but in the browser, too.