Home
Join
check
  • I have a location that reported this on 7 HP workstations in the store.  All Prodesk 400 G1 Microtowers running windows 8.1 using the MOFYUO Model HP Optical Mouse that shipped with these.

    Noticed the same issue where the device is coming in as HID in device manager, then switching to USB-c display port.  Confirming update with BizLink Technology.  Have a solution for a quick fix even if your rollback driver is greyed out.  I believe it is greyed because it seems the device is connecting and disconnecting from the system intermittently.

    Here is how I got mine working without doing a driver rollback, I just had to define to use the device as a USB device and not the USB-C Display port adapter.

    Open Device Manager

    Right Mouse Click on: Custom USB Devices -> HP USB-C to DisplayPort Adapter

    Choose Update Driver Software

    Choose: Browse My Computer for driver software

    Choose: Let me pick from a list of device drivers on my computer

    Click Next

    Select: USB Input Device from the options

    Click Next

    You should get a successful update dialog

    Click Close

    Enjoy your working mouse...

    Looks like I'll be returning to the skeptical watch of windows updates.  Good luck!

    Pepper graySpice (15) flagReport
    Was this post helpful? thumb_up thumb_down
  • View Best Answer in replies below

    67 Replies

    • Wouldn't it be easier to give the user a different cheap free mouse rather than spend hours fixing this issue? Those 4 hours you just spent on this could have been used elsewhere, instead of trying to save a $2.50 mouse that came with an old PC.

      Pepper graySpice (16) flagReport
      Was this post helpful? thumb_up thumb_down
    • Hi Ross42.

      We spent about 1 hour troubleshooting the issue for our client.

      The USB mouse came with 50 computers, so maybe it justifies to understand what happen and to solve the issue instead of avoiding the problem. Besides, we like to understand and to explain to our clients what happened, it's the way we like to provide our IT services.

      Certainly this can help other people.

      We appreciate people which can actively contribute to problem solving, not people questioning why we want to solve an issue. Can you imagine if you go run buy 50 brand new good looking and expensive mouses to your client telling them that it will solve the issue and then you realize that the problem wasn't mouse related but instead malware or other thing? ;-) 

      Pepper graySpice (23) flagReport
      Was this post helpful? thumb_up thumb_down
    • Sometimes avoiding the problem IS the best solution. But if you're dealing with them in bulk, then i can definitely understand spending a few hours on this topic.

      After a certain point though, it isn't worth it to keep looking. I'm not sure what that cutoff is for you, obviously.

      Pepper graySpice (5) flagReport
      Was this post helpful? thumb_up thumb_down
    • We just discovered this exact same issue with the new mice we've been receiving with new computers.  It looks to me like the issue is due to the mouse itself.  We've found that there are two different "types" of the same mouse, they both have the same part numbers but the difference is the bottom shell. One type works without issue and the other gets falsely detected as a USB-C to display port adapter.

      Details about each are as follows,

      Working design:  sticker with part number and serial numbers is located in the center above the optical sensor.  Manufacturer appears to be Silitek Electronics M/N: SM-2022

      Non-Working design: sticker with part and serial number is above and to the left of the optical sensor.  Manufacturer appears to be Primax Electronics Model: MOFYUO

      Pepper graySpice (10) flagReport
      Was this post helpful? thumb_up thumb_down
    • What a stupid problem. Was prepping a new PC and had this happen with the mouse discussed here (and in the case of jeffkrueger3's post, the exact model he indicates is problematic).

      Was not able to roll-back the driver package so proceeded with complete uninstall. Windows 7 detected and reinstalled the same stupid USB-C adapter (it's obtaining driver info from Windows Update). Had to kill networking and proceed to reinstall offline way in order to get the mouse functioning (using generic USB Input Device driver). I wonder if this is HP's fault or another Microsoft Update problem?

      Pepper graySpice (3) flagReport
      Was this post helpful? thumb_up thumb_down
    • Hi,

      The "revert driver" button was not available or blocked.

      I had to uninstall the driver firstly (ckecking the remove as you posted...), unplug and plug the mouse again and then "revert driver" button appeared available and i could gladly revert the driver and solve the problem.

      The mouse works perfectly till you simple search for more windows updates through the Windows Update "console".

      This is not enough. We need to know how to completely remove the update that caused this.

      Regards,

      Ricardo

      Pepper graySpice (2) flagReport
      Was this post helpful? thumb_up thumb_down
    • Ross42: Amateurs do solve issues as you suggest, by avoiding the issue, getting a different mouse and hoping it will work. A professional needs to understand what happened, so that it could be fixed with a certainty that it is going to work even tomorrow.

      Pepper graySpice (13) flagReport
      Was this post helpful? thumb_up thumb_down
    • Would be interesting to know if HP used BizLink's USB Vendor ID or if BizLink made an error and included the HP Vendor ID in the driver.

      Pepper graySpice (6) flagReport
      Was this post helpful? thumb_up thumb_down
    • I have a location that reported this on 7 HP workstations in the store.  All Prodesk 400 G1 Microtowers running windows 8.1 using the MOFYUO Model HP Optical Mouse that shipped with these.

      Noticed the same issue where the device is coming in as HID in device manager, then switching to USB-c display port.  Confirming update with BizLink Technology.  Have a solution for a quick fix even if your rollback driver is greyed out.  I believe it is greyed because it seems the device is connecting and disconnecting from the system intermittently.

      Here is how I got mine working without doing a driver rollback, I just had to define to use the device as a USB device and not the USB-C Display port adapter.

      Open Device Manager

      Right Mouse Click on: Custom USB Devices -> HP USB-C to DisplayPort Adapter

      Choose Update Driver Software

      Choose: Browse My Computer for driver software

      Choose: Let me pick from a list of device drivers on my computer

      Click Next

      Select: USB Input Device from the options

      Click Next

      You should get a successful update dialog

      Click Close

      Enjoy your working mouse...

      Looks like I'll be returning to the skeptical watch of windows updates.  Good luck!

      Pepper graySpice (15) flagReport
      Was this post helpful? thumb_up thumb_down
    • Just as I suspected, there are many people running into this issue.

      Thundervortex, yes we really need to be careful with the updates...

      Pepper graySpice (3) flagReport
      Was this post helpful? thumb_up thumb_down
    • Hello,

      on Win 8.1 I rersolve the issue simply unistalling the driver "HP USB-C to DisplayPort Adapter" you said.

      THANK YOU!!!

      Pepper graySpice (1) flagReport
      Was this post helpful? thumb_up thumb_down
    • I'm having the same problem and i solved it by removing the driver.

      But this update is categorized as important and windows will try to install it again.

      How can we report to Microsoft this issue?

      Pepper graySpice (3) flagReport
      Was this post helpful? thumb_up thumb_down
    • Just did it like Thundervortex suggested!

      The issue is overtaken! The mice are working fine now and I am able to proceed into applying all the following windows updates, including a recent major one for Windows 10.

      Thank you all.

      Ricardo Santos

      PT - Lisbon

      Pepper graySpice (4) flagReport
      Was this post helpful? thumb_up thumb_down
    • are you sure?

      because this morning, approximately at 10:30 am, i was preparing a new PC with Windows 8.1 and that driver was installed with the mouse issue.

      I have already removed it and installed it again but the mouse issue remain.

      The driver is still there in the important updates and sooner or later windows will install it, if i don't disable the automatic installation of the updates.

      So, what do you mean with overtaken? and what is Thundervortex?

      Pepper graySpice (1) flagReport
      Was this post helpful? thumb_up thumb_down
    • Please check above Thundervortex's contribution...

      Pepper graySpice (1) flagReport
      Was this post helpful? thumb_up thumb_down
    • Gracias, es un buen aporte me estaba volviendo loco sin saber que les pasa a los Mouse.

      Was this post helpful? thumb_up thumb_down
    • Same issue with our company. We started receiving calls at 3pm yesterday (Eastern Time). We narrowed it down to a specific HP mouse model and a HP 600 G1. Updating the driver and picking from the list as a "USB input device" resolved the issue. Simply disabling the device will not fix issue.
      HP mouse assy p/n is 672652-001 Spare p/n 674316-001. Can someone confirm if you have the same mouse that is having this issue

      Was this post helpful? thumb_up thumb_down
    • I can confirm that sm-2022 manufacturer of the HP mouse

      Was this post helpful? thumb_up thumb_down
    • ahh ok ricardosantos9, i have already tried the Thundervortex solution but the driver is still there in the important updates.

      Then i must disable windows updates or hide manually the that driver device update.

      Was this post helpful? thumb_up thumb_down
    • Yes, also my mouse are HP mouse p/n is 672652-001 Spare p/n 674316-001

      Was this post helpful? thumb_up thumb_down
    • Hi everyone,

      To completely remove the driver package:

      - open a CMD prompt as admin

      - use pnputil.exe -e and identify the hp package (custom USB devices)

      - use pnputil.exe -f -d Oem*.inf (*=n° of inf package)

      Regards,

      Pepper graySpice (1) flagReport
      Was this post helpful? thumb_up thumb_down
    • Thank you so much! This is exactly what's going on in my school district. Much appreciated.
      (Thank you for providing all this help and not just "replacing with cheap mice" ;])

      Pepper graySpice (2) flagReport
      Was this post helpful? thumb_up thumb_down
    • Hmph i just ran into the same issue with it on a windows 10 build 10586.14

      Was this post helpful? thumb_up thumb_down
    • Thundervortex wrote:

      I have a location that reported this on 7 HP workstations in the store.  All Prodesk 400 G1 Microtowers running windows 8.1 using the MOFYUO Model HP Optical Mouse that shipped with these.

      Noticed the same issue where the device is coming in as HID in device manager, then switching to USB-c display port.  Confirming update with BizLink Technology.  Have a solution for a quick fix even if your rollback driver is greyed out.  I believe it is greyed because it seems the device is connecting and disconnecting from the system intermittently.

      Here is how I got mine working without doing a driver rollback, I just had to define to use the device as a USB device and not the USB-C Display port adapter.

      Open Device Manager

      Right Mouse Click on: Custom USB Devices -> HP USB-C to DisplayPort Adapter

      Choose Update Driver Software

      Choose: Browse My Computer for driver software

      Choose: Let me pick from a list of device drivers on my computer

      Click Next

      Select: USB Input Device from the options

      Click Next

      You should get a successful update dialog

      Click Close

      Enjoy your working mouse...

      Looks like I'll be returning to the skeptical watch of windows updates.  Good luck!

      Thundervortex you safed my hardwares life cause i was about to go & play soccer with the damn mouse as i couldn't play my favourite time waster anymore

      Was this post helpful? thumb_up thumb_down
    • Edwin_Eekelaers wrote:

      Thundervortex wrote:

      I have a location that reported this on 7 HP workstations in the store.  All Prodesk 400 G1 Microtowers running windows 8.1 using the MOFYUO Model HP Optical Mouse that shipped with these.

      Noticed the same issue where the device is coming in as HID in device manager, then switching to USB-c display port.  Confirming update with BizLink Technology.  Have a solution for a quick fix even if your rollback driver is greyed out.  I believe it is greyed because it seems the device is connecting and disconnecting from the system intermittently.

      Here is how I got mine working without doing a driver rollback, I just had to define to use the device as a USB device and not the USB-C Display port adapter.

      Open Device Manager

      Right Mouse Click on: Custom USB Devices -> HP USB-C to DisplayPort Adapter

      Choose Update Driver Software

      Choose: Browse My Computer for driver software

      Choose: Let me pick from a list of device drivers on my computer

      Click Next

      Select: USB Input Device from the options

      Click Next

      You should get a successful update dialog

      Click Close

      Enjoy your working mouse...

      Looks like I'll be returning to the skeptical watch of windows updates.  Good luck!

      Thundervortex you safed my hardwares life cause i was about to go & play soccer with the damn mouse as i couldn't play my favourite time waster anymore

      So this fixes this issue?  LMK if not, I have a post in my internal Yammer group to see if I can get any answers.

      Pepper graySpice (1) flagReport
      Was this post helpful? thumb_up thumb_down
    • OK, so we all know USB devices present themselves with a USB DeviceID and then the OS uses this to decide which driver or drivers to install.

      Either HP reused someones DeviceID in hardware, or Microsoft fat fingered something and is misidentifying the hardware.

      https://msdn.microsoft.com/en-us/library/windows/hardware/ff546284%28v=vs.85%29.aspxOpens a new window

      Pepper graySpice (2) flagReport
      Was this post helpful? thumb_up thumb_down
    • I'm glad my only problem is the cheapness of the HP mice we are getting with our $1200+ HP Z230 SSD Workstations. I've deployed 24 since June, I've had a 25% failure rate! I've never seen mice fail like this before. I wonder if there is any recourse?

      Pepper graySpice (1) flagReport
      Was this post helpful? thumb_up thumb_down
    • Palmtop: thanks for your clear troubleshooting. We ran into the same problem with a client with about 20 HP machines. Late yesterday two users reported their mouses were failing. It was not immediately clear what was going on. But today many more where failing and it was becoming a big problem. It was the exact same problem described here.

      Also thanks to jeffkrueger3: looking at the sticker on the bottom we were quickly able to identify the problem mouses.

      This thread was the only one I could find describing this problem and a solution. Many, many thanks!

      Pepper graySpice (2) flagReport
      Was this post helpful? thumb_up thumb_down
    • Running into the same issue.  Thought I took a wrong turn on driver updates.  Is this showing up in the WSUS list yet?

      Was this post helpful? thumb_up thumb_down
    • I've reached out internally to see if someone knows anything about this, I will update once I get more info.

      I know it might not be funny, but this is what popped into my mind when I heard about issues with mice...


      Pepper graySpice (4) flagReport
      Was this post helpful? thumb_up thumb_down
    •  Sounds like maybe the driver has incorrect device ID info, causing it to misidentify the mice as a converter?  That, or somehow the same ID was reassigned to a new product down the road, lol.   If that is the case, I don't think there's a permanent solution, other than waiting for them to fix the driver release (and rollback, as you did - or assign a generic HID driver)

      Pepper graySpice (3) flagReport
      Was this post helpful? thumb_up thumb_down
    • Chris (Microsoft) wrote:

      Edwin_Eekelaers wrote:

      Thundervortex wrote:

      I have a location that reported this on 7 HP workstations in the store.  All Prodesk 400 G1 Microtowers running windows 8.1 using the MOFYUO Model HP Optical Mouse that shipped with these.

      Noticed the same issue where the device is coming in as HID in device manager, then switching to USB-c display port.  Confirming update with BizLink Technology.  Have a solution for a quick fix even if your rollback driver is greyed out.  I believe it is greyed because it seems the device is connecting and disconnecting from the system intermittently.

      Here is how I got mine working without doing a driver rollback, I just had to define to use the device as a USB device and not the USB-C Display port adapter.

      Open Device Manager

      Right Mouse Click on: Custom USB Devices -> HP USB-C to DisplayPort Adapter

      Choose Update Driver Software

      Choose: Browse My Computer for driver software

      Choose: Let me pick from a list of device drivers on my computer

      Click Next

      Select: USB Input Device from the options

      Click Next

      You should get a successful update dialog

      Click Close

      Enjoy your working mouse...

      Looks like I'll be returning to the skeptical watch of windows updates.  Good luck!

      Thundervortex you safed my hardwares life cause i was about to go & play soccer with the damn mouse as i couldn't play my favourite time waster anymore

      So this fixes this issue?  LMK if not, I have a post in my internal Yammer group to see if I can get any answers.

      Chris i did like mentioned, changed the driver & selected the USB input device manually and the mouse works like a charm again.. Mine's also the Mofuyo model. It is strange that it occurred around the time of the last update that was downloaded.. That displayport thing came as a second update.. Before applying them i was on 10586.3 and afterwards on 10586.14

      I ( and i'm sure a whole lot of others ) am interested to find out what caused it...And i pray it's not gonna happen on Windows 7 too cause i dont want to do the same on 5-600pc's per site we manage

      Pepper graySpice (2) flagReport
      Was this post helpful? thumb_up thumb_down
    • Did anyone log a support case with Microsoft or HP regarding this issue?  If so, can you PM me the details so that I have something to go off of?  I've shared this thread, but if someone already did the leg work on reporting the issue - I want to share this with my team.  Thx.

      Pepper graySpice (2) flagReport
      Was this post helpful? thumb_up thumb_down
    • I had one of these HP mice plugged into a dell laptop and this issue occurred. Only one of the 20 or so desktops that the MOFYOU mice came with has this issue, odd.

      Pepper graySpice (2) flagReport
      Was this post helpful? thumb_up thumb_down
    • Just so its known, we are having the same issues with the same model of mouse on new loads of Win 7 Enterprise, so its not just 8 and 10.

      Pepper graySpice (3) flagReport
      Was this post helpful? thumb_up thumb_down
    • Ran into this today to at our company and a friend at a different company reported the same issue. Since neither one of us had time to really troubleshoot it we both ended up running out and buying a bunch of new cheap USB mice to work around the issue

      Pepper graySpice (1) flagReport
      Was this post helpful? thumb_up thumb_down
    • HP and Microsoft Support is so slow No Tier 1 support persons wants to call them to report the issue.

      I had to go

      "change device installation settings" search for this in your search bar.

      Turn off  automatic Windows device driver installs so  that

       after you delete the driver it won't automatically installs itself again.

      Delete the driver from command line or rollback the driver from device manager.

      Go to windows updates and hide the update .

      This Fixed the problem on my companies machines

      Pepper graySpice (1) flagReport
      Was this post helpful? thumb_up thumb_down
    • Had a phone call about this issue earlier today. We planned on ordering another mouse for the person, but I'm glad that I read this article so now I know how to handle the next call that comes in! Thanks!

      Pepper graySpice (1) flagReport
      Was this post helpful? thumb_up thumb_down
    • We are having the same issues with the same model of mouse on HP Computer with Win 8.1.  After rolling back the driver it works fine.

      I believe the bad update might be https://support.microsoft.com/en-us/kb/3103696Opens a new window

      Pepper graySpice (1) flagReport
      Was this post helpful? thumb_up thumb_down
    • I've got a hammer
      Therefore I can fix anything  :)~

      Have you tried to make certain that your USB's aren't set to automatically turn themselves off? 

      This should save you tons of headaches and, therefore, not to allow the system to go out and search for new drivers when it wakes those ports up.  I've seen similar things happen when they "doze" off

      Pepper graySpice (1) flagReport
      Was this post helpful? thumb_up thumb_down
    • see mypost earlier in this thread. i was able to correct this without rolling back drivers or uninstalling windows updates. you just need to guide windows to the type of device manually using device manager and updating the device driver.

      Pepper graySpice (4) flagReport
      Was this post helpful? thumb_up thumb_down
    • Has there been any official update or messaging from Microsoft?

      Thanks,  Rich

      Pepper graySpice (1) flagReport
      Was this post helpful? thumb_up thumb_down
    • </lurk>

      Wow Palmtop, congratulations on your first post, you got a great response, and helped a lot of people.

      Nice going.

      <lurk>

      Pepper graySpice (2) flagReport
      Was this post helpful? thumb_up thumb_down
    • You can always hide the update, but you have to check if it shows up in windows update after you uninstall the update.

      Jeff

      Was this post helpful? thumb_up thumb_down
    • There is no way to hide the update in Windows 10. At least I don't found it...

      Was this post helpful? thumb_up thumb_down
    • I wonder if it is scriptable to do so. Who's going to be the first one to do this in Powershell?

      Was this post helpful? thumb_up thumb_down
    • I just did a test: cleaned the Windows Update cache, rebooted, verify for updates and, apparently, the buggy update is gone!

      Can anyone confirm that too?

      Was this post helpful? thumb_up thumb_down
    • I hate it when Windows Updates overrides drivers like this... I had the same thing happen yesterday and it baffled me that they could screw that up so badly.

      Pepper graySpice (2) flagReport
      Was this post helpful? thumb_up thumb_down

    Read these next...