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

Garmin Express 6.12.0.0 does not recognize SD card

Garmin Express 6.12.0.0 / GPS is running the latest software iteration 5.90 / Windows 10

I've had this wonderful Garmin DriveAssist 50LMT for 3 years now and it's high time I finally get this SD card issue resolved.

I've tried multiple micro SD cards, the most recent being a class 10 Samsung 64G (link to specs here: https://amzn.to/2XXMccK )

I've formatted it multiple times to exFat (that and NTFS are the only options to format to on Windows 10)

Every time I plug the GPS in and connect to Garmin Express to install any map updates it says that the internal memory is 96% full and that there is no more room and to insert an SD card. This is understandably frustrating considering there IS an SD card installed (which my GPS itself seems to be fine with - it asked once the first time I inserted it to format it to FAT32.)

So, any ideas?

0 etrenbeath over 5 years ago

I have a 64GB card in the camera slot that has been working fine since the beginning, and the 64GB card I've been trying to use in the other slot.

0 SUSSAMB over 5 years ago

See post #9 above, what's the result?

0 etrenbeath over 5 years ago

I'm not sure 64Gb cards can be formatted FAT32 without some external program, so are you sure the card is FAT32? Click on Properties via Windows Explorer and in the General tab see what is shown against File System.

If that confirms the card is FAT32 check it's not write protected.

Now remove the card and run Express, only inserting the card when Express asks you to do so and see if that helps.

It's definitely FAT23 and it's not write-protected. It doesn't ask for the SD card to be installed per se, just that it needs one. But either way, it doesn't recognize it as additional memory whether it's already inserted in the GPS before I plug it in, or if I insert the SD card after it's plugged in.

0 SUSSAMB over 5 years ago

That's very strange then, the only other thing I can suggest trying is to master reset the device but I'm not hopeful.