The XT has a much larger drive than the 590 so the likelihood of any given cluster with a deleted file relic being over-written is smaller. But, yes, the sooner the better for file recovery, in general.

Like you, I tend to pull my archives every few months. But I had a real good few months and lost ...

I gave iBeesoft a try, danham . Same result. The zumo device doesn't register as a location that can be scanned. It may be a great finisher, but I can't start it. Thanks for looking.

Peobody , yup, I think drive letter is the root of the matter. There are a couple of third party tools for doing ...

I don't know how the storage space is allocated, but keep in mind that the number of Active Logs is limited, with the oldest file being deleted as a new one is started. Your old files may have simply been overwritten.

Table stakes for the question was already well past that.

My old files have ...

I've been fiddling unsuccessfully, trying to recover some of the numbered archive files in "internal storage / GPX / Archive" that got auto-deleted at the 20 file cap before I got around to grabbing them. Not for any critical reason, just a little OCD trying to complete the logs of my journeys.

Has ...

I had things working tolerably well, then a Garmin Explore app update on/about 20 Oct 24 crushed the last shred of usable route functionality. I cannot figure out what is doing on with routes and Garmin Explore. Any insights?

Background: I have no problems passing gpx files (waypoints, routes ...

Thanks for those ideas, lkraus .

I will rely on my ability to get to the archive periodically rather than to the unsaved tracks log too frequently. Either is a compromise. Player's choice.

There are options here and there to share things, like routes. And one of the methods is to "share" to SD ...

I'm revisiting the details here since I'm fiddling with track histories again.

Cruising through Garmin support I found this item which states the same "last 20" track archive approach jfheath et al provided. https://support.garmin.com/en-CA/?faq=1tDxR0iBK84W2kxh5nmEo7&productID=679804&searchQuery ...

Hopping in to flog a dead horse, since I was just in my device and looking at things.

Current.gpx used to have tracks in it in older devices (years back). Now, it does not. Apparently because those have been moved to CurrentTrackLog.gpx.

I am still confident Current.gpx behaves as it has for a ...

Just to further flatten the cat, I was very hopeful I'd find 10-15 or even 1-9 under .System, but it seems whatever made them vanish (me or the system) outside .System was mirrored inside. Stand-alone weirdness that Drivelog17.gpx was NOT there but Archive/17.gpx still lives; that was definitely not ...

Current.gpx for a LONG time has been a dump of what's in device memory. It is the net of all imports, on device edits & deletes, etc. Not the last transfer, like Temp.gpx

The device spits it out but never reads from it. If you delete it, next power off the device will spit out a new one.