New
#11
The last couple of fast builds behave differently.
They get all the way to 61% and that is it.
Suggestions on how to solve this are very welcome.
The last couple of fast builds behave differently.
They get all the way to 61% and that is it.
Suggestions on how to solve this are very welcome.
The latest fast built gets all the way to 61% and that is it.
Suggestions on how to solve this are very welcome.
There are points in the update where it will not display any changes to the % progress. 63-64% is one, another is around 73-74%. That does not mean it has stalled, stopped, broken, or crashed. Check your Task Manager>Processes Tab when these apparent "stalls" occur. It is very likely you will find high CPU and/or Disk I/O for either or both of the processes "Windows Update" and "TiWorker". This is natural, not an error. How long it remains running like is will depend on your machine's hardware....MEM, CPU, HDD/SSD, space available, a number of factors.
If you just kill it thinking it's stalled, and restart the update, you'll get right back to the same spot. You just need to verify it is actually doing something, not frozen solid, and let it be until it's finished. No way to predict for you how long that would be.
If it really is taking forever to update using Windows Update method, try making an ISO and update that way.
The ISO can be made by going to UUP dump and follow the instructions. Many of us do this, just ask in the latest Insider build thread for help if needed.
Updating the build with an ISO is exactly the same process as an In-Place Repair, don't let the words spook you. Same process.
Repair Install Windows 10 with an In-place Upgrade
Hi Tom
Thanks a lot for all the insight. A few days ago I noticed a Feature Update was installed. That gave me hope! So I forced the install of the newest fast install and let it sit for 12 hrs, it did not finish, still stuck. Because of what you wrote I forced another install and left it alone for another 24 hrs. When I checked again the OS was updated. Did it really take more than a day, was it the feature update, was it the new fast version ? No ide, but next time I will let it run at least 24 hrs!