Basecamp update 4.7.2 caused loss of City Navigator Map?

Former Member over 5 years ago

So I mistakenly clicked on update when I opened Basecamp to program a ride for this afternoon for my Zumo. I have City Nav 2021_10 installed and was working fine within Basecamp and in my Zumo last weekend.

Now when I start BC, it only shows the Global Map. I clicked on Maps > Manage Map Products, and in the first tab, it only shows the Global Map installed in C Drive. On the second tab, it shows 3 map products not installed. It only shows long numeric/alpha codes, so I have no clue what they are.

So I try to click Add, it's asking for codes I don't have. I have free map updates for life between my Zumo and Nuvi, and this updated maps have been installed through Garmin Express perfectly all these years.

Anyway, when that failed, I tried the Import function, to direct BC to the location in the D Drive for the Map. As an FYI, I have to use D Drive as C Drive is a small Solid State Drive. Again, this has been working fine all these years.

When I try to use the Import, it's looking for either a a *.ucx or *.gma which it is not finding in the directory no matter how deep I drill.

Can I get some tips on how to solve this nightmare. It's always frustrating when updates screw stuff up like this, at the worse possible time.

0 SUSSAMB over 5 years ago

Simplest way is just use Express and download the map again

0 Former Member over 5 years ago in reply to SUSSAMB

I did - three times. The map files is there clear as day

I attached the Zumo, and had the Map reinstalled to the D:\ProgramData\Garmin\Maps. It went very fast so there must be an archive located somewhere? Towards the end it says it's Activating Maps. All solid there.

The short cut is in C:\ProgramData\Garmin\Maps that directs BC to the D Drive - D:\ProgramData\Garmin\Maps

City_Navigator_North_America_NT_2021_10.gmap

The issue is BC is not seeing it, and I'm trying to figure out how to get BC to pick it up. Again for all these years and countless map updates, everything was fine. Suddenly there is a BC update and everything goes hay ware.

I even went as far as to download and run the GMTK program you recommended elsewhere, and as a test, had GMTK take the D drive install and copy it to C:\ProgramData\Garmin\Maps. Only then it would work.

However, if I close BC, and rename the map folder on C drive, it doesn't work again.

So, then I suspected that BC must have corrupted the shortcut that has been working fine all these year when I noticed that the file date was now 6/17/20. Sure enough, I made a new shortcut and all is well.

Why would a BC update corrupt a shortcut? How irritating!

Sure would be nice if Garmin got out of the stone age and allowed different drives natively without requiring bandaids and work arounds. This is kind of absurd that there isn't a simple function within BC to point to the install location on a different drive or network drive.

Hopefully this will help the next guy to avoid wasting 1/2 day to figure out this nonsense.