If this 10176 th1 build gets approved it will likely be assigned 10400 This is just speculation, but every MSOS I can remember upped their ver to a multiple of 400. I think FaiKee was right on with his guess for the OP. Of course, since they're doing insider builds, this RTM won't exactly be a final version like we're used to. Insider versions will hopefully be updated with kb fixes and improvements with the tradeoff that it may be buggy and hard to get good drivers.
It's always hard to get good drivers with a new os. I noticed however that when I installed 135 every single driver I needed on three different machines were provided in the iso itself..they even had lenovo, dell and asus names on some of them. That build ran great and none have run as well since. Of course that was a leaked build and not "official" and none of the official builds have any drivers at all so you have to go hunt for them. I wonder because of how they will roll this out if MS will include the drivers like they did in that build or if some machines may just die in the upgrade process.
I always had doubts about the 100 multiple rule, unlike the 16 multiple rule which is compulsory for QFE, the 100 multiple is just "traditional", although from Vista to Win8.1 all RTM's were 100 multiples, it doesn't mean MS couldn't decide to do away with it for win10.
Due to the current rangeset Code: <Range name="win10" minVersion="10.0.9868.*" maxVersion="10.0.65536.*" minSPVersion="0.0"/> it can be any build, and they have reserved a ton of builds for Windows 10 upgrades. That servicing/QFE numerology would apply only to LTSB which is likely to follow the ancient QFEs servicing schema. As most users are going to be on CB/CBB that's likely be updated via full builds as soon as updates are ready instead of patch Tuesdays, that makes the numerology and so this whole guessing thread, pointless
They very well could. If they did, now would be a good time since they're starting that Insider build stuff post-RTM.
So if we have 10500.0.150706-1800.th2_CLIENTENTERPRISE_VOL_x64fre_en-us.esd which is in th2, I think we can say that 10400 has just been confirmed since the th1 branch is for RTM and th2 is for everything after it. Likely this means that 101xx has just been signed of as RTM.
Tks @arseny, but I don't believe MS would replace patch Tue with "updating via full builds", at least ATM Insiders are still getting patch Tue's for their preview builds. Also, the main object of this thread is "Anticipating win10RTM", but when I started this thread there was very little to talk about, so I added the numbering thing to the title.
I agree with everything but the last line. I think they have decided that the RTM will be 400 but I don't think they have signed off on it quite yet.
True, around Nov 2012 it was known Build 9622 has been compiled for Project Windows 9, and most people was quite certain that WinBlue(not called win8.1 yet) would RTM on Build 9600.