Ah, thanks for this report. I experienced exactly the same issue a few days ago and had a chat with Garmin. They forwarded it to the developers. I also explained the issue in the gpsrchive forum (see the thread here) but it couldn't be reproduced by other users. In any case, please keep us informed.