Map update 2027.10 out

Waited two days and retried the second 3597. Map update 2027.1 now shows available and updated without errors. My PC and both 3597s have been successfully updated.
Mark

Two old nuvi 760's still working fine for me. Guess I'll give them a shot at the update. Even if it works they will take forever to update as they have antique USB. I'll just do it on my old desktop and let it run and see how it goes. Got a 6 week cross-country (and partly out of the country) camping trip coming up in a bit and would like to have new maps.

Been waiting for this. Thanks.

The download was fine but the transfer to the unit resulted in a few errors. This is because for whatever reason, my nuvi 3490 & it's installed 8GB microSD Card do not like to be ejected properly; properly ejecting from the System Tray from my Windows PC can result in the disk(s) just sitting unresponsive until they are manually unplugged/removed without a "safe to remove" message. This can result in leaving "not properly ejected" type errors. Running "Check Disk" fixes the issues and the transfer then proceeds error-free.

Well, after 6 days of trying, I still cannot update my 3597. Numerous attempts have failed.

My DS76 was not a problem. It updated in less than an hour.

@ajugo11

Same for me. Don't know why Garmin Express is acting like this.

First map update that won't fit on my Drive 52's internal storage... bummer. 7+gb is quite a bit and weirdly enough the update file for my 1390lmt is ~5gb.

I also have had problems ejecting a GPS (3597 & 855) with a μSD. I have found with my laptop if I eject the GPS first, I will immediately get the "safe to remove" message. I then attempt to eject the μSD card resulting with explored being unresponsive. If I wait long enough (10s of minutes), explorer becomes responsive and I can safely eject the μSD with out getting any errors.
Mark

Updated with no issues

Exact same symptoms with my 3490 (I believe my eTrex 32x also does this) but I've never waited long enough to see if Explorer regains consciousness. Thanks for the tip regarding this.

I seldom remove the mSD card from my device so I’m a bit puzzled why some people are talking about removing the mSD card (as part of an update process) and that being a potential issue. Some mention of a “safe to remove” message as well.

One way to eliminate any potential is once the GE update appears to be complete, exit GE and then shut the computer down. Be certain it is powered off, or fully into a standby state, then disconnect the GPS. Then you can remove the mSD card from the device should there be a need.

I'm not ejecting the mSD card for the sake of removing the card from the nuvi...it's staying in the nuvi. The ejection is from the Windows PC's USB connection.

To prevent file corruption, it's good practice to use the "Eject" command from the Windows Task Bar for any attached SD cards, external SSDs or HHDs (the nuvi is exactly that; two external USB disk drives). This safely closes open & in-use files on the external drive(s) and allows the OS to properly release the drive(s) from USB. Not doing so can result in open & in-use files not being closed properly which in turn can result in a corrupted file system on the drives, in which case one needs to run Check Disk to correct the file system errors.

This directly resulted in my update reporting 3-4 errors with the drive(s). It proceeded to the end but not trusting this, I afterwards ran Check Disk on the nuvi and it's mSD card, corrected the errors and re-ran the map update with zero errors.

In my case (as well as baumback's report above), when I try to properly eject the two nuvi drives (the nuvi root drive and the nuvi's internal mSD card) from the PC, the main nuvi will eject properly but the external mSD still needs to be ejected from the PC (you can not eject both at once). I've tried ejecting the mSD card first and then the nuvi drive last but the result is the same. Upon doing so, File Explorer will hang and become unresponsive. Garmin's USB implementation for devices has been very inconsistent for a long time now. I have experienced this behavior ONLY with Garmin devices. I have many external USB devices (SSDs, HDDs, etc) that will all eject properly.

Just for Hohos, I rebooted my PC and it worked. Install completed.

Since I do a lot of genealogy, I don't shutdown each night because of all the windows I usually have open.

Have tried shutting down/restarting the PC before, it takes just as long to shutdown/restart as to wait for "safe to eject" message. The PC won't shutdown or restart if it thinks the μSD is still busy.
Mark

That is weird. The update fit on my Drive 51 without a problem and without needing a MicroSD card.

…but when Windows shuts down or goes into standby you are assured it is done writing to the media.

As an FYI, what Windows 10 vs. Windows 11 does when writing to media can be different. Windows 11 uses a "Quick Removal" policy by default, minimizing risks. With Windows 10, for external storage the default changed to "Quick removal" (disabling write caching) in version 1809 and later, whereas earlier versions defaulted to "Better performance"

The 2597 is retired my drivesmart 66 updated with no problems,

What do you mean when you say the 2597 is “retired”. Were you unable to do an update on that device?

Will install later this week

It didn't power on did hard reboots, then screen kept flashing and express couldn.t connect.

Especially with so many in decent condition and at low prices on eBay.

Picked up the 66 at a decent price.

Ejecting any normal USB drive (USB stick, thumb drive, SD card, etc) from USB results in a "safe to remove" message in under ten seconds. The nuvi on the other hand causes a 17 minute Explorer hang (as below). Going by what "baumback" reports, ten minutes or more? As I previously mentioned, some Garmin devices are the only devices that do this. You don't even need to have accessed the nuvi drive nor it's mSD card. Simply plugging it in, then trying to eject it results in the same thing.

As a test just now, I plugged the nuvi along with it's mSD card into the PC. I did not access any files on either of them. I then ejected the nuvi drive from the PC which ejected immediately. I then tried to eject the mSD card (plugged into the nuvi) from the PC and Explorer has remained hung for 10 minutes now, no access to anything as far as Explorer goes. After 15 minutes, Explorer window goes gray with a "Not Responding" message. Trying to access Explorer results in the same hang. After 17 minutes, I finally have access again when I can eject the remaining mSD card from USB safely...maybe, as the system hangs once again after trying to do so.

Simply unplugging the device from the PC without a "safe to remove" message immediately frees the Explorer hang but then one can expect errors on the drives which will need to be scanned/repaired.

I really doubt this is how things are supposed to work. Sure I can turn off the PC but in my experience, Garmin does not know how to code some of their devices to eject gracefully (among other various things as well).

In the end, I have resorted to leaving the connected nuvi along with it's installed mSD card connected for a couple of minutes after doing anything with it to make sure that any open/used files are closed. At that point, simply unplug the thing from the PC (bypassing "safely eject") since clearly, trying to safely eject it seems to cause more issues then just unplugging it after a couple of minutes of inactivity.

…doesn’t happen to me, and as best I recall never has. In my case, with three devices, when the map update is complete (as indicated by GE) I simply close down GE and immediately disconnect the device. I do not receive any warnings from GE or Windows. That has been my process for many years of updates; basically three devices every update. During the update process File Explorer is not used to access the Garmin device or the installed card and that may be key since it is the use of File Explorer that generates the “safe to remove” message. Essentially I let GE handle the entire process. I would suspect that GE is capable of determining when its process is complete, and would warn if they weren’t when you close it down.

Took 4 tries but finally.

Without incident

...and it only took about 20 minutes.

Have two old nuvi 760s. It took 3.5 hours for the first one but it worked. The second one took just as long but still showed the older maps. Did it again and let it run while I was sleeping. Next morning it showed the new maps. Very old units but they work great.

Seems the latest version found some old long forgotten saved places and re-activated them...

thanks, will try it.

Updated my 2x 2689LMT's.. and POI's

Thanks