The Winpe doesn't expire anymore, there is no nagging to set the insider level, no watermark/exp date, it prolly is the final and official RS3 build.
I used this tool https://forums.mydigitallife.net/th...t-jatdevice-mkiii-v1-02-54.44717/#post-750896 My terminology appears to be correct since @s1ave77 says these tools convert https://forums.mydigitallife.net/threads/uup-dump.75052/page-5#post-1368477
^^Like that dejavu moment every time a new iteration gets released and some still deny RTM state, always so cute.
The screen on itself is not really proof, it would be more official if the url to that txt was posted
2 times already on 2 notebooks. Both systems were activated with Digital Certificate and kept this type of activation.
BTW, is there any way to prevent ContentDeliverManager from pulling down the suggested apps junk on a clean install in the first place? The GP in question only works on Enterprise/Education SKU. Maybe block it connecting to the internet via firewall rule (is this possible using the deployment tools)?
The debate is over. --- This is Windows 10, Red Stone 3, Fall Creators Update, RTM release. I am not particularly happy with the build number (16299.15), but there are more important things in life to be upset about and not just the silly ending point of a build. I am glad my source did not mislead me on when there would be release, so I did get the when part right. A small part of me still hopes that we'll get a small download just before general availability release (October 17) which would change the string to 16300, but it is not the end of the world if that does not happen. That all said, again, the debate is over. --- This is the RTM.
Windowscentral is not an official source, i have watched mr bowden going into some really depressing tweets last days.
I stopped the insider affiliation a few minutes ago, MS asked me to reboot, after reboot I still have 16299.15 running and digitally activated. that settles it
Mine two systems are activated by Digital Certificate and thus no problem to clean install. But I prefer long-history systems and hate clean install. For sure ProfessionalWorkstation is for x64 only
I'm happier that RTM is 16299.15 and not 16300, because to MS important to release stable build and not hurry to release new build number.