Windows 10: 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?













:)

 

Upgrade From Win10 10240 to Win10 14393 Failed

I have repeatedly encountered a failures in trying to upgrade Win 10 from 10240 version to the current 14393 version.

1. I used the Windows10Upgrade28084.exe program - failed.

2. I used the MediaCreationTool to download the iso and create a bootable DVD for upgrade - failed.

3. Created virtual drive for the iso to upgrade - failed.

The normal Windows Update function appears to work properly - I get windows and other updates on the usual time basis.

The relevant files for diagnosing what went wrong seem to be:

A. The $WINDOWS.~BT\Sources\Panther\setupact.log

B. The $WINDOWS.~BT\Sources\Panther\setuperr.log

C. There are also small files with these same names in the $WINDOWS.~WS\Sources\Panther folder (i.e., another setupact.log and setuperr.log)

================================================

Here is the file $WINDOWS.~BT\Sources\Panther\setupact.log:

2016-08-31 12:59:32, Info SP CSetupPlatform::Initialize: Setup log starts:

2016-08-31 12:59:32, Info SP Host system information:

VM: NO

Firmware type: UEFI

Manufacturer: HP

Model : 860-180st

BIOS name : A0.14

BIOS version : A0.14

BIOS release date : 20160606000000.000000+000

Total memory : 34359738368

Number of physical CPUs : 1

Number of logical CPUs : 8

Processor manufacturer : GenuineIntel

Processor name : Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz

Processor caption : Intel64 Family 6 Model 94 Stepping 3

Processor architecture : x64

Processor clock : 3408

2016-08-31 12:59:32, Info SPVerifyFootprint: Starting verification of footprint section Footprint.Basic

2016-08-31 12:59:32, Info SPVerifyFootprint: Could not find footprint file C:\$Windows.~WS\Sources\reagent.admx

2016-08-31 12:59:32, Info SPVerifyFootprint: The requested footprint is not present

2016-08-31 12:59:32, Warning SPGetFootprintCapabilities: Footprint [Footprint.Basic] incomplete; the platform capability will not be available

2016-08-31 12:59:32, Info SPGenerateCopyListFromConfigFile: Didn't find file list in C:\$Windows.~WS\Sources\setupplatform.cfg, section Footprint.Servicing.x86

2016-08-31 12:59:32, Info SPVerifyFootprint: Starting verification of footprint section Footprint.Servicing

2016-08-31 12:59:32, Info SPVerifyFootprint: Could not find footprint file C:\$Windows.~WS\Sources\compatprovider.dll

2016-08-31 12:59:32, Info SPVerifyFootprint: The requested footprint is not present

2016-08-31 12:59:32, Warning SPGetFootprintCapabilities: Footprint [Footprint.Servicing] incomplete; the platform capability will not be available

2016-08-31 12:59:32, Info SPGenerateCopyListFromConfigFile: Didn't find file list in C:\$Windows.~WS\Sources\setupplatform.cfg, section Footprint.ICB.x86

2016-08-31 12:59:32, Info SPVerifyFootprint: Starting verification of footprint section Footprint.ICB

2016-08-31 12:59:32, Info SPVerifyFootprint: Could not find footprint file C:\$Windows.~WS\Sources\cmi2migxml.dll

2016-08-31 12:59:32, Info SPVerifyFootprint: The requested footprint is not present

2016-08-31 12:59:32, Warning SPGetFootprintCapabilities: Footprint [Footprint.ICB] incomplete; the platform capability will not be available

2016-08-31 12:59:32, Info SPGenerateCopyListFromConfigFile: Didn't find file list in C:\$Windows.~WS\Sources\setupplatform.cfg, section Footprint.Migration.x86

2016-08-31 12:59:32, Info SPVerifyFootprint: Starting verification of footprint section Footprint.Migration

2016-08-31 12:59:32, Info SPVerifyFootprint: Could not find footprint file C:\$Windows.~WS\Sources\cmi2migxml.dll

2016-08-31 12:59:32, Info SPVerifyFootprint: The requested footprint is not present

2016-08-31 12:59:32, Warning SPGetFootprintCapabilities: Footprint [Footprint.Migration] incomplete; the platform capability will not be available

