Skip to content

Work around for KB938371 disabling HID-compliant input devices

After a few days of non-working mice, someone found a work around for KB938371. As I noted here and here, Vista Update 938371 disabled two the three mice I have I on my main home machine. Here’s the work around that actually worked for me:

  • Just go to device manager -> HID-devices -> Unknown Device and search for drivers.
  • When prompted for how to search for driver software, select “Browse my computer for driver software”
  • Enter “C:\windows\winsxs” for the driver location and press the “Next” button.
  • If you get a popup saying “this is an unsigned driver…”, just allow Windows to install the driver.

At this point, Windows should select the appropriate driver and your mouse will start working again.  When I tried this, only had one of the non-working mice plugged in.  When I followed those steps, the mouse started working.  I plugged the other mouse in and Windows enabled it without any prompting.

I went in to Device Manage and both mice were listed as “HID-compliant mouse” under “Mice and other pointing devices”.  Just to be safe, I selected one the mice, right-clicked into “Properties, selected the “Driver” tab on the dialog that opened up.  I clicked the “Driver Details” button and the mouse was using mouclass.sys and mouhid.sys drivers, located in c:\windows\system32\drivers, which is what they were supposed to be using.

This tip was originally posted here and I came across it here.  I’m happy that I have my mouse functionality back, but how did this get past Microsoft’s testing?  I saw too many people reporting this, it’s not an isolated case.  I have a mouse that comes with my Wacom table that wasn’t affected by this snafu, but what about the people who just had regular USB mice?  They were/are pretty much screwed by an update that can’t be uninstalled with running System Restore. 

I still want to know what happened and why 938371 toasted my HID-compliant hardware.  Was there something broken already with my Vista installation and 938371 was just a symptom of the problem, or did 938371 actually break something?

I’m not allowing MS to automatically update my PC anymore.  That requires a certain level of trust that MS is going to push down updates that will be beneficial.  They just blew that trust.  I’ll take the updates, but I’m going to decide if and when they get installed.

I was asked offline why I have three mice.  It’s pretty simple (almost makes sense).  My day to day mouse is a Logitech MX™700.  It’s a cordless mouse that uses rechargeable batteries.  It’s been the best mouse that I have ever used and I continue to use it under Vista even though Logitech never ported the MX700 drivers to Vista.  It has a little dock that charges the batteries.  I almost always forget to put the mouse back in it’s dock and a every few days, the batteries give out.  When that happens, I place it back in it’s dock and use a Dell USB optical mouse while the MX700 is charging.   The third mouse is a digitizer mouse that comes with my Wacom Bamboo Fun tablet.  That mouse works, but only on it’s little pad.  It was OK enough to use while tracking down this problem, but I wouldn’t want it to be my everyday mouse.

Update: 2/22/2010
I repaved this machine with Windows 7 about 6 months ago and replaced the MX700 with a Logitech mouse that is supported under Windows 7.  For anyone that is still having this problem, consider Windows 7.  It’s much nicer than Vista.