MyDrive connect problem with Windows 10
After conducting an intensive internet search, I found that other TomTom users had been experiencing (similar?) problems with Windows 10. I tried many of their suggested remedies, as well as those taken from the TomTom web pages, namely:
· Connecting the USB cable directly to the PC, not through a USB hub, and not using the windshield mount provided with the GO 6100
· Trying several USB ports, with several different USB cables
· Resetting the TomTom device, by holding down the ON/OFF switch until the drum roll
· Uninstalling the MyDrive Connect software and its associated data files, uninstalling my VPN4ALL software, deactivating my ZoneAlarm Extreme Security firewall and anti-virus, and then reinstalling MyDrive Connect.
Since none of these actions were effective, I contacted TomTom Support (French-language department). Their initial response, received after a few days, was basically to suggest the various measures listed above, even though I had already explained in my written request that these were not effective.
I therefore pursued my own investigations. First – and most importantly – I discovered that when I installed MyDrive Connect on my laptop PC, running Windows 7, I was able to connect the GO 6100 normally and update my maps without any problems. Note that this laptop shares the same router and Ethernet connections with the desktop, and runs much of the same software, including VPN4ALL and ZoneAlarm Extreme Security firewall and anti-virus, which I had not removed from the laptop or deactivated.
Second, on the Windows 10 machine, I noted that the TomTom was listed in the Device Manager, under Network Adapters, as being a “Remote NDIS Compatible Device” (with an exclamation mark in a yellow triangle), i.e. there was no specific entry for a TomTom GO 6100, unlike the case of the Windows 7 laptop.
On clicking on the Properties tab of the Remote NDIS Compatible Device, on the Windows 10 machine, the General tab stated that “Windows is still setting up the class configuration for this device. (Code 56)”. Furthermore, pressing the Driver Details button on the Driver tab returned the statement that the necessary driver files were “C:\Windows\System32\Drivers\mdismp6.sys” and “C:\Windows\System32\Drivers\usb80236.sys”. Somewhat surprisingly, when I pressed the Update Driver button, I received the response “Windows has determined that the best driver for this device is already installed”.
I then checked posts on various forums to try and identify what was causing the Code 56 error. In some cases, this was attributed to the use of a Checkpoint VPN. But, as I stated above, uninstalling my VPN software did not help.
So I wrote again to the French-language TomTom Support, outlining my latest observations and queries. Very rapidly, I received a response saying that my explanations indicated that the problem was due to Windows, since I had been able to update my TomTom device using a different PC. I was therefore advised to contact Microsoft’s Technical Support.
Well, I certainly do not deny that my problem is related to Windows – and indeed apparently to Windows 10. Nevertheless, if there is an incompatibility between the TomTom hardware and Windows 10, then it would seem reasonable for TomTom to work together with Microsoft to resolve the issue. After all, Windows 10 is no more or less than the latest version of the world’s most popular operating system – and (according the forums) I do not seem to be the only TomTom MyDrive Connect user having a problem with Windows 10. On the other hand, I can hardly imagine that Microsoft Technical Support would be keen to spend much time trying to resolve an issue with a TomTom GO 6100 and MyDrive Connect, since these are only one example (out of many thousands – or millions?) of third-party hardware and software that their designers wish to run harmoniously using Windows 10. So, I interpret the brief response from French-language TomTom Support as being merely a desire to close the case without putting in any more effort.
Perhaps my correspondent at TomTom also felt that I no longer had any reason to bother her, since I had been able to update my maps using a Windows 7 PC. Well, considering that I had spent more than a whole day trying unsuccessfully to resolve the problem, I was curious to discover what was preventing satisfactory operation under Windows 10. Also, Windows 7 and my old laptop that runs it will not be around forever.
Finally, I am by no means an IT specialist and I find it unacceptable today to have to resort to trying to elucidate how to rectify abstruse “Code 56” situations in order to use a popular and widespread commercial satellite navigation device. After all, you do not need to have in-depth expertise in automobile mechanics to drive a car…