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

Update to Trailforks 2019.10

I opened a new discussion as the subject of "USA/Canada Trailforks maps on European Garmin Edge 530?" that covered the same is misleading and the dicussion in the meantimee very long.

Unfortunately I am still on Trailforks 2018.20 and not on 2019.10. The update to Garmin Edge 530 version 4.10 did not help either.

If anybody does find a solution for this so that I see all those 4.10 enhancements that are linked to the latest Trailfork maps this woudl be great.

Top Replies

All Replies

0 tke_ over 5 years ago

Same issue here. I think Garmin should do some actions here and do something to the back-end server to enable update of trailforks to every device. Trailforks authentication ok and map is active. Unit in Finland (bought from UK).

0 jason106 over 5 years ago

same problem. german edge530. update to 4.10. garmin connect has trailfork auth. no update to 2019.xx. i did map opntions, reinstall

0 jfl_austria over 5 years ago

Same issue here. German Edge830. Update to 4.10. Latest version of Garmin Express.

0 glennursino over 5 years ago

Still nothing. Garmin this can't be too hard to fix. Can we not just get the map file to be able to download and install ourselves.

0 Martin868 over 5 years ago

When connected to a computer, the Garmin Express app offers an option to re-install a map that is already there. Have you tried to do that ?

0 sir_lambo over 5 years ago in reply to Martin868

Tried it a while ago and unfortunately gave me a reinstalled 2018.20. No update...

0 glennursino over 5 years ago in reply to Martin868

Yes. Also completely deleted the map and associated files from the 530 and the express offers a map update which is 2018.20 again.

0 Meistergigi over 5 years ago

Reporting the same problem, only update for 2018.20 avaliable

+1 glennursino over 5 years ago

I received a message from garmin saying they had made some changes and asked me to check. The fix has worked for me so hopefully it works for everyone else too.

0 sir_lambo over 5 years ago in reply to glennursino

Thx for the heads-up. I can confirm that the change did fix the problem for me as well. Update was offered and I am on 2019.10 now.