Windows Will No Longer Be Supported After 12/31/2107 At 3:59:58 PM?

So I was bored, and decided to see how far into the future I can set the metadata for a file's "Date Modified" detail.

So I played around by putting future dates into Filo, to modify a file's Date Modified detail.
I put in the date as the year 3000, and the "Date modified" detail just disappeared! hah? (refer to the 1st picture)

I was now up for a challenge. So I got curious to when exactly the date would disappear. I put in random year numbers to narrow down where that cut-off point is. I was able to narrow it down to the year 2107 (not last year 2017), but twenty-one oh seven, 2107. I tried different months and days, and apparently it's on the last day of that year. But then I also played around with the Time on that day... and narrowed it down to 3:59:58 PM. If I set the time to 3:59:59 PM, that's when the Date Modified detail disappears!!! HUH? Why 58 seconds, but not 59 seconds??? (Apparently that's the cut-off point.) That's the most puzzling part of this lame math problem though, 58 not 59 seconds.

That date (year) and that specific time must mean something.

So is that our last day here?

Since no one reading this will be around then, it does seem to be a good idea.

Josey Wales: Hah. You got me on that one. But what about my children (when I find a woman to reproduce with)...? Too bad for them, right?
PolarNettles: Wow cool! I tried searching for that date but didn't find that result. Thanks for that link. I remember hearing about that 2037 bug or whatever back then, but noticed that this bug was fixed. On the site, they say FAT Filesystems, they gotta update to NTFS also.. or I just missed seeing that. And yes: "4PM Pacific time is 0:00 UTC".
BUT wait! What about that last second of 2107!!! The last second doesn't exist! I guess Microsoft added that as a little Easter Egg or whatever. HAH they got me good on that one.
Edwin: I've seen weird and scary YouTube videos that predict the future... I honestly wouldn't want to stick around for that long. :)

pepanee said:

Josey Wales: Hah. You got me on that one. But what about my children (when I find a woman to reproduce with)...? Too bad for them, right?
PolarNettles: Wow cool! I tried searching for that date but didn't find that result. Thanks for that link. I remember hearing about that 2037 bug or whatever back then, but noticed that this bug was fixed. On the site, they say FAT Filesystems, they gotta update to NTFS also.. or I just missed seeing that. And yes: "4PM Pacific time is 0:00 UTC".
BUT wait! What about that last second of 2107!!! The last second doesn't exist! I guess Microsoft added that as a little Easter Egg or whatever. HAH they got me good on that one.
Edwin: I've seen weird and scary YouTube videos that predict the future... I honestly wouldn't want to stick around for that long. :)

You do realize that 2017 is 89 years from now so unless you are about 4 , your offspring as well as my Daughter will not be here.

Josey Wales said:

You do realize that 2017 is 89 years from now so unless you are about 4 , your offspring as well as my Daughter will not be here.

What about my grandchildren =P

pepanee said:

What about my grandchildren =P

They will be smart enough not to need windows or a PC by then.

Josey Wales said:

They will be smart enough not to need windows or a PC by then.

So the Android operating system will probably take over... and the Space Androids will claim that company's ownership. HAH. The future is gonna be a strange place.

pepanee said:

BUT wait! What about that last second of 2107!!! The last second doesn't exist!

It's just 64-bit binary arithmetic....

FILETIME structure
Contains a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601 (UTC).

FILETIME structure (Windows)

Ohh, what's really going to bake your noodle later on is, why does the world start in January 1601?


SPOILER ALERT the answer is here