The final build number consumers will update to on July 29th reads10240.16405.150725-1815.th1, and those keeping track will notice the delta number has increased from 16384. Those upgrading will actually download 10240.16384 alongside the day one patch handsomely titled KB3074683, and will be applied automatically during the upgrade so by the time the consumer lands on the desktop, they'll be running 10240.16405.
So 10240.16384 will be the final distribution build (ISO/ESD), and then further patches will be applied... I wonder if there will be 10240.16405 ISO made available that won't require the extra download.
Well, most of us already have KB3074683 and my delta number is 16393
Mr E got it backwards or maybe a copy error?
I stand corrected, the article does read that way, but it ends with Day One patch (wrong KB# in article??) will be applied automatically during the upgrade so by the time the consumer lands on the desktop, they'll be running 10240.16405
increased from
10240.16384 to
10240.16405.150725
I received KB3074683 three times - first failed, next two succeeded ????
According to Richard Hay on WinSuperSite, KB3074683 is a patch to fix what kb3074681 broke.
Patch for crashing on Windows 10 after update KB3074681 released to Insiders
Hi there
My latest is 10240.16384.150709-1700.th1...... From the last ESD file I used to create an ISO so it must be 99.99% RTM if your numbers are correct.
Note it was the GB PRO version -- not sure if US / GB builds have the same numbers -- they probably do but I don't know.
Cheers
jimbo
Mine, too.
Hello, can you please remind me from where can I see this last number (delta number?) of my build?
Thank you!
This is one place you can see it [HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionDiagnosticsDiagTrackSettingsRequests cfc.flights]
Hi there
Here's from another machine
How do I tell the build etc from this MESS. (image of the Registry key you suggested(.
Cheers
jimbo
Okay, thank you, and wow...what a path....
Here is mine then: