Terribly sorry about this.
We have tried to fix this bug in V1.05 and it should hopefully not happen anymore.
