You were right! Thanks.MarkO wrote: Mon Jun 23, 2025 1:59 am I was getting a similar thing at one stage. I would update to the current database, but the next time I powered the aircraft, it would revert to the old database. I spoke to my service centre, and the fix was to take out the flightstream card and remove all files from it. Since I have done this each time I update, it has gone very smoothly, and I have no issues.
1. Create a new SD card using Garmin Database Manager.
2. Remove the Flight Stream card and replace it with the SD from Garmin Database Manager.
3. Apply power, and while the SC card is updating the avionics, delete all files from the Flight Stream card.
4. Turn off the power and replace the SD card with the Flight Stream card.
5. Repower aircraft.
I don't bother trying database concierge any more using wifi as it is more trouble than it is worth.
At first I did not think it would help me a lot because when I inserted the Flight Stream SD card in my latest gen MacBook’s SD slot it would not appear, as if nothing was inserted. Since I had hooked a GPU I had time to make several attempts after deleting all databases and noticed that old databases were starting to appear once I had inserted the FlightStream card back in the plane.
The flightstream SD card apparently contained databases valid at the time of delivery of the aircraft. I tried to read it again on my Mac but this time I used a recent Sandisk external USB-C SD card reader. It then worked and I could confirm that it contained many database files. I formatted the card.
After once again erasing all databases from the plane, loading from a clean JDM loaded card and then I inserting the freshly reformatted FlightStream card then everything worked and survived several avionics reboots. I even managed to load the next nav data cycle that stayed nicely in the standby database.
Crossing fingers but it looks like this is finally sorted out. Thanks again for your input.
