Announcing Windows 10 Insider Preview Fast+Skip Build 17063 for PC Insider

bordi · 29 Dec 2017

dencal said:

Do make sure that the Motherboard matches with the eighth generation i7 CPU....ie Z370.

Yes mate thanks, I’ve narrowed it down to these below

moorhen2 · 29 Dec 2017

bordi said:

Yes mate thanks, I’ve narrowed it down to these below

Have you looked at G-Skill ram, ?

Tony K · 29 Dec 2017

That's great, guys, but as cereberus pointed out this is the Insider thread.

PC Custom Builds and Overclocking - Windows 10 Forums

johngalt · 29 Dec 2017

AndreTen said:

nightly 58??

No, nightly is 2 steps ahead. Current Nightly builds are 59.0 alpha 1

badrobot said:

Just wondering. why not 16299 straight to 17063?

Uh, because this was in the beginning of December when the was no 17063?

johngalt · 29 Dec 2017

f14tomcat said:

No. I have not jumped back several builds to find which one will successfully migrate to the next, then to the next, etc. I'll keep it in mind, though. Thanks for the suggestion.

No, that wasn't my point. My point was clean installing fast ring builds directly is not supported and tends to give more issues than it is worth, so it might be worth considering using the MCT to build a regular install media for clean installing and then using the UUP2ISO created media to upgrade.

The tutorial I linked to didn't work as planned for me, so I just opted to use my UUP2ISO created media to upgrade directly to 17046 after installing FCU, and it worked perfectly fine. Later, when 17063 was released I took it as an upgrade directly through Windows update.

I understand, though, if you are testing specifically single build upgrades - good to do on one / couple VMs / machines. I would upgrade at least a couple of them in the 'Microsoft-accepted manner' as well, if for no other reason, then to verify if certain issues maybe caused by the unsupported direct clean install of Fast ring builds.

johngalt · 29 Dec 2017

badrobot said:

Just wondering. why not 16299 straight to 17063?

Sorry. Just read back on my post, and realize it may be confusing.

What I meant to say was that, at the time I was clean installing, 17046 was the latest build out, so I clean installed FCU (16299) abd then used my UUP2ISO created install media to upgrade to 17046.

Then, when 17063 was released, I upgraded it normally through Windows Update.

I hope that cleared up my confusing previous post - thanks for pointing it out

f14tomcat · 29 Dec 2017

johngalt said:

No, that wasn't my point. My point was clean installing fast ring builds directly is not supported and tends to give more issues than it is worth, so it might be worth considering using the MCT to build a regular install media for clean installing and then using the UUP2ISO created media to upgrade.

The tutorial I linked to didn't work as planned for me, so I just opted to use my UUP2ISO created media to upgrade directly to 17046 after installing FCU, and it worked perfectly fine. Later, when 17063 was released I took it as an upgrade directly through Windows update.

I understand, though, if you are testing specifically single build upgrades - good to do on one / couple VMs / machines. I would upgrade at least a couple of them in the 'Microsoft-accepted manner' as well, if for no other reason, then to verify if certain issues maybe caused by the unsupported direct clean install of Fast ring builds.

Thanks, John, for all you've pointed out. There may be a little misunderstanding. I am not having any issues with clean installing anything. My issue is the MS accepted and approved method of upgrading from one build to the next. In this specific case, from 17046 to 17063. It simply will not do. Rolls back every time. This is the first time I have had so many problems with it in many, many months. It has always worked fine before. Not this time. The issue is all over Feedback and Dona & Brandon's Twitter. So it's not just me.

martyfelker · 29 Dec 2017

I have no issues either updating 17046 to 17063 or using the "rogue" clean install of 17-63 from an ISO created using uup2iso.

Wynona · 29 Dec 2017

f14tomcat said:

Thanks, John, for all you've pointed out. There may be a little misunderstanding. I am not having any issues with clean installing anything. My issue is the MS accepted and approved method of upgrading from one build to the next. In this specific case, from 17046 to 17063. It simply will not do. Rolls back every time. This is the first time I have had so many problems with it in many, many months. It has always worked fine before. Not this time. The issue is all over Feedback and Dona & Brandon's Twitter. So it's not just me.

And I updated from 17046 just fine . . . go figure.

Another thing that makes me wonder about non MS support of creating our own ISOs and clean installing, is that Kari has continually helped us with tutorials and instruction on same. So, it can be assumed that Kari's aiding and abetting creating our own ISOs and clean installing, yet he has recently been awarded an MVP. Just doesn't compute that Microsoft would be unaware of Kari's work on our behalf. If they really, really don't want us to have this procedure in our arsenals, it would seem that they'd tell Kari not to do it anymore.

The issues I have with Build 17063 are minor, but annoying. Today will tell the tale of whether a clean install will eliminate those.

AndreTen · 29 Dec 2017

johngalt said:

No, nightly is 2 steps ahead. Current Nightly builds are 59.0 alpha 1
Uh, because this was in the beginning of December when the was no 17063?

Thanks John. Not sure about jumping to 59.0 alpha

Rumors are, they'll fix it in 58 and 57, on the other hand 57.0.3 is out and no fixes, nor in 58...