Do NOT Update to Basecamp v 4.7.0!

Sorry this is just a quick message - but because it's kinda important and may cause a lot of confusion - I send out this short newsletter.

 Garmin released a new version of Basecamp - 4.7.0 - in order to remove many features that were not in accordance with the GDPR regulation. Actually it's not that 4.6.2 is wrong here - it's that there were a few web services - that Garmin switched off - and those were interlinked into 4.6.2 - so that actually in 4.6.2 some functionality is not working anymore - I could on a quick check however not discover any actual difference otherwise in relation to the GDPR regulations - so 4.6.2 is no different in this regard to 4.7.0 - well and new privacy page/EULA of course).

Now the problem is - Basecamp 4.7.0 also ships an updated version of Garmin MapInstall - and that version is broken in so far that it does not send any maps in .img format anymore! This also applies to original garmin maps. I have some old Garmin Topo Austria and Garmin City Navigator map - that cannot be sent anymore. Also any of the garmin demo maps converted into .img format from gmapsupp.img do not transfer anymore.


If you are a Windows user and upgraded to 4.7.0 you have 3 choices:

a) Downgrade to Basecamp v 4.6.2: it can be found here:

ATTENTION - you need to first deinstall Basecamp, then Install Basecamp 4.6.2. If you simply install 4.6.2 without deinstalling 4.7.0 Mapinstall is not correctly downgraded.

b) download the OSx (Mac) version of all openmtbmaps/velomaps in .gmap format. You can install them by placing them into the C:\ProgramData\GARMIN\maps\mtbCOUNTRY.gmap respectively C:\ProgramData\GARMIN\maps\veloCOUNTRY.gmap and better read the OSx tutorial too: respectively for Velomap users here:

c) do not send any .img format maps until Garmin releases a new version without this bug.


Actually right now only a part of the overview map is sent - it would be nice if Garmin could send the overview maps in general too - as right now they are only used on Desktop. Would actually speed up the GPS devices a bit - especially if you have no activated Basemap on your device.


Besides this: I'm still working hard on improving the contourlines just another time, and fixing some bugs (e.g. in the Europe continent map right now in the north of Norway/Sweden some contourlines/DEM data is missing). Should not take long anymore. Expect a new release of the Europe map in the next 10 days (also worldwide all maps will come soon with even better DEM/contourlines).



Oh and of course I also updated my Privacy/Rules according to the GDPR rules now effective. Actually nothing changed except that I explained a bit better which data I gather (which was very easy to see/find out anyhow).

In effect I do not store (except temporary logs on my server) any data from users except the one I'm forced to store for invoice creation and making sure you can login to your account. (IP address, email, name, address) and yes I use google analytics in anonymized mode. Still due to great wisdom in actual IT knowledge of our chosen EU representatives and local governments the privacy rules have become long and tedious to read....

If I could I would not store addresses at all - but well VATMOSS EU regulations force me to do so. So nearly all of the personal data I gather, I gather only because just of another super stupid EU regulation.


20 comments to Do NOT Update to Basecamp v 4.7.0!

  • Fitti53

    Hab jetzt wieder Basecamp 4.7.0 installiert. Die Daten des Backups werden
    jetzt vollständig eingelesen. -Glück gehabt.
    Hoffe, dass Garmin das Problem zeitnah lösen kann- und will.

  • Fitti53

    Hallo Felix!
    Der Tipp mit dem Downgrade auf die Basecamp- Version 4.6.2 ist nicht ganz unproblematisch.
    Hierbei gehen alle Daten verloren. Die Wiederherstellung eines Backups, das mit 4.7.0 erstellt wurde, scheint ebenfalls nicht zu funktionieren.

  • Fontanus

    gestern Abend habe ich versucht per PayPal zu zahlen. Leider hat das nicht funktioniert. Eine Wiederholung ebenfalls nicht. Gibt es ein Problem damit?


  • agmaione

    is this suggestion also valid for mac users?

  • agmaione

    this message is also true for mac version of basecamp? or only for windows users?

  • JKT

    It seems it is not just Mapinstall.

    Before reading this, I made a mistake of updating both the BaseCamp and the firmware in GPSMAP64s. Naturally the installed map didn’t work and the img file was also quite small.

    Then I installed BaseCamp 4.6.2 on another computer and installed the map from there. The map was now about correct size, but I had the same error message on the 64s.

    Then I copied the *.img file (that did not work) from the 64s to older 62s and … it worked! So even though the Mapinstaller in the older BaseCamp worked, the new firmware in the Unit did not. What on earth is Garmin up to?

    • JKT

      Another interesting tidbit: the older maps already installed on the 64s still work. So those img files can still be read. That means there is now a difference in img files, which causes them not to work.

      I suppose I’ll try two more things: I’ll send a new map to old device and copy it to new and I’ll send an older map to the new device. This should tell if it is the maps or the firmware messing things up.

      I’ll try to report on results, but there may be a delay.

      • JKT

        OK – here’s what I found: Older maps (up to November 2017) work in both units. Newer maps (from April 2018) work only in the older unit. The new ones I have use the shaded countours, but this may be a co-incidence – at least installation without countour lines did not help. Whether this has anything to do with the latest firmware I can’t say for sure. However, if it did not, I’d think you would have heard about this already.

  • isarbiker

    Hallo Felix,
    vielen Dank für diese Info. Ich habe Basecamp 4.7 deinstalliert und dann 4.6.2 installiert. Beim Aufruf von MAPINSTALL bringt er einen DLL-Fehler… Ich behelfe mir übergangsweie mit MAPSOURCE – da funktioniert das Senden ans GPS wie gewünscht.

    • extremecarver

      Ich habe vom DLL Fehler eigentlich nur gelesen, dass der auftritt wenn eben nicht deinstalliert wurde. Deinstalliere am besten nochmal per Systemsteuerung – dann lösche den Installationsort – und installiere die 4.6.2 neu.

  • Joe

    Hi Felix,
    super vielen Dank für diese Info. Habe leider auch schon 4.7.0 installiert und mich dann gewundert. Jetzt ist wieder alles in Ordnung dank deiner Hilfe.
    LG Joe

  • Roland

    Danke Felix, ich habe dein Posting leider erst nach der Installation von 4.7.0 gelesen und auch den Bug mit meinem Edge 820 nachvollziehen können, habe mich gewundert wie schnell auf einmal die Karten übertragen wurden… Für Windows 10 Benutzer ist eine saubere Deinstallation angesagt, war zumindest bei mir so: also erst 4.7.0 deinstallieren und dann 4.6.2 wieder drauf. Einstellungen bleiben erhalten, zumindest bei mir.

  • CNitz

    Hallo Felix ! Danke für die Info. Kurze Frage. Du redest von 3 Möglichkeiten für Windows User. Wie sieht es mit der MacOS Version aus ? LG Christian

  • Okay. Super. Danke für die Info. Habe eh noch nicht aktualiesert auf 4.7.0.

Leave a Reply