Trying to replace an executable I put yesterday with today's fix. The version of yesterday's build was 1.2.29, today's is 1.2.30. Going through three machines to get there (why did the chicken cross the road? - for security reasons), I finally get the exe in place in one of the customer's servers. Now the final step, copy it through their internal network to the other server, where I need it to be (but where FTP is streng verbotten). I see by the date on the file that it's been replaced, although the time on my original is 9:47 and on the copy there it's 8:50 (one timezone off, that's OK, but why the three minutes? I guess FTP didn't preserve the time).

I run it, and it has the same error as yesterday. I look at its log, and it says 1.2.29. Huh? Rightclick, properties, version 1.2.29.

Rename the file, copy again. Still 1.2.29. Repeat three more times, same every time.

Eventually build the exe under a different name, copy that all the way through. That works.

Is there any particular reason why would the OS just reinstate the old version out of the blue, several times in a row? Is there some hidden checkbox where to turn this maddening feature off?