If you'd overwrote the old file with the one from this thread and then later ran the updater, it's possible that the updater set the modified date to the then-current time (or something similar) even though the file hadn't actually been changed. Windows in general is really bad about properly preserving file metadata, at least in ways that folks normally would think it should. In this case I'd be surprised if the updater is actually modifying the file in a traditional sense and instead is just creating / overwriting the existing, giving the potential for that timestamp weirdness.
__________________
|