Well, I think that after they identified the "show stopper" bug when it was too late, the next build will address it and will become the new RTM for SCU. Same mess could happen again if they will find another similar one after...
17133.73 is stable for me and my type of usage. Unhappy that i bothered to install it (thinking it's RTM), but I will just stick to it until a real RTM happens, and cleanly install that new build again zzz. Lost time.
So will a clean install of 17133.1 auto update to 17134 via Windows updates or whatever the next real RTM would be? or would it require another clean install?
i mean its kinda funny how people blame Microsoft because they jumped the gun on 17133.1 and installed it on their machines. Its not done until its done guys. I am as eager to reinstall as most people but after the 16299.0 "disaster" you should really have learned your lesson.
sure thing but is it really worth the gamble to install 2 weeks early? There is always the chance of something like this happening. Scoll back some 40-50 pages and you find people answering the "should i install now?" question with "yes sure thing / its rtm" all over. 2 weeks of waiting saved a lot of us from double installing.
16299.0 was an evaluation build, it has expiry date and watermark how possibly anyone would think it's RTM?
WU/UUP side effects https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-282#post-1418532
On an unrelated note, is there any credible intel on whats so wrong in 17133.1 that they canceled its RTM status and rollout? I mean to do that, something must have been really screwed up.
The build had update blocking bug which meant a certain percentage of PC configurations would have failed to update to it automatically.