PC vendors need at least 2-3 weeks to have their devices pre-installed with 1703. There simply is not enough time for Microsoft to push out a new build at this time point.
Am thinking this doesn't matter to be fair and can be done by the end user after all via windows 10 update after all windows 10 has no real changes.? just a few new features added to be frank ..
Same here, ran the test version of the update tool after the ISO's started to 404. Instead of upgrading to 15063, it downgraded me to 14393 without any updates. I just tried running it again, and now it can't download the ESD. Checked in Fiddler, it's trying to go to go.microsoft.com/fwlink/?LinkID=844074 which redirects to gwx.windows.com/preview/cxe/vanilla/products_rs2.xml which the installer doesn't seem able to handle. Maybe they're working on finalizing the backend for the upgrade process?
That testversion did try to download 15058 full esd from Chinese servers, it never worked. And the 15063 full esd permalinks still work. So please, stop spreading nonsense.
Also everything is digital stream these days.. Just look at pc/console/mobile games before you could play straightaway once you visited you're local game store but these days you have to download the content even before you actually play the game these days also pc vendors don't need time due to being in the windows insiders program .. most likely what will happen is that you need to read the fine small print there is always a catch these days Main reason No RTM for Windows 10, Microsoft Says back in 2015 ..
It was done, because same ISOs will be re- released without "Insider Preview" descriptions. Anyway we have everything apart that those two FOD ISOs, right? Or do we have FOD ISOs too?
They didn't bother to block the 14393 IP links at the Techbench Dump after releasing 14393 officially.
This time it generated too much traffic probably. Only for me it was 68GB today (en-US + cs-CZ). ) For ESDs another 57 Gb + updating all those test VMs to grab the links. 20 GB UUPs. 6GB baseimage.wim and leaked Kits.
The Sleep Mode seems to be moody on some devices as well, usually it requests a password after wake up, but occasionally it wakes up into the session without a password. This is a serious security breach in some environments. I hope they'll have it fixed soon. P.S. Fresh installations (not upgrades) don't seem to exhibit weird behaviors.
The esd's, which the upgrade assistant/MCT would download, were never down, so why did you get the "404 forbidden" error?