Bluetooth Gps issue after Windows 10 upgrade

[steveg47]

I have upgraded 3 different laptops and they all exhibit the same problem. Using Delorme Street Atlas 2009 and a Qstarz 818XT bluetooth I have always been successful in pairing the device and selecting the outgoing com port from the Delorme software. After upgrading to Windows 10 from Windows 8.1 & 7 the Delorme no longer displays the Outgoing com port in it's pulldown gps config menu. I tried downgrading one of the laptops to 8.1 (Lenovo Thinkpad x220) which corrected the problem. I downgraded a 2nd laptop (Asus T100tam) to Windows 8.1 and again the problem disappeared. Since one of my primary uses for these laptops is gps tracking while travelling I cannot use Windows 10 which is really a shame since Windows 10 has improved the performance of these laptops in most other respects.

Note that the 3rd upgrade with similar bad results was a Thinkpad x100e. Two of the laptops use BroadCom bluetooth. Not certain what the x220 uses. I have tried various drivers and reinstalls. And am now wondering if this is a chronic Windows 10 issue. What I would like to know is, has anyone experienced a similar problem with bluetooth com ports using a gps. Any suggestions or a solution greatly appreciated.

[steveg47]

Anyone? Please!

[Dekks]

Looks like you need to contact the authors of the software for win 10 updates.

[steveg47]

The authors????

[RealBlackStuff]

Delorme

[GomJabbar]

Not sure if this will help, but this is how I did something similar back in the day...

http://forum.thinkpads.com/viewtopic.php?t=95307

[erik]

there's a BT virtual COM port issue in 10240.   it's supposedly been fixed in build 10532 and should be released to the public after testing.

here's one thread about it: http://answers.microsoft.com/en-us/wind ... df4abfbb46

[Billaboard]

This is interesting because I have been having trouble testing some Bluetooth vehicle diagnostic interfaces on my one W10 Insider test machine that supports BT.

There has long been a problem in Microsoft's BT -> serial drivers where, if the BT device power cycles when connected the serial port counts up. The serial port on the host machine then is blocked, so the next port is then used. With much of this ODBII software, only the first few ports can be selected, so MS often counts up an out of the way.

On the later builds I haven't been able to get it to work at all, and this thread has pointed me to the reason.

The machine that has BT is set to a local login and so has remained at build 10240. I don't want to change this. Unfortunately the machine that has 10532 doesn't have BT.