Garmin-Matthew has closed the thread below, saying the issue was resolved by 4.24. It wasn't.
See images.
Given the recent track record of poor software releases; in future, it may be better to ask your customers if the latest version has resolved an issue rather than deciding it has.