Skip to main content

Dreaded Code 10 and 39 messages in Device Manager

You might have seen the dreaded error codes of 10 ("This device cannot start. (Code 10)") and 39 ("Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)") messages. The solution is elaborated really nicely here: http://hateadub.wordpress.com/2011/04/20/code-10-device-manager-keyboard-and-mouse-not-working/

In my case, the issue was with the mouse and the keyboard which made it extra infuriating since I needed to use the On-Screen Keyboard and Mouse Keys (true nightmare). In particular, the issue was with the "upper filters" in the bowels of the registry where you just needed to keep 1 value (HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Class\{4D36E96B-E325-11CE-BFC1-08002BE10318} mouclass and HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Class\{4D36E96B-E325-11CE-BFC1-08002BE10318} kbdclass)

Once I retire, I will get back and take a look at windows documentation, in particular, how the devices are represented in the registry. That is quite a dark world. Waste of an hour, but the joy you get when things are working again is priceless.

Comments

Popular posts from this blog

The feature you are trying to use is on a network resource that is unavailable

You see this:
The feature you are trying to use is on a network resource that is unavailable. This is happening because the cached installer is missing (in my case due to running a scan on folder sizes, seeing this particular windows folder with all the uninstallers (the cache) and removing them.)


Use this:
http://support.microsoft.com/mats/Program_Install_and_Uninstall
Uninstall the program that is causing trouble using the tool and voila.