2016-08-31 12:59:32, Info Initializing diagnostics helper; data file = (NULL)

2016-08-31 12:59:32, Info No existing diagnostics data

2016-08-31 12:59:32, Info Key CollectTrace is not available.

2016-08-31 12:59:32, Warning SP CSetupPlatform::Initialize: Failed to initialize tracing

2016-08-31 12:59:32, Info There is already a running setup user mode etw session!

2016-08-31 12:59:32, Info VDS available

2016-08-31 12:59:32, Info Key CollectTrace is not available.

2016-08-31 12:59:32, Info SP Attempting to resurrect a new system from C:\$Windows.~BT\Sources

2016-08-31 12:59:32, Error SP CSetupPlatform::ResurrectNewSystem: Cannot resurrect new system.: Win32Exception: \\?\C:\$Windows.~BT\Sources\NewSystem.dat: The system cannot find the file specified. [0x00000002] __thiscall UnBCL::FileStream::FileStream(const
class UnBCL::String *,enum UnBCL::FileMode,enum UnBCL::FileAccess,enum UnBCL::FileShare,unsigned long)[gle=0x00000002]

2016-08-31 12:59:32, Info SP SetupPlatform opted-in to sqm

2016-08-31 12:59:32, Info Set Watson bucketing parameter #0 to 7

2016-08-31 12:59:32, Info Set Watson bucketing parameter #1 to 8

2016-08-31 12:59:32, Info Set Watson bucketing parameter #4 to 0x0

2016-08-31 12:59:32, Info Set Watson bucketing parameter #5 to 0xA001A

2016-08-31 12:59:32, Info Set Watson bucketing parameter #3 to 0

2016-08-31 12:59:32, Info Set Watson bucketing parameter #6 to 10240

2016-08-31 12:59:32, Info Set Watson bucketing parameter #7 to th1

2016-08-31 12:59:32, Info SP SetupPlatform opted-in to sqm

2016-08-31 12:59:32, Info SP Suspending and releasing setup platform

2016-08-31 12:59:33, Info Copy telemetry file: source folder: C:\$Windows.~WS\Sources\Panther, destination folder: C:\ProgramData\Microsoft\Diagnosis\ETLLogs

2016-08-31 12:59:33, Info Copy etl files: source: C:\$Windows.~WS\Sources\Panther\DlTel-Merge.etl, destination: C:\ProgramData\Microsoft\Diagnosis\ETLLogs\DlTel-Merge.etl

2016-08-31 12:59:33, Info Diagtrack service is running

2016-08-31 12:59:33, Info Restart Diagtrack service successfully

2016-08-31 12:59:33, Info SP Closing Panther Logging

=========================

Here is the file $WINDOWS.~BT\Sources\Panther\setuperr.log:

2016-08-31 12:59:32, Error SP CSetupPlatform::ResurrectNewSystem: Cannot resurrect new system.: Win32Exception: \\?\C:\$Windows.~BT\Sources\NewSystem.dat: The system cannot find the file specified. [0x00000002] __thiscall UnBCL::FileStream::FileStream(const
class UnBCL::String *,enum UnBCL::FileMode,enum UnBCL::FileAccess,enum UnBCL::FileShare,unsigned long)[gle=0x00000002]

=========================================================

The WIN10 10240 is the original OS for this system as factory installed by HP.

I appreciate someone stating what went wrong (and keeps going wrong with various approaches to upgrade) and how do I fix it ?

Thanks.

 

N97 : WAP problem.

hey just hope you get it sorted, and illinjah brought a very good point, you may not be able to acess a lot of stuff just by using wap on your phone, you might have to get the full interntet from your provider for a full n97 experience.
Message Edited by radical24 on 31-Jul-2009 12:58 PM
Message Edited by radical24 on 31-Jul-2009 12:58 PM

 

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

 

Time formatting and storage bugs - Wikipedia

4PM Pacific time is 0:00 UTC. I guess there may be some leap second math there as well.

 

Huh!!! I plan on hangin around for another 89 years!!! *Wink

 

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. *Smile

 

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.*Wink

 

What about my grandchildren =P

 

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.

 

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

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

 

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!!! *Wink

 

The Borg will be landing then. Don't ask me how i know, I'd have to assimilate you early. Resistance is futile.

 

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.