You are currently at least the third one reporting this misbehavior. In my case it was cleared by another update but I went from 2.0.1.11 to 2.0.2.43 first. The update from 2.0.2.43 to 2.0.2.45 fixed it. I have not tried directly from 2.0.1.11 to 2.0.2.45.

As V10lator say, try version --dup again. You have nothing to lose at this stage, the damage has already been done..