We have now discovered the cause of the problem below:
It is common for specific settings to end up in the following folder:
C:\Users\BosmanG\AppData\Roaming\EchoPAC\Export\Backup\resources\idunn
However, whether or not a check mark is checked is placed in the following location by the EchoPac plugin:
C:\Program Files\GE Healthcare\EchoPAC PC Plugin\User\target\resources\idunn\userdefs
Since we work with a VDI where a new (standard) VDI is offered to users every day, the settings in question under Program Files have disappeared again.
Perhaps we can prevent this by means of a copy action, but I think the real question is why the EchoPac plugin places these settings in this illogical location while other settings are placed in the correct location (AppData).
It would be worth a lot if this were improved in a future version.
Agree Guy that no user settings should be stored under program files and only under the user profile, it would affect other environments the same also not just VDI such as where a user has a roaming profile to work at multiple workstations.