it's very variable for me. It varies from two and a half to five hours to get to the restart 16299.0 was two and a half 16299.15 was over three. The part after the restart is 30 to 45 minutes and doesn't vary much for me. The part that takes the longest is Installing, particularly the 60 to 80% range.
I have tried to install this build numerous times and i keep getting this error - Windows 10 Insider Preview 16299.15 (rs3_release) (6) Last failed install attempt on 04/10/2017 - 0xc1900101a, any help would be appreciated.
What changed in UUP is that because some users had requested that the computer should remain online (usable) for as long as possible during the upgrade process, MS moved most of the process to the online phase. What we have now, is a very slow upgrade process and the computer remains still unusable for many tasks that are time critical (we have now a lot of lag and stuttering in everything we do while upgrade is in progress). The previous version of UUP was much faster, because it did most it's work in offline mode.
WU, UUP and tools like DISM still has a very long way to go. There is a lot that can still be optimized. One optimization would be to improve speed and compression levels of DISM to same level as the open source wimlib-imagex does, which has multithreading support and can run on all CPU cores/threads available.
So if UUP was bad, now it is even worse. :)
Thanks for doing that - I was thinking on similar lines but you beat me to it.
In my global.ini, I don't have IsFirstTransitionToPlaceholderEnabledState - it's not there at all (so obviously is neither True nor False)
I do have SavedPlaceholdersEnabledState, and the pattern is the same as you've seen.
I note that merely joining the Release Preview ring is enough to switch the Onedrive state to turn placeholders on again.
HUH!?! My Windows suddenly started to behave erratically. Nothing was responding not even after a couple of reboots.
Now it's behaving normally again.
The time that it takes for me to update my system is pretty constant. From the time that I press "check for updates" to the time that I am completely into the new build takes less than half an hour. This includes;
1. Getting ready to update
2. Downloading update
3. Installing update
4. Restart
5. Into the new build.
Even as an insider I would not have the patience to wait an entire hour to update my system.
As an aside, a clean install of a new build, such as I performed with 16299.15, takes about 10 minutes. This is also pretty constant. Anything more than that and Microsoft would be alienating many a customer.
Quote