none
USB mouse fails after installing XP SP3

    질문

  • I have an older Kensingtom mouse model 72121.  It was working fine until I installed Service Pack3.  Now the computer won't even see it.  I have scaaned for hardware, and reinstalled Kensington's drivers. 
    Kensington tech support said the mouse was not compatible with Service Pack 3.  So how many other USB devices are going to fail with Service Pack 3?
    I am responsible for over 120 computers not to mention servers.  I am looking into what does and does not work with SP3.  Does anyone have a list put together or is it all hit and miss?
    2008년 8월 14일 목요일 오후 9:51

답변

  • Did you download and install the correct drivers?


    If the issue still occurs, you can disable all startup items and third party services when booting. This method will help us determine if this issue is caused by a loading program or service. Please perform the following steps:

    1. Click the Start Button type "msconfig" (without quotation marks) in the Start Search box, and then press Enter.

    Note: If prompted, please click Continue on the User Account Control (UAC) window.
     
    2. Click the "Services" tab, check the "Hide All Microsoft Services" box and click "Disable All" (if it is not gray).
    3. Click the "Startup" tab, click "Disable All" and click "OK".

    Then, restart the computer. When the "System Configuration Utility" window appears, please check the "Don't show this message or launch the System Configuration Utility when Windows starts" box and click OK.

    Please test this issue in the Clean Boot environment, if the issue disappears in the Clean Boot environment, we can use a 50/50 approach to quickly narrow down which entry is causing the issue.

    The issue can also be caused by the ACPI of your BIOS. If the issue still occurs in Clean Boot Mode, I suggest you upgrade the BIOS.

    If the above suggestions do not help, I suggest you contact the technical support for Microsoft Hardware.

    Microsoft Help and Support - Hardware

     

    2010년 7월 14일 수요일 오후 9:59

