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

Page 2 of 2 FirstFirst 12

  1. Posts : 17,832
    Windows 10
       #11

    pepanee said:
    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.
    And I'll still be hunched over my keyboard, at about 140 years old, with rigor mortis settin in, waitin for Build 17063 to install!!!
      My Computer


  2. Posts : 35
    win10 pro x64 ver. 1709 bld. 17046.1000
       #12

    The Borg will be landing then. Don't ask me how i know, I'd have to assimilate you early. Resistance is futile.
    Windows Will No Longer Be Supported After 12/31/2107 At 3:59:58 PM?-borg.jpg
      My Computer


  3. Posts : 809
    Win10
       #13

    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.
    NTFS uses 64 bits for the timestamp, so it will overflow somewhere in September of 30828.

    Based on Design of the FAT file system - Wikipedia it looks like the modified time only has a 2-second granularity, so it would stop at 11:59:58. The creation time has 10ms resolution so you should be able to get to 11:59:59 if you try to modify that.
      My Computer


  4. KCR
    Posts : 347
    Windows 10 Home, 64-bit, Version 21H2 (OS Build 19044.1806)
       #14

    Edwin said:
    And I'll still be hunched over my keyboard, at about 140 years old, with rigor mortis settin in, waitin for Build 17063 to install!!!
    Lol, it could be worse...

    Windows Will No Longer Be Supported After 12/31/2107 At 3:59:58 PM?-kcr-still-reading-2.jpg

    KCR
      My Computers


  5. Posts : 25,076
    10 Home x64 (21H2) (10 Pro on 2nd pc)
       #15

    PolarNettles said:
    NTFS uses 64 bits for the timestamp, so it will overflow somewhere in September of 30828.
    No, it's earlier than that because it starts counting in 100ns intervals from January 1, 1601 (UTC). See my post #10.
      My Computers


  6. Posts : 809
    Win10
       #16

    Bree said:
    No, it's earlier than that because it starts counting in 100ns intervals from January 1, 1601 (UTC). See my post #10.
    I was going by the analysis in Interpretation of NTFS Timestamps | Forensic Focus - Articles which shows the maximum FILETIME to be 0x7FFF FFFF FFFF FFFF.

    This corresponds to:

    2^63 ticks * 100ns/tick * 1s/1E9ns * 1hr/3600s * 1day/24hr * 1yr/365.25days = ~29227 years

    1601 + 29217 = 30828

    Edit: Adjusting calculation to take into account leap years.
      My Computer


  7. Posts : 25,076
    10 Home x64 (21H2) (10 Pro on 2nd pc)
       #17

    PolarNettles said:
    I see, so why the 2107 cut-off then? It's a puzzle...

    Edit: Oh, I see they covered that too.
    Windows Explorer GUI:
    Timestamp range:
    1980-01-01 00:00:00 2107-12-31 23:59:57
    2107-12-31 23:59:58 and :59 are shown as (blank)
    Remaining timestamps outside the range are translated as (blank) .
    It must be noted that the timestamp range only refers to the times shown in the GUI list. When the timestamp of an individual file is examined in the file property dialog (see below), the coverage appears to be full range of years.
      My Computers


  8. Posts : 1,678
    Windows 10 Pro for the Bro
    Thread Starter
       #18

    All this info is so complicated.. all I understood was what KCR said: I'm gonna be a skeleton trying to study my math homework from that book
    LOL
      My Computer


  9. Posts : 30
    windows 10
       #19

    You people have way too much free time on your hands:)
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 22:54.
Find Us




Windows 10 Forums