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

Tony K · 07 Jan 2018

Winuser said:

Has anyone used the reg hack to rejoin the Skippy build lately? I tried to rejoin tonight and after a restart my Insider reverts back to the Active development of Windows slow ring.

I hope I'm wrong, but I think I read that they closed that off to where that won't work anymore. Wish I had a more defining answer for you.

Tony K · 07 Jan 2018

LEOPEVA64 said:

I kept thinking about that and wanted to know if all the apps could be opened with "Sets", I have 5 third-party apps that I use regularly and all of them are compatible.
Out of curiosity I also wanted to know how many apps can be opened at the same time, so I opened almost all the apps I have installed (24), with 20 apps open, my PC slows down so I did not open any more.

LOL! That's really testing it, Leo. :)

Haven't had much time to toy with it yet.

Winuser · 07 Jan 2018

Tony K said:

I hope I'm wrong, but I think I read that they closed that off to where that won't work anymore. Wish I had a more defining answer for you.

After a restart of my computer earlier I got a message about my Insider settings. When I checked I found out that I had been changed to the slow ring. When I use the reg red hack I get changed back to the Skippy ring. When I restart my desktop I get changed back to the slow ring. I'm going to make sure I'm in the fast ring and see what happens when I do a restart.

johngalt · 07 Jan 2018

Berton said:

Didn't we get to Build 17063 about the time of the announcements or maybe before?

Umm, Meltdown was released to the public after 17063 was released. But it has been known about for much, much longer. The researchers responsible for discovering Meltdown reported it to Intel back in June 2017. And everyone was working on patches as far back as November (as reported) but IMO probably as far back as late August

Tony K said:

I thought the reason was some UUP deliver bug.

And LOL. I thought this was the 063 thread and saw Brink's post before yours and thought we were getting a build. Didn't look at the numbers. I was in my FCU and booted over to my IP. Started pinging the update server with no results. Then come over her to find you're on the 035 thread.

A little before, yes?

Sorry for the confusion lol - but I am curious if the original bugcheck caused in AMD devices was because this was version 1 of the proposed patches to the NT kernel by Microsoft, which were being tested by us Insiders.

johngalt · 07 Jan 2018

Winuser said:

Has anyone used the reg hack to rejoin the Skippy build lately? I tried to rejoin tonight and after a restart my Insider reverts back to the Active development of Windows slow ring.

I did it when I did my (last) clean install a couple of weeks before 17063 came out. And I am currently still on Skip ahead

Winuser · 07 Jan 2018

I did a restart while set to fast ring and it stayed in the fast ring. Then I did the reg hack again and did a shut down startup and the setting stayed on Skippy. I'll keep checking to see if it resets back to slow.

Wynona · 07 Jan 2018

johngalt said:

Umm, Meltdown was released to the public after 17063 was released. But it has been known about for much, much longer. The researchers responsible for discovering Meltdown reported it to Intel back in June 2017. And everyone was working on patches as far back as November (as reported) but IMO probably as far back as late August

Sorry for the confusion lol - but I am curious if the original bugcheck caused in AMD devices was because this was version 1 of the proposed patches to the NT kernel by Microsoft, which were being tested by us Insiders.

Surprisingly, John, I've never gotten the "bugcheck" on this AMD machine. Guess I'm just lucky. :)

CountMike · 08 Jan 2018

Winuser said:

I did a restart while set to fast ring and it stayed in the fast ring. Then I did the reg hack again and did a shut down startup and the setting stayed on Skippy. I'll keep checking to see if it resets back to slow.

That makes sense, Skippy is Fast only.

Tony K · 08 Jan 2018

johngalt said:

Sorry for the confusion lol - but I am curious if the original bugcheck caused in AMD devices was because this was version 1 of the proposed patches to the NT kernel by Microsoft, which were being tested by us Insiders.

No harm done on your part. It was the trouble of my own making. I just have to look more closely. One of those moments where I sat back in my chair and laughed at myself.

So far as the bugcheck and the AMD block with 035, I was under the impression it was a UUP delivery flaw, but then again one couldn't install even with an ISO. I'm quite sure members have tried that. So far as I know my/our IP 17063 doesn't/don't have the data of the KB patch that FCU was given as seen below. Not sure why some say it does.

Attachment 171486

Winuser · 08 Jan 2018

CountMike said:

That makes sense, Skippy is Fast only.

I just brought my computer out of sleep and checked my Insider setting. I was back to Insider (active development of Windows) slow ring. The computer was never shutdown or restarted. Apparently the reg hack is no longer a permanent setting. At least for me anyway