모든 응답

  • Various people have reported problems with both USB and firewire devices but they seem to be in an unlucky minority.  Shortly after SP3 was released I read about problems with certain older wireless adaptors but they never seem to crop up on this forum. 

     

    I find it very hard to believe that a USB mouse could be incompatible with SP3.  If it is true then AFAIK it is the first USB device (other than a wireless adaptor) to be positively identified as incompatible.  I'm sticking my neck out a bit here but others can shoot me down in flames if I am wrong.

     

    2008년 8월 14일 목요일 오후 10:15
  • We are getting the same issue here with some Dell USB mouse. Out of 300 or so PC's that we released SP3 on for a trial we have about 3 that the mouse have failed on. Have no idea why at the moment.

    2008년 8월 18일 월요일 오전 12:31
  •  philip127 wrote:
    I have an older Kensingtom mouse model 72121.  It was working fine until I installed Service Pack3.  Now the computer won't even see it.  I have scaaned for hardware, and reinstalled Kensington's drivers. 
    Kensington tech support said the mouse was not compatible with Service Pack 3.  So how many other USB devices are going to fail with Service Pack 3?
    I am responsible for over 120 computers not to mention servers.  I am looking into what does and does not work with SP3.  Does anyone have a list put together or is it all hit and miss?

    It's been well documented around here that SP3 has problems with some USB devices (and FireWire) on some PC's (http://forums.microsoft.com/technet/showpost.aspx?postid=3321844&siteid=17&pageid=33).  Generally this was USB mice, but it also occasionally affected other USB devices.  No one, not even MS has been able to determine why this affects some but not others.  Just be thankful your PC boots, many were getting the BSOD/reboot loop issue with USB mice attached.  Their PC's were generally useless until they removed the mouse or used a PS/2 mouse.  Yet SP3 still remains available for download.  The strange thing is, some were able to use their PC's after connecting various USB devices.

     

    Your options are to remove SP3, try a PS/2 mouse, or try a PS/2 adapter on the mouse.

    2008년 8월 18일 월요일 오전 3:36
  •  

    Most likely Kensington support meant that its mouse drivers and/or software are not compatible with SP3, which is really not all that unusual.  I haven't installed mouse software in over five years now for this reason (out-dated or buggy).  Most settings are configurable through the default MS drivers and mouse properties, anyway.

     

    Roll-back to SP2, uninstall the Kensington drivers and software, make sure the mouse is using the default MS drivers, check for any out-standing updates by going to Windows Update website in your browser, then try installing SP3 again.

    2008년 8월 18일 월요일 오후 4:03
  • On our PC's on SP3 the mouse is using the Microsoft drivers hidclass.sys, hidparse.sys, hidusb.sys and hid.dll under Human Interface Devices in device manager. There is no "Mice and other pointing devices"  section and I cannot seem to get it to use moucalss.sys and mouhid.sys even if I point it to msmouse.inf, even though the device ID for the mouse is listed in this file.

     

    What is a little stranger if I reimage the PC with the mouse plugged in, SP3 is applied overnight via WSUS, the mouse will than work (using mouclass and mouhid.sys under "Mice and other pointing devices") but only in the port that it was plugged into. It will not reinstall on any new port.

    2008년 8월 19일 화요일 오전 12:02
  •  MVanZee wrote:

    On our PC's on SP3 the mouse is using the Microsoft drivers hidclass.sys, hidparse.sys, hidusb.sys and hid.dll under Human Interface Devices in device manager. There is no "Mice and other pointing devices" section and I cannot seem to get it to use moucalss.sys and mouhid.sys even if I point it to msmouse.inf, even though the device ID for the mouse is listed in this file.

     

    What is a little stranger if I reimage the PC with the mouse plugged in, SP3 is applied overnight via WSUS, the mouse will than work (using mouclass and mouhid.sys under "Mice and other pointing devices") but only in the port that it was plugged into. It will not reinstall on any new port.

     

    (In addition to some Logitech drivers), I'm showing mouclass.sys as one of the drivers on this PC.  It's a USB but using a PS/2 adapter.  Your "anomalies" could be due to the "issues" SP3 has with USB devices.  Sometimes XP sees USB devices as HID devices, this may be more so with SP3.  If it's causing you any problems, trying using a PS/2 adapter.

    2008년 8월 19일 화요일 오전 11:37
  • It's been a while since I posted this, but the knowledgeable techs at Microsoft have provided me with a solution that worked for us at any rate.

     

    1. Open %windir%\inf folder.
    2. Backup and delete these files:

    - INFCache.1
    - msmouse.pnf
    - input.pnf

    3.       Open a command line and run
    Net stop Cryptsvc
    4.       Backup and delete this folder “%windir%\system32\catroot2”
    5.       Reboot the computer to make sure the information was clean up.
    6.       Insert USB mouse to another port which hasn’t been used before.

    7.       Uninstall all HID devices than "Scan for new hardware"

     

    2008년 9월 24일 수요일 오전 3:42
  • MVanZee, very interesting!  I wonder how many others who have peripherals not being recognised after SP3 would benefit from similar procedures (not identical procedures - the .pnf deletions would have to be different)?

     

    2008년 9월 24일 수요일 오전 10:23
  •  

    My experience at home has been that I have too many USB connections to the machine - SP3 is able to handle it, but the mobo itself doesn't seem to be able to.

    I had issues with my mouse or keyboard when I had too many USB devices plugged in, it was resolved by removing un-needed devices.

    2008년 9월 24일 수요일 오후 5:27
  • Evening all

      people reporting the problem installs mainly seem to have the following in common

     

    using windows installer 3.0, and windows installer 3.1

    Microsoft has admitted problems with these installers. And issued hot fixes for this installers before installing Sp3.

    another portion of the problem seems to be the latest WSH sometimes replaces some files.

    Of course people by now know that Sp3 leaves .net 1.1 sp1 in a weird state. regardless of which version is used.

    Sp3 uses 3.1 v2.

     

    And other internet reports indicate that more reliable installs can be had using the ISO image of Sp3. Usually includes the latest security releases. I have not looked into the ISO yet

     

    . But at least can reasonably assume there is something fixed inside WI 3.1V2. Not only does this eliminate the older Installer issues. But instead of being inside the UAC account, at least program associations, and settings are preserved. But avoids the recognition problems of USB. USB has its own stack, not unlike TCP/IP. And using the seperate image and the proper WI seems to reduce the usb recognition problem.

    And also stopping the anti-virus programs from interfering with Sp3 installs, and of course the dreaded lack of SATA drivers. Reducing the environmental problems.

     

    So a solution is to install WU 4.5 before Sp3. or at least searching Microsoft for these hot fixes to WI 3.0, 3.1.

     

      Microsoft recommendation of WU 4.5 of course has its own issues, Certain older SATA drivers do not install properly with out rebooting. But seems to recognize certain raid 0 issues. Rollback of drivers in my testing seems to respond properly, and works out better then past roll backs; 3.0, 3.1

      Seems WI4.5 has its own slightly more rigid enforcement of unsigned drivers. Prepping people for Vistas UAC image. Partly to get people used to UAC. And to reduce the support requirements for Sp3. If you are not using a WHQL signed driver then its definately not Microsofts problem.

     

     Inside  Fireware we have the associations of wnaspi, storage management and a few other things. Time to get the debugger out. Where is WinFS when you need it?

     

     and of course a properly prepaired image can also take advantage of preactivation. Of course leaving you to do the research on this. 

     

    Hopefully this helps out some people out there.

    Keith

    2008년 9월 26일 금요일 오전 12:28
  • BINGO!  This (Almost) Worked!  Other steps that "helped" - I updated to latest Windows Installer as noted in a later post on this thread - that helped a little with some devices - seemed to make the storage class of devices work better, and CardScan Pro seemed to work after that - also the Belkin 7-port HUB no longer seemed to be a problem (before this it was an "unknown device" despite needing no drivers).  Second, I re-installed Active Sync latest version and it (thankfully) reported "Updating USB Drivers" - and then my ATT Kaiser/Tilt was able to connect...  However nothing seemed to allow Logitech Nano or MX Revolution drivers to complete installation - they seemed to hang while attempting to install the windows user mode driver framework or kernel mode driver framework leaving a log file at C:\windows\wdf01005Inst.log with an error message in it and a temp directory in C: with update files in it.

     

    I then read MVanZee's post and it looked like a good bet - so I deleted all the PNF's for fun since they get recreated as needed, and deleted INFCache.1, stopped the crypto service and deleted Catroot2 - rebooted a bit later - and when I inserted the mouse "receiver" I got further in the installation - beyond prior attempts  - Logitechs driver began prompting for a missing file from the Logitech CD - so I stopped that install, and re-ran the SETPOINT 4.6 installer (logitech doesn't seem to be able to install any other way for most of their devices), and after a reboot I tried the receiver once more, and it simply reported "Logitech USB HID Device Found" in the taskbar of WindowsXP - and the wireless mouse worked worked !!  So I swapped the Revolution device for the Nano device in the same port and it worked fine - didn't even report a "new device found" - just silently worked as advertisedWink

     

    Thank You MVanZee  - thanks also to the person who pointed me to the latest windows installer.

     

    After the above success, I decided to test things further so I plugged in an MP3 device and it did not complete installation as a storage device, then I tried a logitech camera and it ALSO did not install - both seemed to hang with "Windows Service Pack Installer" running (update.exe) from the temp directory created in the C: directory.    Here's the (repeated) error in the log file:

    0.031: ================================================================================
    0.031: 2008/10/07 11:30:33.906 (local)
    0.031: c:\fb74e1e59d13c118d09a77f6\update\update.exe (version 6.3.4.0)
    0.031: Hotfix started with following command line: /quiet
    0.031: In Function GetBuildType, line 1170, RegQueryValueEx failed with error 0x2
    0.031:  C:\WINDOWS\system32\DRIVERS\wdf01000.sys is Present
    0.031: FileVersion of C:\WINDOWS\system32\DRIVERS\wdf01000.sys is Greater Than 1.5.5600.0
    0.031: Condition Check for Line 1 of PreRequisite returned FALSE
    0.031: ReadStringFromInf: UpdSpGetLineText failed: 0xe0000102
    0.031: Wdf01005 Setup encountered an error:  Setup cannot continue because one or more prerequisites required to install Wdf01005 failed. For More details check the Log File c:\windows\Wdf01005Inst.log
    0.031: ReadStringFromInf: UpdSpGetLineText failed: 0xe0000102
    0.031: Setup cannot continue because one or more prerequisites required to install Wdf01005 failed. For More details check the Log File c:\windows\Wdf01005Inst.log
    0.031: Update.exe extended error code = 0xf0f4
    0.031: Update.exe return code was masked to 0x643 for MSI custom action compliance.

     

    I then noticed that moving the wireless mouse receiver to any other USB Port caused it to not be installed - basically it works great on the one port that I first plugged it into after MVanZee's recommendations - but other ports still seem to get hung in the update.exe process - perhaps trying to install the drivers...? 

     

    So...  I'm closer... but not there yetWink  Any Further IdeasWink?  I'm going to retrace some steps and re-install activesync, and redo MVanZee's steps to see if I can get  a few more devices workingWink  I suspect that any time I reinstall Logitech's drivers I may need to "re update" something that gets stepped on...?    Thanks for listeningWink

     

    CaptPat

    2008년 10월 7일 화요일 오후 4:26
  • I very much love you right now! I just spent four hour googling before i found you post.. And now it f... works!
    2009년 6월 19일 금요일 오후 7:15
  • It's been a while since I posted this, but the knowledgeable techs at Microsoft have provided me with a solution that worked for us at any rate.

     

    1. Open %windir%\inf folder.
    2. Backup and delete these files:

    - INFCache.1
    - msmouse.pnf
    - input.pnf

    3.       Open a command line and run
    Net stop Cryptsvc
    4.       Backup and delete this folder “%windir%\system32\catroot2”
    5.       Reboot the computer to make sure the information was clean up.
    6.       Insert USB mouse to another port which hasn’t been used before.

    7.       Uninstall all HID devices than "Scan for new hardware"

     

     

     

    This worked like a charm! thanks alot man spent hours looking for a solution.
    2009년 7월 14일 화요일 오후 1:23
  • BINGO!  This (Almost) Worked!  Other steps that "helped" - I updated to latest Windows Installer as noted in a later post on this thread - that helped a little with some devices - seemed to make the storage class of devices work better, and CardScan Pro seemed to work after that - also the Belkin 7-port HUB no longer seemed to be a problem (before this it was an "unknown device" despite needing no drivers).  Second, I re-installed Active Sync latest version and it (thankfully) reported "Updating USB Drivers" - and then my ATT Kaiser/Tilt was able to connect...  However nothing seemed to allow Logitech Nano or MX Revolution drivers to complete installation - they seemed to hang while attempting to install the windows user mode driver framework or kernel mode driver framework leaving a log file at C:\windows\wdf01005Inst.log with an error message in it and a temp directory in C: with update files in it.

     

    I then read MVanZee's post and it looked like a good bet - so I deleted all the PNF's for fun since they get recreated as needed, and deleted INFCache.1, stopped the crypto service and deleted Catroot2 - rebooted a bit later - and when I inserted the mouse "receiver" I got further in the installation - beyond prior attempts  - Logitechs driver began prompting for a missing file from the Logitech CD - so I stopped that install, and re-ran the SETPOINT 4.6 installer (logitech doesn't seem to be able to install any other way for most of their devices), and after a reboot I tried the receiver once more, and it simply reported "Logitech USB HID Device Found" in the taskbar of WindowsXP - and the wireless mouse worked worked !!  So I swapped the Revolution device for the Nano device in the same port and it worked fine - didn't even report a "new device found" - just silently worked as advertisedWink

     

    Thank You MVanZee  - thanks also to the person who pointed me to the latest windows installer.

     

    After the above success, I decided to test things further so I plugged in an MP3 device and it did not complete installation as a storage device, then I tried a logitech camera and it ALSO did not install - both seemed to hang with "Windows Service Pack Installer" running (update.exe) from the temp directory created in the C: directory.    Here's the (repeated) error in the log file:

    0.031: ================================================================================
    0.031: 2008/10/07 11:30:33.906 (local)
    0.031: c:\fb74e1e59d13c118d09a77f6\update\update.exe (version 6.3.4.0)
    0.031: Hotfix started with following command line: /quiet
    0.031: In Function GetBuildType, line 1170, RegQueryValueEx failed with error 0x2
    0.031:  C:\WINDOWS\system32\DRIVERS\wdf01000.sys is Present
    0.031: FileVersion of C:\WINDOWS\system32\DRIVERS\wdf01000.sys is Greater Than 1.5.5600.0
    0.031: Condition Check for Line 1 of PreRequisite returned FALSE
    0.031: ReadStringFromInf: UpdSpGetLineText failed: 0xe0000102
    0.031: Wdf01005 Setup encountered an error:  Setup cannot continue because one or more prerequisites required to install Wdf01005 failed. For More details check the Log File c:\windows\Wdf01005Inst.log
    0.031: ReadStringFromInf: UpdSpGetLineText failed: 0xe0000102
    0.031: Setup cannot continue because one or more prerequisites required to install Wdf01005 failed. For More details check the Log File c:\windows\Wdf01005Inst.log
    0.031: Update.exe extended error code = 0xf0f4
    0.031: Update.exe return code was masked to 0x643 for MSI custom action compliance.

     

    I then noticed that moving the wireless mouse receiver to any other USB Port caused it to not be installed - basically it works great on the one port that I first plugged it into after MVanZee's recommendations - but other ports still seem to get hung in the update.exe process - perhaps trying to install the drivers...? 

     

    So...  I'm closer... but not there yetWink   Any Further IdeasWink ?  I'm going to retrace some steps and re-install activesync, and redo MVanZee's steps to see if I can get  a few more devices workingWink   I suspect that any time I reinstall Logitech's drivers I may need to "re update" something that gets stepped on...?    Thanks for listeningWink

     

    CaptPat


    The latest Logitech Setpoint software is 4.72, CaptPat, which I'm using with my logitech wireless usb mouse on WinXP SP3.

    Latest Winodws Installer 3.1 update I know of for WinXP/2003 is KB968006 .  Install MSI 3.1 KB893803 v2 first, then install the KB968006 update.  Or install MSI 4.5 KB942288 and then apply the KB967756 hotfix.
    2009년 7월 14일 화요일 오후 3:48
  • It's been a while since I posted this, but the knowledgeable techs at Microsoft have provided me with a solution that worked for us at any rate.

     

    1. Open %windir%\inf folder.
    2. Backup and delete these files:

    - INFCache.1
    - msmouse.pnf
    - input.pnf

    3.       Open a command line and run
    Net stop Cryptsvc
    4.       Backup and delete this folder “%windir%\system32\catroot2”
    5.       Reboot the computer to make sure the information was clean up.
    6.       Insert USB mouse to another port which hasn’t been used before.

    7.       Uninstall all HID devices than "Scan for new hardware"

     

     

     


    Good to see that this worked for some but not for me :o(

    About a week ago all of my USB ports stopped working.

    They have power (mouse laser lights up, USB lamp is bright as a button etc.) but none of the plugged in peripherals are recognised.  I usually have my mouse (Logitech MX5), keyboard (Logitech), 2 x external HDD (500Gb and 750Gb), camera and a hub with 4 ports but these rarely have more than one thing (USB stick) plugged in.

    In addition to the above solution I have also:
    * Uninstalled all the USB areas in Device Manager.  Used Find Hardware Changes, which re-installs the USB parts and even "sees" any USB devices I leave in (i.e. the yellow triangle comes up in "Other Devices") but these dissapear when the main USB section is installed.
    * Used a so-called registry workaround from the Asus website
    * Carried out a full CMOS reset (removing battery and moving jumpers, as per Asus manual)
    * Unplugged all USB devices and tried each one in different sockets INCLUDING a USB/PCI card
    * Sacrificed a chicken by the light of a full moon (see how desperate I am?)

    Something else that I find strange is that when this all happened I'd had updates every night for 6 days (unusual) and my broadband router/hub worked until I unplugged it to check other devices.  I'm now having to go via a "normal" LAN cable.

    Any ideas?

    I don't think the ports are fried, because the USB/PCI card has stopped too.  But any suggestions will be welcomed.

    Thanks all.

    2009년 7월 15일 수요일 오후 1:24
  • Hi!

    Thanks. Your answers solved my USB Mouse problem too! I know this post is old, but I just wanted to add a few comments:

    In my case this was enough:

    1. Open %windir%\inf folder.
    2. Backup and delete these msmouse.pnf
    5. Reboot the computer to make sure the information was clean up.
    6. Insert USB mouse to another port which hasn’t been used before.
    7. Uninstall all HID devices than "Scan for new hardware"

    To solve this permanently I had to include Windows Installer 4.5 (pre-installed) in my WinXP (w/SP3) image (legacy RIS).

    It seems like WI4.5 handles the driver signing differently (better) from the old WI3.1 version.

    Moving on to Windows 7 soon....all this will be history...

    Again, thanks for this sollution.

    Frode.

    2010년 2월 5일 금요일 오후 1:50
  • Hi!

    Thanks. Your answers solved my USB Mouse problem too! I know this post is old, but I just wanted to add a few comments:

    In my case this was enough:

    1. Open %windir%\inf folder.
    2. Backup and delete these msmouse.pnf
    5. Reboot the computer to make sure the information was clean up.
    6. Insert USB mouse to another port which hasn’t been used before.
    7. Uninstall all HID devices than "Scan for new hardware"

    To solve this permanently I had to include Windows Installer 4.5 (pre-installed) in my WinXP (w/SP3) image (legacy RIS).

    It seems like WI4.5 handles the driver signing differently (better) from the old WI3.1 version.

    Moving on to Windows 7 soon....all this will be history...

    Again, thanks for this sollution.

    Frode.


    Thank a lot, this worked for me.

    1. Open %windir%\inf folder. (just type that in your address bar or C:\windows\inf folder)
    2. Backup and delete these msmouse.pnf

    I didn't had to reboot, all i did was uninstalled the HID Device and rescan for hardware change and that was it. my hp usb mouse started to work.

    2010년 3월 26일 금요일 오전 5:13
  • Hi!

    Thanks. Your answers solved my USB Mouse problem too! I know this post is old, but I just wanted to add a few comments:

    In my case this was enough:

    1. Open %windir%\inf folder.
    2. Backup and delete these msmouse.pnf
    5. Reboot the computer to make sure the information was clean up.
    6. Insert USB mouse to another port which hasn’t been used before.
    7. Uninstall all HID devices than "Scan for new hardware"

    To solve this permanently I had to include Windows Installer 4.5 (pre-installed) in my WinXP (w/SP3) image (legacy RIS).

    It seems like WI4.5 handles the driver signing differently (better) from the old WI3.1 version.

    Moving on to Windows 7 soon....all this will be history...

    Again, thanks for this sollution.

    Frode.

    Thank a lot, this worked for me.

    1. Open %windir%\inf folder. (just type that in your address bar or C:\windows\inf folder)
    2. Backup and delete these msmouse.pnf

    I didn't had to reboot, all i did was uninstalled the HID Device and rescan for hardware change and that was it. my hp usb mouse started to work.
    2010년 3월 26일 금요일 오전 5:13
  • MVanzee, it worked for me!!!!!! U rock - I was trying to fix this from last 4 hours and ur post fixed it for me..its very hard to find soultion for this on net.

    thankyou

    alok

    2010년 4월 11일 일요일 오전 3:18
  • It's been a while since I posted this, but the knowledgeable techs at Microsoft have provided me with a solution that worked for us at any rate.

     

    1. Open %windir%\inf folder.
    2. Backup and delete these files:

    - INFCache.1
    - msmouse.pnf
    - input.pnf

    3.       Open a command line and run
    Net stop Cryptsvc
    4.       Backup and delete this folder “%windir%\system32\catroot2”
    5.       Reboot the computer to make sure the information was clean up.
    6.       Insert USB mouse to another port which hasn’t been used before.

    7.       Uninstall all HID devices than "Scan for new hardware"

     

     

     


    Worked like a treat - followed word for word - The pc wouldn't see the keyboard also - so in addition I deleted keyboard.pnf.  Both now working fine
    2010년 7월 13일 화요일 오후 2:29
  • Did you download and install the correct drivers?


    If the issue still occurs, you can disable all startup items and third party services when booting. This method will help us determine if this issue is caused by a loading program or service. Please perform the following steps:

    1. Click the Start Button type "msconfig" (without quotation marks) in the Start Search box, and then press Enter.

    Note: If prompted, please click Continue on the User Account Control (UAC) window.
     
    2. Click the "Services" tab, check the "Hide All Microsoft Services" box and click "Disable All" (if it is not gray).
    3. Click the "Startup" tab, click "Disable All" and click "OK".

    Then, restart the computer. When the "System Configuration Utility" window appears, please check the "Don't show this message or launch the System Configuration Utility when Windows starts" box and click OK.

    Please test this issue in the Clean Boot environment, if the issue disappears in the Clean Boot environment, we can use a 50/50 approach to quickly narrow down which entry is causing the issue.

    The issue can also be caused by the ACPI of your BIOS. If the issue still occurs in Clean Boot Mode, I suggest you upgrade the BIOS.

    If the above suggestions do not help, I suggest you contact the technical support for Microsoft Hardware.

    Microsoft Help and Support - Hardware

     

    2010년 7월 14일 수요일 오후 9:59
  • WOW..bump this article....been working on this for now, the 3rd day.  Was getting to reinstall.  I'll tell my quick story.  I had stripped down effects/services/programs on my older P4 dell.  Everything worked just great after that.  I noticed that somehow my intellipoint had been disabled and I wanted to have the features like zoom etc.

     

    So I install MS intellipoint 8.1.  I have WXP SP3 and a MS Laser wireless Mouse 5000.  Immediately after almost being done it says something like mouhid.sys doesn't exist.  After that the 3 day nightmare ensued.  I reinstalled drivers, different versions of intellipoint, did a recovery, did a sfc /scannow, manually tried to install drivers etc and it kept showing up as MS optical mouse 1.0 etc etc.  An absolute nightmare and only because of my intense stubborness did I even read this article and try it. 

    FWIW this was my "last" try at anything as I was going to clean house and reinstall XP.  Thanks again!

    2011년 3월 2일 수요일 오전 5:49
  • MVanZee, your (and Microsoft's) solution here is a real timesaver.

    I had a client bring in a workstation with a failing hard drive. Replaced the drive, performed a data rescue copy (bit-for-bit) of the old 80 GB drive to a new 500 GB drive, everything worked great... until we plugged in a USB mouse.

    Then it would bring up a 'new hardware found' dialog which finished with this: There was a problem installing this hardware: HIDClass

     

    There was a problem installing this hardware: HIDClass

    An error occurred during the installation of the device:

    The driver installation file for this device is missing a necessary entry. This may be because the INF was written for Windows 95 or later. Contact your hardware vendor.

    A Logitech mouse would work, a Microsoft mouse would work, any PS/2 mouse would work... but their Lenovo mouse kept coming up with this unrecognized HID device.

    One thing, in this case:  After following your procedure, it still listed the USB mouse under 'Other Devices' in Device Manager.  I had to manually select 'update driver,' it came back and said the best driver was already installed -- but it went from 'Other Devices' with a warning mark to working properly no matter which port it's plugged into.

    I spent a lot of time searching before I found this; there's a lot of useless and outright wrong noise out there. I leave this error screenshot and text in the hopes that others encountering a similar problem will find this solution more readily.


    • 편집됨 BryanMichael 2011년 10월 17일 월요일 오전 3:04 exact syntax of error message (capitalization)
    2011년 10월 17일 월요일 오전 3:02
  • Thank you very much MVanZee for posting this. It helped me fix a similar problem that turned out to be a corrupt msmouse.inf file.
    2012년 6월 9일 토요일 오전 10:59
  • It's been a while since I posted this, but the knowledgeable techs at Microsoft have provided me with a solution that worked for us at any rate.

    1. Open %windir%\inf folder.
    2. Backup and delete these files:

    - INFCache.1
    - msmouse.pnf
    - input.pnf

    3.       Open a command line and run
    Net stop Cryptsvc
    4.       Backup and delete this folder “%windir%\system32\catroot2”
    5.       Reboot the computer to make sure the information was clean up.
    6.       Insert USB mouse to another port which hasn’t been used before.

    7.       Uninstall all HID devices than "Scan for new hardware"


    2012년 6월 9일 토요일 오전 11:02
  • 1. Open %windir%\inf folder.
    2. Backup and delete these files:

    - INFCache.1
    - msmouse.pnf
    - input.pnf

    3.       Open a command line and run
    Net stop Cryptsvc
    4.       Backup and delete this folder “%windir%\system32\catroot2”
    5.       Reboot the computer to make sure the information was clean up.

    That worked. Thank you very much!

    2012년 11월 25일 일요일 오후 4:09
  • MY PROBLEM WAS SOLVED USING THE FOLLOWING:
    I HAD USB mouse, which causes the error, especially when it was plugged.
    (I have detected that after testing the BIOS option for USB enable/disable).
    So, i unplagged it, and then with LAPTOP's built in mouse, i browsed INTERNET and i founded solutions at -


    1) http://en.community.dell.com/dell-groups/new-to-community/f/3511/t/19249216.aspx


    My FIX was following:
    after i uninstalled the MOUSE Driver from DEVICE MANAGER, then i copied usbport.sys,usbui.dll, usbhub.sys, usbuhci.sys files from
    C:\WINDOWS\system32\ReinstallBackups\0010\DriverFiles\i386
    to 

    C:\WINDOWS\system32\drivers
    and
    C:\WINDOWS\system32\drivers\files

    and after that, i plugged my mouse, and windows works normally!!


    2014년 1월 22일 수요일 오후 1:12