(Keyboard) Code 19: Windows cannot start this hardware device because its configuration information (in the Registry) is incomplete or damaged. Solution

I deleted VMware directly without uninstalling it. After removing some residual services from VMware and restarting the system, the keyboard cannot be used. After you press the keyboard, the mouse does not move, causing the system to be suspended. If you do not move the keyboard, you can still use the mouse, turn off the system, re-plug in the keyboard, the boot failure is still, hot swapping does not help, the system is starting until the system enters the system, there is no hardware error prompt, think twice about it. At first, I thought the keyboard was broken. My dual system and the other system was Linux. When I went to Linux, the keyboard was usable, which proved that the keyboard was correct.

However, you can only use the mouse to find the fault. Open the Device Manager and you will see an exclamation point in the keyboard!

View Details:

Device Manager display: Code 19: Windows cannot start the hardware device because its configuration information (in the Registry) is incomplete or damaged.

Delete the device. After scanning for hardware updates, the system still prompts: Code 19: Windows cannot start the hardware device because its configuration information (in the Registry) is incomplete or damaged, it's really depressing.

Google to get a solution similar to the following:

Open regedit,

Go to HKEY_LOCAL_MACHINE/system/CurrentControlSet/control/class/{4d36e96b-e325-11ce-bfc1-08002be10318}

Delete upperfilters items

Uninstall the device and restart it.

In the Device Manager, code 10 fails to start the device.

Go to HKEY_LOCAL_MACHINE/system/CurrentControlSet/control/class/{4d36e96b-e325-11ce-bfc1-08002be10318}

Add the string upperfilters. The content is kbdclass.

Uninstall the device and restart it.

The actual application is easy to use and the problem is finally solved! In fact, similar situations occur, not only on the keyboard, but also on other peripherals, such as optical drives. However, the solution is roughly the same as this one.

Class/{detail} Here {4d36e96b-e325-11ce-bfc1-08002be10318} indicates the keyboard, which is also described in detail in the registry. There are many such characters in the class. When you open it, you will understand what it means.

PS: (this is what the problem solver said)
In fact, this problem should be caused by upperfilters. The content comes from the dxdiag program, the PS/2 device in the "input-related device" under the input tag, and the high-level screening program. The upperfilters value in the registry is the same as that in the high-level filtering program.

PS: Although there is a problem with the Device Manager, it is strange that the dxdiag program has not found any errors.