If you go on a RTM as the build that companies have put on the first machines out the door, then 22000.9 is the RTM. 22000.194 is the official M$ release build. 22000.25x will be the next stable build.
Correct. But in all 3 cases base build 22000 is the same, so people who clean installed 22000 starting from June (with no Windows Insiders enrollment) was already on final base build, and just got regular CUs as a proper production OS.
Business ISO's are different checksums to the IP ISO's. Business links not been posted yet? @Enthousiast 22000.194 Business ISO's Checksum post.
Yes and no. The idea that the same build number 22000 would be the one they would stick with and just use cumulative patches was correct. The idea that the original 22000.51, 22000.9 or any of the previous cumulative patches were the final versions or *cough* RTM is incorrect. Enthousiast and others were right in that we very much need to retire that term. It means nothing anymore. MS is clearly intent on releasing garbage and signing off on releasing garbage. I apologize for being so belligerent about insisting that it would be different because this is a "new OS and not a refresh ISO". I clearly had no idea how far MS had fallen in the quality department.
Hello! I have already install the Insider Preview Build 22471.1000(yesterdays build) what i have to do to have the retail version without do clean install??
I think they originally planned on making a 32-bit version but then they decided on doing the TPM requirement. I'm pretty sure TPM requires UEFI and since MS only allows UEFI booting in 64-bit mode, that means either they had to start supporting 32-bit UEFI or drop 32-bit support. I can't even imagine trying to run this OS on a single 32-bit processor core. They've had 64-bit processors for a couple decades. I think they just decided it was time to drop 32-bit OS support.
I don't want to put words in his mouth, but I think his plan was to make svf patches from consumer isos to business isos. That way people can download the consumer isos directly from MS to save us all bandwidth and then some of us can share around the smaller smartversion delta patches. Depending how large those patches are that plan could change. If they are fairly small like a couple hundred megs or less, it's a decent plan. If they end up like 500+mb it might be easier to try techbench ver1 iso to techbench ver2 (aka final) svf patches which would probably be much smaller. This is less preferable because you have to log in with a insider account iirc to download them. @Enthousiast will figure out something. He's a smart dude.
Yeh I agree, but the problem is RTM is etched into the minds of most, so much so it wont be easy to simply ignor it. It has an almost mystic meaning to too many. When a manufacturer starts putting it on their machines, rightly or wrongly, the public believe this is the "first stable final version", ready for the public. They will naturally call it RTM, even if the term and operating system fail to meet the minimum standards. Yes M$ has adopted a new way of rolling out an operating system. Like it or lump it, thats their right to do so. One has to strike that balance of being familiar with the old ways, and at the same time, realising the change is here to stay. Til there is a term the public like for what manufacturers first start putting on their machines, RTM will be around for a few builds to come.
I think from a "Prosumer" user like many of us here and from a merely practical point of view, the term RTM in the past was just used to identify the "final" Build or ISO to be used for clean installing our main device(s) with and be sure to receive all future production Windows Updates for that build without issues. Well, even if there are no more "final" Builds or ISOs as per current distribution model, that actually happened this time starting with 22000.1