New
#50
Three strikes! I'm out!
Announcing Windows 10 Insider Preview Fast+Skip Build 17063 for PC Insider
-
-
New #51
No fails, ISO made no problems, under an hour for everything and now to start testing the new build. It's nice to have something new to use during the holidays. Happy Holidays to all.
Bob
-
New #52
UUPtISO worked and I copied the ISO to an external USB drive. Then I deleted the UUPtoISO directory on the C: since it weighed in at 10.5 GB with the ISO (not complaining I just have limited space). Now that's done and its time to reboot ...
-
New #53
My installation failed in one of the reboot, I wasn't present so, I don't really know what happened, when I came back it was rolling back to the old build.
But since I created the ISO before rebooting I cleaned the debris from the download/install and updated through the ISO without any problems.
-
New #54
I see lots of "canonical" in actionlist.xml.
took about 3 hours from d/l to final boot.
so good it says it did it twice:
-
New #55
Smooth update here, not timed but less than an hour overall, including making an ISO. Some differences in the update procedure, earlier builds switched to the monitor driven by the on-board graphics at 32%, this one at 44%. Switched back to my primary still at 44%, jumped to 48% momentarily, then to 52% for some seconds, and back to 46%. Incremented more or less as usual from then on, apart from flashing up a notice about "Installing updates (IIRC) 100%" after the restart at 75%, on a black screen. The usual "Working on updates 75%" on a green screen followed.
-
New #56
-
New #57
I haven't timed mine as I have been busy doing other tasks on the computer. The Desktop has been ready to install for a while, and I even have the .ISO made, but the laptop is still 3% from being ready to start rebooting.
Guess I will see if my machine joins the ranks of (what I suspect) is the set of machines that cannot update anymore because of aging hardware....
-
New #58
First time for me FAILURE
First attempt ended with "~ failed due to other updates going on"?
Second, third and fourth attempt reverts back to 17046 0x80000002 at the very end.
Tomorrow is another day!
-
-
New #59
Re the Win32 app elevation/Suspend issue in the last build, MS says:
"We haven't been able to repro it in builds > 17051, but we don't have an exact commit that might have fixed it, so didn't include it in the flight notes [for 17063]."
I haven't seen it yet in 17063, but then it never happened right away, either, usually a day or more after the last boot. Still, I think there's a very good chance that it's gone.
Quote
Related Discussions
