New
#30
I make images of all the builds I test lol so I restored my image of 18334 changed to fast and now downloading 18342.... Im just confused for the skip build do they release builds every week like this one? Newbie still learning ...
I make images of all the builds I test lol so I restored my image of 18334 changed to fast and now downloading 18342.... Im just confused for the skip build do they release builds every week like this one? Newbie still learning ...
Downloading now on an Intel I5 4690K at 30%. I'll post when successful.
WEK
Last edited by WEKJR; 20 Feb 2019 at 21:26.
Generally, this close to a new general release, you'll start to see more Fast ring releases, and it will slow a bit on Skippy. They really are on 2 separate channels and with different schedules. Fast is more like Beta and Skippy is more like Canary/Alpha. Doesn't fully answer your question, but don't think there is a "full" answer.
I completely understand so Skippy doesn't get builds every week?
Im updating now as we speak to 18342 and continuing here, I'm guessing we will be getting 19h2 when this one goes public
It is nothing like as predictable as all that. The Insiders get advanced looks at the next, upcoming major 'feature update' of Windows. Skip Ahead has always been an additional look at the release after that. They come when they come, sometimes weekly, sometimes not.
Now, the last Skip Ahead build was code intended for 2 releases ahead, completely upending the model. In my opinion, MS has jumped the shark with this move, and what with all these builds and rings and whatnot, and it's just an out of control mess.
In the beginning of Windows 10, the intention seemed to be to have tout le monde all running the same Windows 10. There are now many versions out there, all receiving CU's and updates and whatnot. It's more confusing and disorganized than ever, which is saying something.
I really wish they would tighten things up, but I don't know that they're capable at this point.
Made an 18342 ISO and am updating a Fast ring VM now. On a blocked CPU...... No smoke or flames....yet.
All good here on 6 yr old I5. Less than 9 min from restart to desktop - pretty good work, MS.