Windows PC does not detect Fenix 6X Pro

Former Member
Former Member

Nothing seems to work for me in the Garmin ecosystem...

Now, my PC (running Windows 10 update 2004) is not able to detect my Fenix 6X Pro. The Garmin device first shows up as Garmin USB GPS, then after some setting up ends up as "Unknown Device" in Control Panel\Hardware and Sound\Devices and Printers. The device never shows up in file manager and is never found by Garmin Express.

I did all the tricks I could find, from both Garmin and Microsoft, e.g. testing different USB ports, forcing reinstall of USB hub drivers, changing USB selective suspend power save settings, and fast start up options, doing an eternal start/stop key press when restarting the device,... nothing unfortunately helped.

Interestingly, a borrowed laptop was able to find the device without issues.

Any ideas?

  • Former Member
    0 Former Member over 4 years ago in reply to NoClaim
    So yes, there seems to be a driver issue.

    I agree some may be having some type of driver issue.  Maybe a file that's gone corrupt?  I had a similar problem where my watch was recognized by my computer (Windows 10), but it didn't matter what version of Express I was using, I kept getting a "communication error" and couldn't update or download anything in Express.  I went to add or remove programs in my control panel to remove Express thinking I'd try a clean slate when I noticed a program called Garmin USB Driver's or something like that.  I removed that program and without reinstalling it everything works great again.  

  • Any ideas?

    Hi.

    Try to check and re/uninstall garmin usb drivers with this program

    www.nirsoft.net/.../usb_devices_view.html

  • I had a similar issue with Windows 10 showing Unknown Device when connecting Fenix 6 Pro.

    After a lot of experimentation, it turned out that I was using Windows 10 N edition, which doesn't have some media support and MTP drivers. I've installed Windows 10 (regular edition, not N or KN) and now Fenix is detected out of the box.

  • Thank you so much for sharing this. I've had my Fenix 6X for 9 months now and was never able to get it to connect to my PC. I also have Windows 10 N. Found instructions to install "Media Features Package" on microsoft.com and it works now!

    To install the Media Feature Pack, navigate to Settings > Apps > Apps and Features > Optional Features > Add a Feature and find the Media Feature Pack in the list of available Optional Features

  • Thank you so much! I was struggling with that exact issue since 3 months. That solved it for me, it would be great if Garmin points out somewhere that Windows 10 N installations need this optional feature installed!

  • I use an MSI 64 bit computer with Windows 10 20H installed.
    Settings > Apps > Apps and Features > Optional Features > Add a Feature and find the MSIX Packaging Tool Driver in the list of available Optional Features > Install.
    Then
    With Garmin fenix 6 Pro Solar connected to USB, Device manager > Checked for USB devices not recognised under > Human Interface Devices; Other Devices; System devices and Universal Serial Bus controllers. Clicked each open to see whether it is working properly. One showed the unrecognised device. I uninstalled, accepted the warnings.
    Updated windows to version 10 21H1 and restarted with watch connected to USB.
    Windows recognised my watch correctly, the Garmin Express App also worked perfectly, updating my watch software.
    All good now.

  • Former Member
    0 Former Member over 3 years ago in reply to 9710584

    Just to clarify, after the update on Win 10 when restarting the system,  the watch is connected to the USB port, and not after that?

  • Thank you for this. My Fenix 6x Sapphire had been working without issue until recently. I'm not sure what changed, but installing the MSIX Packaging Tool Driver fixed it for me. I'm running Windows 10 Pro 21H2.

  • ho seguito tutta la procedura, ma non si collega. in precedenza ho disistallato tutto reistallato ed ha funzionato per un giorno poi di nuovo nulla

  • Thanks. After running Connect once as administrator, this fixed the issue for me.