@ Lobo11, Haha, no worries, I got like 8 hours sleep last night. Have you slept yet? Busy again tomorrow but like I said last night, I'll probably just skip this build and get the next one, Thursday is open here.
No new features, I at least thought they would have EDGE store, more extensions I'm staying with Chrome Dona please have held this back to surprise us, please
It has to pass through internal ring testing first... Builds do not get compiled and release to insiders instantly.
RS1 is feature complete and they announce what's coming out for rs1 at build2016. So no "surprises"regarding stuff that wasn't talked about at build.
Another uneventful, perfect upgrade install through WU--from 14385. No, there is no sarcasm here, I am actually getting accustomed to things working well again... However...my AMD Crimson 16.7.2 driver package *still* fails to install with secure-boot on...! It's a SHA-256 certificate problem that neither Microsoft nor AMD either singly or together has been able to work out (don't really know how much effort either entity has put into it, though.) Crimson 16.5.3 is the last AMD driver install that works properly with secure-boot on, and 16.5.3 is the last Crimson driver package to use *only* a SHA-1 certificate for ...\bin\atdcm64a.sys I'm guessing that Microsoft still hasn't firmed up its SHA-256 certificate formats for Win10 and that AMD is guessing...?...SO don't know who to blame for this ongoing problem--Microsoft & and AMD have both officially acknowledged the situation but it has yet to be fixed....I use Firefox x64 DE and don't use Edge, so really this is my largest outstanding issue. Getting tired of running with secure-boot off (either that or dropping back to 16.5.3.) Anyone got any news on this topic, per chance?