Why are people moaning about the RTM hehe In my opinion ist's an good build so far even my sound works correct and is that not what counts an good and stable OS ??
Yeah you proberly right about the time bomb that's an bummer but the watermark who cares Ps for me RTM is also beta but different RTM will get CU updates
ALL Windows 10 downloads (RTM/Insider or whatsoever) are simply Betas and will be further on! That a release is classified as final, would be only if there isn't any further development of that specific edition.
And to give a stage of development a name, the official release will be called "Final", But really, every time a "Final" major build is about to be released, MDL seems to be filled with the exact same "discussions", it's all said many times before
Has anyone had problems with using "uup-converter-wimlib-13" for this build UUP files. I get a error message "C:\Portable\uupdl\uup\16299.0\en-us\amd64\Microsoft.ModernApps.Client.cloud.esd": Error reading header: Invalid argument ERROR: Exiting with error code 65: Unexpectedly reached the end of the file."
No errors here: https://forums.mydigitallife.net/th...uild-16299-pc-rs3_release.75204/#post-1374340 Must be a corrupt or incomplete download.
Redownload and try again, watch the download progress closely for any errors, when errors, re-run the same download.
No errors from "UUPDL v0.08.30" during download. I downloaded again using "UUPDL v0.08.30" and this time "abbodi1406 uup-converter-wimlib_13" worked.
As with most other OS's, an RTM build is an agreed upon Checkpoint, for which development of current features is declared complete. Once the checkpoint release is out in the wild, it is given an RTM designation, and development continues on a new branch for the next version of the OS. Even going as far back as NTOS/2 (the original name of NT 3.1), Microsoft released a handful of checkpoint builds, where they encouraged developers to develop for NT on beta-quality checkpoint builds, even though several major changes occurred between each checkpoint. Re-targetting back in those days was much tougher, as developers had to wait at least a year between checkpoint releases. Windows 10's development cycle has been closer to the early days of NT's developer checkpoints than previous releases of Windows, as everything is forward-moving, instead of sticking around on a single checkpoint for a matter of years (or decades). The loss of Service Pack releases was a great way to force development into a quicker pace - delivering checkpoint releases far faster than previously possible. So, even though this build may not be the RTM, it is a part of the checkpoint releases. It will likely upgrade to the RTM properly, and then receive the next major checkpoint release with no issue.
With the arrival of 10, MSFT stopped using terms like RTM, Service Pack or even Upgrade, which they now call an update.
It's been posted on MDL many times by many posters, that with the release of W10 MS declared the term RTM defunct, I guess this explains it though...
