This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

BMW Navigator VI - not recognised - DELL Win 10

Former Member
Former Member
HI All - hope somebody has the fix to this.
I just bought the Garmin BMW Navigator VI but when I plug it to my DELL laptop (Win 10), nothing happens. I can only see the navigator switching on and that the battery is recharging.
I went though different forums and it seems there is an issue with Win 10 but I could not found the solution.

I need to connect it via Garmin Express to register it and make all required updates but, as I said above, it is not recognised.

Any suggestions? Something I need to somehow update on the nav before it gets recognised?

The Laptop is a DELL XPS running on Win 10.


Thanks
Christian


  • Former Member
    0 Former Member over 5 years ago in reply to Former Member

    Hi 5926476,

    Garmin has had this problem for a long time. There is one thing I learned testing on my laptop with various USB gear. It's not that Garmin doesn't work with USB 3, because sometimes it does, what I found is that some USB 3 ports on my laptop (Dell 5510 Precision) have a Dell proprietary tech they call PowerShare. So what is Powershare on Dell's laptops, its something that allows USB devices plugged into a standard USB 3 port to be charged when the laptop is turned off, don't fully understand it, and there's very little literature on it searching through Dell's website, I even asked a Dell tech over the phone about it once, and they said they never heard of it, but check out Dell's specs on powershare.

    https://www.dell.com/support/article/en-us/sln155147/usb-powershare-feature-on-dell-laptops?lang=en

    I suspect maybe Samsung and others have similar or other tweaks to their systems that prevent Garmin V & VI Navigator from connection, I have not seen any other device that fails on these USB 3 ports, I have ton's of gear I use from music servers, to various interfaces to mobile phones to scanners and camera equipment, and all connect via these Dell USB 3 ports, all but the Nav V & VI.

    My fix was to purchase a USB-c to USB-3.0 adapter from Amazon, heres the link in case your equipment has USB-c. 
    https://www.amazon.com/gp/product/B07CVX3516/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&psc=1

    Hope this helps, and more importantly, I really hope that Garmin can find a fix for this.

  • Former Member
    0 Former Member over 5 years ago in reply to Former Member

    UPDATE: I bought two different USB hubs and neither of them solved the issue. I ended up trying every laptop in our home which included Dell, Samsung and HP but still couldn't connect. I was finally able to connect when I used my son's old AlienWare gaming laptop. I wish I could be more help to all those who come after and cannot connect. I know there will be many who can't and Garmin isn't doing anything to make this problem go away. 

  • Former Member
    0 Former Member over 5 years ago in reply to Former Member

    Thank you for the help! It isn't just Dell. I couldn't get it to connect on Samsung or HP either. Maybe they also have some sort of Powershare system. If that is the case then, again, because those systems are now common across many manufacturers, Garmin needs to update their product to work with those systems. I ended up getting a successful connection on my son's AlienWare laptop. That particular laptop has many various USB ports and is configured to attach things to.

    This is clearly a Garmin issue. I am at a loss to explain why they would choose to make it so difficult. I am no expert but every other piece of tech seems to have figured out how to accomplish things of this nature without jumping through so many hoops so why can't Garmin? 

  • If you haven't already I suggest you call Garmin and let them know.

  • Former Member
    0 Former Member over 5 years ago

    I have had the same problems with my NAV VI and my HP Envy with USB3.0. I found if I just left it connected, over a minute or two, it would eventually connect on it's own.

  • Former Member
    0 Former Member over 4 years ago in reply to SUSSAMB

    The MTP settings solution worked for me.