The methodology is not new. The BUILDS are. And thus as the builds change things will break, as noted in the Issues section of the first post.
It's not just a matter of updating a single file, like updating your program. Then entire OS has to be made ready to be updated, and if they have changed something significantly in the OS, the prep time can take longer.
And they may well have broken something n the update process itself, I mean, sheesh, you're beta testing.
No wonder it is taking folks some time to download (install) this update. Before I reboot, I am making a copy of the Windows.~BT folder, all 14.7 GB of it.
The .iso of version 193 is only 4GB
The mind boggles.....Release notes on this flight....how on earth can we participate when unable to establish a connection?.
This problem occurred on the last flight, you would have thought this would have been a priority...
- the build seems to have completed, but I'm still sitting here with this showing - rather a long wait..
The Windows.~BT folder for this build is over 14GB. That "installing" part of the message is actually the downloading of 95% the stuff in the folder. Under the "downloading" message, I had only 59MB in the folder. The "installing" part was when the bulk of the update was downloaded. That is why it is taking a while.
Nice and easy unattended update. It has been a while since I had one of these!
Update was stuck on 79% for awhile then jumped to 80% for another while. It is now up to 95% and is still writing to the disk a lot. Now 99% and crossing my fingers. A very slow download.
WEK
Quote
