Since build numbers go up very rapidly these days, it could even happen that 10200 will be reached naturally as one of impressive of winmain builds but the final RTM build number definitely is much higher and, again, must be a multiple 16 and 100. So 10400 or 10800 are most likely candidates for RTM
MS would refrain from jumping too many numbers, the binary string of builds has 14 bits for the build number, 2^14=16384, i.e. build numbers could only reach 16383. Naturally, they could change the format and have 15 bits for the build number, but then it would cause compatible problems with current softwares that only read 14 bits as the build number, so it would be another major pain to make this transition.
I'm just one of those guys who likes to see the build number grow and believe it is getting better with each build and ofcourse that is an under statement because they always screwed up in the end !! I hope this time it would be different
Hope not. I did activate 10074 with my windows 8 upgrade key (retail). I had to make a phone call but it worked. Will make running licensed VM a bore if I'm stuck on VirtualBox with 1 virtual CPU until the end of time...
That jaw line though! lmao me and Paul should be virtual betting on this lel! but in all seriousness there is gonna be no final build number... WHY? because Windows 10 will be constantly going through build updates even after RTM, since there will be no Windows 11/12 etc... Lets just hope that the updates/upgrades that microsoft pushes after RTM wont come borked like they do to windows 7 forcing people uninstall KB updates due to blue screening lol
What's the actual point of this thread? Is this supposed to be a huge, exclusive news item or something? Seems to me it's nothing more than a guy who took a couple obvious build numbers that could be RTM, using a method Microsoft has used for years and somehow it's 20 pages long like it's this really important thing. 20 pages to guess a build number? If it actually ends up being one of those builds then what happens? I just don't see the real point of this thread. Seems the OP is making it out to be more important than it really is IMHO.
negative! There will be a defined RTM build in any way. Shortly after, perhaps week by week, updates will alter these builds but primarily there is a new W10 RTM start by design, period
Sure, there is nothing dramatic about the term RTM. it's simply a stage where the build has passed the sign-off test procedures, and passed to the manufacturers/OEM's to start making money. It's real fun to read the various threads on people guessing and speculating on the win10 upgrade, anyway: - Activation has nothing to do with MS accounts, "MS account" has not been mentioned a single time in the MS documents I read about the upgrade. - It won't do anything on the BIOS.
According to the trend now (the latest: 10143), there is only 1 month, 2 weeks and 4 days (48 days) left. Also, Microsoft usually finishes the RTM version several months before the releasing to MSDN subscription customers or the market, for example, Windows 8.1 RTM: 6.3.9600.16384.winblue_rtm.130821-1623 (Compiled on August 21st 2013 and it released on October 2013) Windows 8 RTM: 6.2.9200.16384.win8_rtm.120725-1247 (Compiled on July 25th 2012 and it released on October 2012) Windows 7 RTM: 6.1.7600.16385.win7_rtm.090713-1255 (Compiled on July 13th 2009 and it released on October 2009) Windows Vista RTM: 6.0.6000.16386.vista_rtm.061101-2205 (Compiled on November 1st 2006 and it released on January 2007) But Windows XP is a special example: 5.1.2600.0.xpclient.010817-1148 (Compiled on August 17th 2001 and released on August 24th 2001). So, MS may finish Windows 10 in a rush but even it rushes, I think the build number won't have a big gap between the current build. So, the build number should be 10160, and the full build information should be like this: 10.0.10160.16383.win10_rtm.150715-1245
10160 will be compiled in 3 july, knowing that every day there will be a new build (except Saturday and Sunday)
No comment on the main build no.(it's Paul's job ), as for the delta, the main build no. is a 14 bit binary string, so the delta always starts with the starting no. of a 15 bit string, i.e. 16384.