Fenix 5 not recognized by PC (Windows 10)

Since a few weeks, I have a problem with my Fenix 5. When I connect it to a computer (Windows 10), the watch is not recognized as a device (i.e. does not show up at all in the Explorer) - its also not shown in connected USB devices.

It does charge however. Tried on three different computers with two different cables....

Its not a problem for now as luckliy I can still cahrge the watch, however it would be nice so I can put beta firmwares on it (and sometimes I also put courses / swim workouts directly on the watch).

Any idea? Or is this directly a Garmin support issue?

  • same issue with my fenix 5s. I did not find a solution: unknown USB device 8device Descriptor request Failed)

  • Putting the watch in Garmin mode and using garmin Express as administrator worked for me. 

    When asked on the watch to switch mode just press yes and wait. 

  • I eventually took my watch apart to see why it wouldn't connect to USB anymore though would charge but only when the cable was connected in only one orientation (it used to charge and connect to USB with the cable in either orientation).

    I found one chip near the charger pins that had clearly blown up. Will attach picture.

    This doesn't help much as I have no schematics and the IC isn't marked, though I suppose it is to do with the USB. My guess is that I blew it up when out camping and was having problems getting it to charge so I kept connecting and disconnecting the charger.

    I'll just keep using it until it totally fails and then get something new.

  • Thanks. This worked instantly. 

  • Just went through this express/fenix5 usb disconnect nonsense(AGAIN, last episode was roughly 4 months ago and - sorry - but, I couldn't recall the precise combination of variables, in the correct order, while in the optimum zen aura that I utilized to magically mate the component to the software once again)

    Well, today, the express/pc/win 10 functionality once again decided to test my patience. Again, after 2+ hours of carefully sequencing the variables, I was able to reconnect. In addition to the methods listed in detail previously, I believe deleting the profile and remating the watch as a new device in one of the other USB ports on my laptop did the trick(this time)

    I believe the latest win 10 update was the cause. Needless to say, this is all too much work for what should be redimentary usb crosstalk.