Not that Windows 7 has anything to do with Windows 10 (minus the free upgrade everyone got), but I also think you are forgetting about Windows 8 and Windows 8.1, which also has nothing to do with Windows 10 (except for the original free upgrade). Having said that, I still see no consistency to support 16299.x.
Peops RTM is already shipped to the OEM manufactory's don't you think ! It's an matter of time that we get ours hands on the version. Fact is that MS allready knows and we don't so pls what is the point of speculating on and on in this topic ! Just my 2 cents
Making your whole reply in all bold text with a size 6 text font, does not make your comment any more (or less) valid. I seriously doubt that 16299.2 will be RTM
Very well said. What's more there's a dedicated thread where those who feel the need to flood every thread with this needless guff and endless speculation/guesswork can post. It's largely irrelevant anyway - fall (autumn) update will be fall update! Every time there's a new upgrade due, threads are flooded with endless speculation and guesswork. Like we all know that shortly MDL will be over run with the masses who only ever turn up here to get new ISO's, don't read anything and demand that ppl upload stuff for them. At least last time a mod got involved and continually warned/threatened to ban ppl for posting requests, hopefully when final build hits, that might happen again.
Microsoft don't need to push RTM versions to OEM's as soon as they've signed off on a build. OEM's don't care when they get the updated code for the latest build of Windows 10. I work for an SMB managed service provider and every computer I've run up with Windows 10 preinstalled by OEM's are using 10586 or 14393. OEM's add an extra part to their OOBE experience to check Windows Update for the most recent build by having the Windows 10 Upgrade Advisor app pre-installed with the image. If it find something it asks to start the download while it finished OOBE or to update later. I usually just cancel the update, plug in a USB of the latest build and upgrade it that way... I suspect (with pure crystal ball speculation) that we'll get a re-compiled build of 16299.2 but with the number 16300.0 Tuesday or Wednesday after Microsoft have finished reviewing all their telemetry on the 16299.0 build they released to us. After being at Ignite all week they've got a bit of catching up to do...
I am so glad someone else finally said this. This is very well said and I completely agree. Overall, sounds about right.
While generally true for nearly every Windows release, that would still not support your belief, though. 16300 would still be a revision just as easily as 16299 could be or 16298 could have been. Nevertheless, your guess is just as good as any.
guys think i be staying on rs2 for a couple of months to things pan out rs3 is so buggy and not the same as rock solid 15063.632
15063 wasn't solid at first. You'll see that 16299 will receive cumulative updates for fix all the problems that it may have