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 No comments

58 answers

Sort by: Newest
  1. Anonymous
    2012-01-13T15:23:49+00:00

    Operating System Windows 7 Home Premium 64 bit. (this new laptop had to be purchased Xmas 2010 after burglars stole my excellent and well liked Advent/Gerrycom Blockbuster 2.8GHz Pentium 4 machine) 

    Friday the 13th January 2012 my cursor went crazy jumping around all over the screen.  Menu panes were flashing on and off and jumping about so I thought some hacker had written a Friday the 13th virus.  Nope its the GPS being seen as a Serial Ballpoint Mouse.  Curiously this bug only kicked-in after last nights Windows Updates! 

    This bug has allegedly been around for well over FIVE YEARS.  Quite frankly this is just not acceptable.  Microsoft NEEDS to issue a patch as soon as possible as otherwise I'm going back to XP.  Several years ago I bought a laptop running Vista.  It was a piece of junk that impersonated a fan heater.  I took it back as soon as the store opened and I did get my money back but it required some tough talking.  As there was no Wordprocessor included I tried installing Lotus Smartsuite.  This almost ran as the welcome pane appeared but a line of red  type showed saying that a line of code was missing.  That's almost like having to buy a new car because a thief has stolen the steering wheel.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2012-01-09T22:31:31+00:00

    You are right in thinking that "tricking" Windows into thinking a serial ball point mouse is there & then disabling it seems to work pretty well.

    We belive that USB Serial ports from DIGI (see DIGI.COM) have a patch that is specific to their devices work - however, we have had intermittant problems with these devices going into some sort of "sleep state", which causes problems as well.

    We are switching people away from using serial devices to using Serial / Ethernet converters, and so far aside from being needlessly expensive and wasting time & effort it seems to work well so far.  This is clearly a Microsoft bug, which they have been trying to ignore for a long time.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2012-01-09T21:20:59+00:00

    You're right, this does NOT seem device specific - I'm experiencing a similar problem on a different system!

    Upon the bootup, my system opens the COM port for 'actual' serial communication with other MPU-based devices.

    However the system sometimes pops up a COM port error message, and I see this 'microsoft serial ballpoint' from my device manager - I did tried to disable it, but it comes back.

    What I found so far is, if I force to transmit '0000' to the COM port while it is booting up, the Windows will detect this 'microsoft serial ballpoint'. Haven't found any way to prevent this though..

    I also tried playing with 'EWF' options which did not help.

    Have you discevered any fixes that works from your experience?

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2011-12-01T23:35:29+00:00

    The center is not very useful as Sony Navus aren't even mentioned.  Big company Sony and their merchandise is always good quality.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2011-12-01T20:02:19+00:00

    Windows 7 sixty four bit does similar with the Sony Navu GPS type NV-U93TW.  It thinks that the GPS is a phone!  Presumably the Navu is running Windows CE that most mobile phones use.  Trying to synchronise My Portable Device with the laptop is only partially successful (failure actually).  The laptop can see the Navu and its expansion memory but it cannot read the memory contents or memory size.  Later the message "Synchronisation did not complete" appeared.  The object of the exercise was to try to load marine charts onto the Navu but it looks as if I'm stuffed for the lack of a few lines of code (I'm not a programmer just a dabbler) This is rather annoying especially as my well liked Advent (AKA Gericom Blockbuster)  that ran Xp was stolen by burglars. 

    I've bought a Toughbook which should be here in a day or two and its running ME.  Hopefully this will pair with the Navu.

    If anyone knows how to pair a Navu with Windows 7 I'd be very pleased to know.

    Was this answer helpful?

    0 comments No comments