Windows detects USB GPS as Serial Ballpoint - please suggest permanent modification to prevent any serial mouse detection

Anonymous
2010-02-23T15:33:38+00:00

Using Win7 ultimate on a variety of machines, when I plug in a 'USB' GPS the system does two things: it installs the support for the USB-Serial device, and then it (using 'serenum' apparently) begins mistaking the GPS for a serial mouse, and 'detects' and installs the microsoft serial ballpoint.  I have editted /windows/inf/msmouse.inf, adding a line after line 28 (guessing at the syntax, copying from the alpha excludes)

ExcludeFromSelect.NTx86 = *PNP0F0C,*PNP0F08,*PNP0F09*PNP0F01,*PNP0F0A,*PNP0F1E

This does *NOT* do the trick.  The GPS is consistently being enumerated by the system as a "serial ballpoint mouse".

This has been reported by numerous people in numerous forums on numerous configurations over multiple windows versions.

When is Microsoft going to fix this?  This is not a GPS issue.  This is not a serial device issue.  This is not a USB issue.  This is, pure and simple, a Microsoft issue.

Removing the 'upperdrivers' entry for serenum might do the trick, but the registry keys are not writeable now in Win7.  Sweet.  Thanks, Microsoft.

Windows for home | Previous Windows versions | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

58 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2010-12-05T13:18:11+00:00

    I trimmed the appropriate section (from usb connect to end of log) and uploaded it to my skydrive.

    The issue seems to be that once the usb to serial converter is detected, driver loaded, and com port initialized, windows then checks on the newly added com port and identifies the serial device as a microsoft serial ballpoint, when in fact its a serial gps device

    The gps works if i can correctly remove the ballpoint from the device manager, but on a touchscreen in my car it is pretty difficult since the incorrect driver moves my cursor and clicks mouse buttons as the NMEA data flows over the com port. if there is no proper workaround, even a script to check for the ballpoint in the device manager and remove it would be fabulous, though a way to exclude the device from being detected at all would be best

    Thanks for your time, and since i didnt see the original poster provide a log, I did.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2010-02-28T18:40:59+00:00

    Tom - Why do you think that line you added will help?  Is that based on info you've seen on other forums?

    None of the ID's you mention is a USB ID.  So they shouldn't do anything here.

    What's the specific device that you are using?  Are all of the people reporting the issue with the same device?

    Also, it would be helpful if you could create a public folder on http://skydrive.live.com, and copy c:\Windows\inf\setupapi.dev.log to that share.  This should allow me to see what exactly is happening during the driver install process.

    Want to know if your current hardware & software will work with Windows 7? Check out these links: **Windows 7 Upgrade Advisor ** **Windows 7 Compatibility Center**

    Was this answer helpful?

    0 comments
  3. Anonymous
    2010-02-23T17:13:29+00:00

    Of course the registry is writeable. Make sure you have administrative permissions.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments