I let WU install this build, it worked perfectly. After a couple of restarts I ran Disk Cleanup, all is good here.. I started testing some apps I had installed in previous Redstone builds, one was VMware 11.1 which I had build 14342 Pro on which was updated by WU awhile back. I got a flash that it was going to expire on July 15th! I checked for WU & sure enough Redstone build 14366 was there waiting to be DL & installed, I let that run also. Strange that my VMware Redstone installs are not by using my Insider account, they just are there, though a bit old, this one now expires on October 1st.
Vip, Come back next Thursday and hopefully real thang I say Thursday because Microsoft Partners Conference ends that day (10th-14th), they hand off to OEM's, then hopefully us, Fri is the 15th, so probably Thursday afternoon
Sticking to a final build number only works if that final build number isn't going to be overtaken by preview builds. If you were to use the 'divisible by 16' rule, the next obvious number would be 14400. In some cultures this would not be a good number, but it's all up to Microsoft . Even when the build goes gold it won't be the 'release' build per se, it will just be the base build upon which the release build would be based. The main download and ISO's would be the final build, but any fixes between when it goes gold and the final will be in a patch released the same day, thus making the 'final release build of RS1' more of a strong foundation rather than an entity in its own right. So, the answer to the final build number is both right and wrong, assuming Microsoft stick with the bumping of the minor build number with updates (10586.494 for example). Excluding the minor build number/revision number however, the main build number would be final.
i also run a hackintosh on the same pc so i use windows 10 pro os x 10.11.6 and 10.12 beta 2 and 10.12 PB1 and linux mint 18 WTH was posted below me so much space wasted
well time to do a fresh install on a Bigger SSD so time to use the 512gb SSD os x is using boot into macos recovery restore macos 10.12 from the 512gb to the 256gb next reboot into recovery with windows SSD in and restore from 60gb SSD to 512gb SSD and done! or do a clean install hmmm