Very good point you have there that's the way I feel about it and it is difficult situation as insider ! You know you are being used to spread the word and on the other side you want to believe that your feedback is used to make a better new OS. I already have decided that I will step out of the insider program after I have RTM in my hands too bad but this decision is based on how I feel and on those 2 points in you're statement you have made
Well, supposedly Insider is going to keep getting new builds. So, I don't know if we'll be able to use offline activation with them, but there might still be an advantage to the program.
Yeah thought about that ! But I have already an windows 8.1 pro system backup image at hand to upgrade to windows 10 after the release of RTM. Just to be on the safe side
Chris said nothing of the sort. inb4 is not a confirmation. It's a meme. Yes, it's 16-bit integer fun. 16th bit is the highest bit, obviously, but they've clearly decided to avoid any signed/unsigned confusion and just skip the 16th bit, which would encode the sign in a signed integer. 15th bit is the next highest, and I guess they just treat that as a sort of "RTM" flag. It was more clearly shown in some Vista SP betas iirc, where like .16633 would also be shown as v.249 in parts of the OS, 249 being 16633 with the 15th bit ignored.
Tks, and yeah, now I noticed the inb4, my bad. And tks for the explanation, although I still don't understand the binaries.
Wzor reveal Windows 10 RTM has been sign off the 12th July. But the 9th july his ''special day''. View attachment 36869
Wzor is an idiot, the 12th is a Sunday and I guarantee they won;'t be signing off anything on Sunday.
to my knowledge, they even work on Sundays during the hot RTM phase and so far it could happen that a sign off suddenly appears this coming Sunday
I am not sure, because BuildFeed couldn't find all the branch builds, guess we'll have interesting days to come.
They are adding them one at a time but still nothing in the RTM branch. 10192.0.150706-1800.fbl_kpg_CLIENTENTERPRISE_VOL_x86fre_en-us.esd 10192.0.150706-1700.fbl_sec_CLIENTENTERPRISE_VOL_x64fre_en-us.esd 10192.0.150706-1700.fbl_iot_CLIENTENTERPRISE_VOL_x64fre_en-us.esd 10192.0.150706-1700.fbl_esc_CLIENTENTERPRISE_VOL_x64fre_en-us.esd 10192.0.150706-1617.fbl_marketplace_CLIENTPRO_RET_x64fre_en-us.esd 10192.0.150706-1617.fbl_marketplace_CLIENTENTERPRISE_VOL_x64fre_en-us.esd They are keeping the build numbers divisible by 16 so maybe that means something and maybe not..maybe it's the next build after RTM..who knows?
The RTM build has 1st 4 bits to be 0, so the next build after RTM has to be at least 16 nos. higher than the RTM.
Guys I am pretty sure that even Gabe doesn't know and follow build numbers as much as you do. You are overexcited and obsessed