I think what needs to be confirmed is that the update process is actually taking what is seen in the UI in 1.6.6 (one synonym elevated to preferred/default) and converting it to real data in later versions which fail validation. By removing the data causing the problem we clean up what appears in the later versions… but we don’t solve the underlying problem (which is that they shouldn’t be elevated to default/preferred automatically).