Map Sync Failed

Hi,

I have posted this before but unhelpfully the thread was closed with no resolution.

I contacted support who recommended I reset everything to default settings and try again, which I did, however, the same problem persists and maps download to 95% and I get a map sync failed error. 

Garmin support offered me a “good will gesture” watch replacement, which is not a brand new watch and is a “recertified” watch which is basically one that has been returned by someone else. Why would I return a 8 week old watch I have had from new for one which may be far older, when no one can confirm if my watch is actually faulty or if this is a software issue (from reading this forum it appears others have the same issue and it is a software issue).

Clearly Garmin need to update the software so OIA updates can be completed (I don’t have a home computer to use Garmin express). The good will gesture of a recertified watch is not acceptable, if my watch is indeed faulty I would expect to receive a new working watch. If the watch cannot perform OIA updates, as advertised, and a home computer is necessary, I would want a full refund on the product as this is clearly misadvertised as it is unable to perform the advertised functions. I expect far more from a watch that has cost nearly £600 and a further £200 to buy the sensors etc. 

Please do not close this thread again without any adequate information, is this a watch defect or a known software problem. If it is the latter please advise if this going to be rectified. If it is the former please advise how I can receive a refund for the watch and sensors I have invested in. 


+

  • It’s good to know in a weird way it’s not just my device but very weird they can’t fix this or acknowledge it’s something that needs fixing…. 

  • The strange thing is that until about a year ago the maps update via OTA worked perfectly.
    Now only the watch software update works, always via OTA. Obviously the wifi network and its settings have remained the same so it is clear that a bug has occurred that is inexplicably denied by Garmin.
    Let's hope that in the future some higher level manager will read this thread and finally solve the problem because what has been answered here so far is absolutely unsatisfactory. Cheers