2025.20 question (img file's creation date)

Would someone who knows how to find the folder/file check the created on date for me please? Thanks.

I checked two of my devices: an ancient nuvi 750 with the new 2025.20 map, and a nuvi 3597 with 2025.20.

The 750
I see on the 750 itself, no gmapprom.img file. I do see a leftover tiny (1KB) gmapprom.unl file which I think I can delete but just in case, I'm leaving it there since it takes up essentially no space. The 750 does have a gmapsupp.img file with an Oct 2024 date.

On the 750's SD card, the 2025.20 map file is called gmapsup1.img and it has the correct October 2024 file date, so it appears the City Navigator NA 2025.20 map is split between the 750 and its SD card.

The 3597
There are no gmapprom files on the 3597 itself, but on the 3597's SD card, the 2025.20 map is gmapprom.img with the correct Oct 2024 date.

I hope this helps.

Thanks for checking it out.

I'm using a DriveSmart 61 for my test I would expect the supp file if my map was split but it was not, it all should still fit on the main drive. I have 'successfully' downloaded 2025.2 to my DS61, twice, yet still the only gmapprom file I can find is the one from March, 2025.1.

Very odd, the unit tells me it has the newer map, 2025.2, there is nothing I'm aware of to confirm this, as in anything new around me that wasn't there last time.

I also downloaded 2025.2 to the computer but cannot find a gmapprom file on my computer, what filename do the img the programs, Basecamp, map install, mapsource use? I have all 3 of those programs on my PC and they all now list 2025.2 as a map I can use.

Is your computer set up to show hidden files and extensions? If yes click on system and you should see gmapprom file . http://www.poi-factory.com/node/41141 and http://www.poi-factory.com/node/39185

Yes, I always have view all files checked, and as mentioned, I do see that file in the .system folder, but it was created on March 13, 2024,the date I installed 2025.10, not Oct. 17, 2024 the date I installed 2025.20 like it should have been.

That's the point of the question, the correct file 'appears' to be the previous version, yet the unit itself when I go to "My Maps" tells me 2025.20 isinstalled, it doesn't make sense. That's why I wondered if anyone else was seeing the same thing, maybe Garmin changed something 'we' are unaware of, but Craig sees what I expected to see on my unit.

All of mine show the install date of 10-10-24 the date I installed them. You got a mind puzzler there. May want to try a new download.

I've done that too, 3 times now, still has the img file as being from March, BUT the unit tells me 2025.20 is installed.

I have an microSD card in the DS61, so out of curiosity I used MapSource to download all of the US and Canada, that gave me a gmapsupp file dated today, on the card, but still, the main unit files are from March. MapSource offered me 2025.20 to download, very very odd.

Soberbyker, I went down to the car and brought my DriveLuxe51 up to the computer. It has no SD Card as the DL51 comes with 14.2GB so the entire 2025.20 map still fits internally to the device.

In my GPS, looking in the .system folder, I see the full gmapprom.img file with my 10/12/24 installation date for 2025.20 and with a size of 3.35GB, 3,604,480,000 bytes. In the file Properties besides my 10/12/24 installation date, I see a Created date of Aug 14, 2024.

For what it's worth, I updated to 2024.20 via USB cable, not Wi-fi. I wonder if you updated via Wi-fi, and if so, would that have an effect? It certainly doesn't seem like it should.

I am very suspicious of your GPS showing 2025.20. To me, that makes me think you do have 2025.20 installed and I wonder if it could be hiding somewhere else. I do think that if your gmapprom.img file is from 2024.10, then Garmin would have possibly named the 2025.20 map gmapsupp.img or gmapsup1.img. If you're using a PC, you should be able to go to your device's .system folder, then do a search for gmap which will show all the folder's files starting gmap****.*** Look for a large img file with the date you last installed 2025.20. Also, installed, search the entire SD card for gmap. Maybe also check the other folders in the GPS for it.

Here's another test you can try. In your .system folder where you have the gmapprom.img file from earlier this year, rename the file gmapprom.img.old, then disconnect, reboot the GPS once or twice, then look to myMaps to see what map is showing. If you still see 2025.20, then it's not the 2025.10 map because you disabled it and you do have 2025.20 somewhere in the GPS or SD Card. I don't think this would have the potential to brick your GPS, but maybe you should not try this.

Good luck.

In re-reading what you wrote that I bolded above, it seems possible that in doing the updates to 2025.20, Garmin Express somehow forgot to delete the 2025.10 gmapprom, so it installed 2025.20 as a gmapsupp.img.

Did you install 2025.10 earlier this year, by a normal method, either using Garmin Express or by Wi-fi if you device can do that? You didn't use the Clone method or anything like that, right?

It'd also be interesting to look for gmapprom and gmapsupp with .unl and .gma to see the file properties with the Oct file dates and earlier dates.

I just offer this in case it kicks someone else into thinking what could be happening.

I have a Garmin USB cable I'm using. Never tried wifi.

FWIW the microSD card was empty prior to today, so it wasn't involved in yesterday's troubleshooting. So it's not likely that the gmapprom was renamed to supp, but what did happen was it showed as a supp after today using mapsource, BUT, the original gmapprom was still there and the date of March 2024 for the last update we had was still there, and all of it's associated files have the same March date.

The only thing with a today (or yesterday) timestamp is the gmapsupp from this morning.

Everything that has been suggested here by all was tried, except renaming the file .old. I've done what I am trying to do countless times before and this is the first time the img file didn't have the new date associated with it and the other files created. I even went back and forth with mass storage and MTP modes a few times, rebooting each time, still no change except the noted attempt on the microSD card.