She just only said: "No builds today" Could be meant for Active Fast or Skip Ahead Fast. I can't remember a tweet, mentioning: "no new build today", when 15063.0 already was known to be the official final release.
All is possible, right before a weekend she normally tweets: no new builds (today), sat, sun or mon. This time she didn't. Also the tweets after they left MSIgnite were a bit harsh, caps used in answers and stating MSIgnite was closed, but there was one day left in Orlando, maybe a bit of troubles with the final build, it's all uneducated speculation, but still....
i literally formatted from CU to 7 to avoid the issues with it. Hopefully fall update has them fixed.
She tweeted this to give a false impression that 15063 is just another ordinary insider build. Just read the disappointed replies to her tweet .
On build 16299.0 (RS3_RELEASE) I had to disable Secure Boot in my BIOS to use DISM at all. In my case on my X99 board change it from 'UEFI' to 'Other O/S'. Now, this was after installing the latest DISM with the Windows Assessment And Deployment Kit. You may not need to if you use the built-in DISM in the build, I'm not sure, never tried.
I'm pretty sure they are still experiencing issues and/or bugs at this stage so that's why they haven't released RTM build yet. Perhaps date of GA will extend. No stable release till today. Just wait and watch
After you format your computer The previous recommended "fix" of simply upgrading to a new version was one of the stupidest recommendations I ever did read coming from a security company. The idea that you could resolve (fix) a compromised system by upgrading that already compromised system was foolish, especially when they had no idea what little "gems" may have been added once the system was infected. Avast was so quick to PR Mode (public relations mode) that they ended up giving misinformation at first. We now know that 1) Both 32-bit and 64-bit of CCleaner were infected (not just 32-bit as originally claimed) 2) Upgrading will not resolve the issue since it loaded a payload into the infected systems The only guaranteed way to fix this is to format your computer and start fresh. The only people who will find that hard to accept is those who do not make regular backups. https://forums.mydigitallife.net/th...njected-compromised.75147/page-2#post-1374693
1710 has only been reported for Xbox and 1709 has been reported for PC and Mobile. -- I think it is strange that they're not all the same, but leave it to Microsoft to do strange things.
RTM has been finished a long time ago, new builds are just released to keep the action going, thus the reason, they have watermarks and timebomb.
I suspect that will change in time, as it did from Red Stone 1 to Red Stone 2. In the early days of every new release, they tend to reflect closely to the current release, and once they progress, finally they refer it as a new id.
It's working in V15063.632. And as you might of seen MS acknowledged the problem. Now, if you want to talk about bloatware, Symantec, Acronis, Nero, and yes Apple and so on are all pretty good at that game. At least Apple is dumping apps from iTunes.