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

SOLUTION: Map changes failed

Posting this in case it prevents others from tearing their hair out as I did this morning.  After getting past USB connectivity/compatibility errors with my Edge 1030 Plus (lots of posts elsewhere on that... which Garmin needs to hurry up and fix), I started getting very unhelpful "Map changes failed" messages when I (finally) got to the point where I could download maps to my Edge.

This solution may not apply to you, as such a useless error message is probably a catch-all for several different error conditions.  But in my case...

I found the Garmin Express logs in C:\ProgramData\Garmin\Logs\Express on my Windows 10 machine, and could see evidence that the application was looking for 6GB of space -- but only 4GB was available.  This was driving me crazy, because I had deleted ALL the maps on my Edge 1030 Plus while trying to resolve this issue, and Windows clearly indicated that ~28GB was available on the device.

I then realized that Garmin Express may be trying to download the map as a temporary file to my local PC... and sure enough, my local PC only had 4GB available.  Freeing up some space allowed the update to proceed without error.

The Bug Report for Garmin is the vague error message in Express.  They need to categorize device update failures into more precise conditions, and provide useful information in the error message.  Doing so would save themselves support calls and unhappy customers.

  • A different solution, but commenting here because this thread is still open for comments. 

    For me the download went fast (~10% in ~20 seconds) then stalled. Over the next hour no more data was transferred, so of course the average transfer rate dropped slowly from 26 GB/s to  < 1 GB /s and the projected time to completion grew from 1 hour to 15.  But in reality it's just completely stalled, wifi activity is zero.

    The solution was just to kill it and try again:

    • attempt 1, stalled at 10%
    • attempt 2, stalled at 20%
    • attempt 3, stalled at 1%
    • attempt 4, completed in ~ 3 minutes

    That suggests that it's not a network issue, or a  bandwidth issue, or a disc space issue. It's a bug, something minor goes wrong like 1 packet lost or corrupted and the update process can't recover and just waits endlessly.

    NB: To kill Garmin Express you have to kill the app & kill another garmin process from Task manager. If you don't kill th eother process then Garmin Express won't restart.