Problem with the loading cable

Not sure if it is a design issue, or simply manufacturing defects. I had no issues on my F5. I then had an issue with an F5X, that apparently had been returned to the store, which I also had to return because of the cable causing a sync issue. I grabbed another and it is fine. So, for me two out of three watches are fine. My wife is now using my original F5 and has not experienced an issue. I have connected my watch via Basecamp etc with no connection issues. I suspect it is a bad batch of cables or watches and that the design may be OK, if the parts are manufactured correctly.

Same problem here. Slightest touch of watch/ cable causes a disconnect.

Fenix 5X, v2.9. Garmin Express 5.3.1. MacOS 10.12.5, 2017 Macbook Pro with Touch bar.

And same here - Macbook pro late 2013

Again, it's not that simple.

Same watch, same cable, on my desktop machine I can move things around and do anything short of actually physically unplugging the cable and it remains connected.

On my LAPTOP, again, same watch and cable, if I slightly move the watch it disconnects (but keeps charging.)

This also explains why different people have different results, but it STRONGLY implies that it's not unit-specific.

See and here I think it's update to 2.9 related. I had no problems with my cable or laptop syncing until that update. My watch was rock solid for connection prior. That update came along a week after I had my watch and it's been a crappy connection ever since. Good thing I bought my 24k topo maps while waiting for my watch and they got installed on 2.4 firmware or else there's no way I'd ever have been able to download them and install them, since it took over an hour to do so. I can't connect now for more than a second or two, no matter what USB port I try or messing with the cable. It just won't stay connected, it's like it flickers showing up. And yet, charging it via that same computer and USB, no problem!

I'm on 2.90....

The unit I had to return was on 2.5 (could not get it to update to 2.9, due to sync not completing). On the same Mac, the replacement works fine and it is on 2.9 now. So, I believe in my instance, either the unit or cable was faulty.

I am still not sure what to do.
I tried my 5x now with 3 different PCs and with 2 different cables and in all occasions the data connection broke after I slightly pressed against the cable.
As long as the watch lies untouched at the back everything is fine. To be honest I did not notice the Problem with Software 2.5 and the 2.72 beta but that does not mean it was not there. I just did not give it a test and only used the cable twice not sure if I moved the cable...
I have not noticed any other problems with the watch so far. That´s why I fear when I exchange the watch I might loose a nearly 100% working watch and get other problems that would be more problematic than the cable issue...
Any good advice?
Regards
wolf

If I had one that had problems on BOTH my computers and had changed the cable without benefit I'd RMA the watch.

What I find interesting is that my experience is very different in that I have ONE computer that has problems and another that doesn't -- ever. That implies that either there's a driver issue (correctable, of course) or worse, it's an electrical margin issue that with some computers you're on the wrong side of those margins, and on the other you're on the ok side. The latter is going to be impossible to fix in the cable since as far as I know there are no electronics in the cable itself (it's just a wire.)

I returned the 5x today to Garmin.
Keep you informed on my cable issue after the replacement has arrived.
I will also check with the replacement cable I got which did not work on the "old" watch.
Best regards
wolf

I am having the same issue as others have described.

There is an intermittent connection via USB to the computer. There is some movement in the connection between the lead and the F5x and when this moves the connection goes. If this does not move then "wiggling" the computer end of the cable seems to have no effect on the cable.

this happens with all USB ports on both my desktop and my laptop. They are relatively new computers, the oldest is 18months old. Both are windows 10.

As others have reported I was unaware of this issue until firmware 2.9. I recognise it could have been present, or that it is nothing to do with 2.9, but there is a clear temporal association. I had never had this prior to 2.9 and have it every time, without fail, since 2.9 and I noticed it immediately after 2.9. I did not use the beta firmware, in case that may have had some effect.

Like everyone else I shall open a ticket with Garmin and see what happens