Thanks. Do you have Enterprise, Pro and Core x32 ESDs too? And pls, what is your Enterprise x64 SHA1 hash?
Honestly, that's fine with me. With the compressed release schedules these days, it makes sense. If there are no large show stoppers Microsoft sign the build off for release, then any smaller bugs are fixed with a patch on release day. With software being developed on an aggressive release schedule, smaller issues are bound to appear but on the whole the last 4 builds have felt extremely stable, it's certainly more than ready.
Still no information on whether Microsoft have signed-off on the RTM/GA yet. It was rumoured to be happening yesterday, but still no information has leaked? But there are still no new builds showing on buildfeed other than 14393.3 which is just a updated sub-branch of 14393. So they seem to be working on a day one patch on the 14393 build, in other words 14393 seems to be the real deal? Would still love to have some kind of official indication telling us that 14393 is where it's at. Twitter is dead silent, and I don't know if that's a good thing. WZoR or someone else would normally have spilled the beans by now.
Can somebody post ESD for Education x64 es-ES? I just can't get it with a Hyper-V VM (I don't know why, but I can't enter to Insider Preview without errors) Thanks
My guess is the next properly new build on BuildFeed will be an RS2 one. They've not pushed another build to the flighting system, but we have noticed that they've been rejigging the internal rings slightly, so my guess is they're just making some tweaks to the flighting system while they've got an obvious breathing space before they push on with RS2.
Before they start pushing rs2 Builds, they will have to release a patch to change the Branch in the Registry from rs1 to rs2 or Windows Update won't see rs2 Builds to download. This had to happen with th1 to th2, then th2 to rs1.
TerminatorII I stand by this statement If the Branch in the Registry is not changed from rs1 to rs2, then Windows Update will not see any rs2 Builds to download. The Registry tells WU what Builds to download.
TerminatorII is quite correct; I think this was changed early in TH2 around the same time BuildFeed lost the logging data. You're correct about the registry being the ultimate determinator of Windows Updates, but you're missing what TerminatorII is saying. Before doing the SyncUpdates check on Windows Update, an Insider-connected machine will check with the Flighting Service to get the latest labs and other configuration data. If this has been changed on the flighting service, then before doing the SyncUpdate, your machine will reset the registry information to the data indicated to the service. You can see this for yourself by changing the lab key manually, then running a check for updates. It'll get reset to the public lab because it'll check with the Flighting service, which will indicate that you've not got the right data and reset the WU registry keys before the SyncUpdate takes place.