Hello,
It is unfortunately a known issue that came up here:
It was also confirmed to us in a support ticket.
To summarize, It looks like some previous update introduced this "feature" (no real idea about which update introduced it) and was fixed in newer builds. So being affected depends if you skipped by chance that particular update.
It also seems that no warning about this _very_ annoying issue was emitted in any changelogs or information bulletin afterward.
Maybe there will be a note in the upcoming STABLE BETA release ?
Kind regards.
Sébastien Riccio
System & Network Admin
https://swisscenter.com