Page 1 of 1
Strange dates far in the future
Posted: 14 Oct 2023 16:06
by RalphM
I suddenly saw strange date stamps on folders in XY (way in the future), so I went and timestamped these folders with a CFA that makes the created date identical to the modified but they still display as wrong.
The same folders show proper dates in Win Explorer.
PicPick_899.jpg
The files reside on a Synology NAS but I never had any troubles so far.
Re: Strange dates far in the future
Posted: 14 Oct 2023 16:10
by admin
Great thread title!
So the error is only in the display, not in the stamping?
Re: Strange dates far in the future
Posted: 15 Oct 2023 03:51
by RalphM
It would appear that Win Explorer does some trickery in its display.
If I check the properties of one of these folders in both WE and XY (same shell dialog I guess) they both show the same wrong created date in 2421 but WE seems to adapt the display of the created column to match modified if it is a "silly" date.
Re: Strange dates far in the future
Posted: 15 Oct 2023 11:09
by admin
Totally clueless. Dates are simple. They are just numbers. Can't see how they could get silly, can't see any pattern in your screenshot, never heard of anything like that.

Re: Strange dates far in the future
Posted: 15 Oct 2023 15:06
by RalphM
And yet here they are.
Maybe another screenshot helps?
PicPick_900.jpg
Re: Strange dates far in the future
Posted: 15 Oct 2023 17:01
by admin
Just shows what you already said.
So there is no way to timestamp these dates back to now / to any other date?
Re: Strange dates far in the future
Posted: 16 Oct 2023 00:47
by RalphM
Not with the usual tools as far as tested.
I found some old posts that something similar happened a few years back on Synology NAS's so the problem may lay there.
Still confused how WE manages to display something different though.
Will keep you posted.
Re: Strange dates far in the future
Posted: 16 Oct 2023 14:56
by admin
I added a way to retrieve the raw 8 byte value of the each filedate. Next beta:
Code: Select all
echo filetime(,, "hex"); //modified date of current file as 8 byte little endian hex, eg: 01DA002E35164B00
Maybe it sheds some light on the mystery.