Announcing Windows 10 Insider Preview Skip Ahead Build 17004 for PC Insider

Edwin said:

Windows Hello not working properly;



then I'll walk away and make a coffee, come back, dismiss the Lock Screen and I'm signed in anyway!!!

Is it not recognizing the camera, or what @Edwin?

I would say Skippy is definitely back as they seem to be trying to deal with the multitude of hardware detection problem. Here's another build 10.0.17006.1000 (rs_prerelease.170926-1400)

As to when we will get a Skippy build next week is of course up in the air. If they are now compiling and uploading a build to buildfeed every day we should get 17009 next week - maybe Wed. As to how they are going to merge Skippy with Fast/Slow will be interesting.

martyfelker said:

I would say Skippy is definitely back as they seem to be trying to deal with the multitude of hardware detection problem. Here's another build 10.0.17006.1000 (rs_prerelease.170926-1400)

As to when we will get a Skippy build next week is of course up in the air. If they are now compiling and uploading a build to buildfeed every day we should get 17009 next week - maybe Wed. As to how they are going to merge Skippy with Fast/Slow will be interesting.

@martyfelker

Marty, this line is from the release notes post #1. It seems Fast/Slow will be merged into Skippy, instead. Fast/Slow becomes FCU, and Skippy becomes Fast/Slow. Skippy goes on vacation until late next Spring when it's re-born as RS5. These are not facts, just MO.

---

RS4 builds include many of the same fixes included in the latest RS3 builds.

f14tomcat said:

@martyfelker

Marty, this line is from the release notes post #1. It seems Fast/Slow will be merged into Skippy, instead. Fast/Slow becomes FCU, and Skippy becomes Fast/Slow. Skippy goes on vacation until late next Spring when it's re-born as RS5. These are not facts, just MO.

---

RS4 builds include many of the same fixes included in the latest RS3 builds.

OK thanks. Does that mean that the "RTM" released on Oct 17 with be a 17K build ? I'm suppsoingthat must be the case. Next Spring Skippy will return with 18k builds? Numbers are easier for my brain to relate to this case.

martyfelker said:

OK thanks. Does that mean that the "RTM" released on Oct 17 with be a 17K build ? I'm suppsoingthat must be the case. Next Spring Skippy will return with 18k builds? Numbers are easier for my brain to relate to this case.

No it does not mean that. It means that once RTM is finished MS merge Skip Ahead code with new features into that RTM as much as possible (may exist some incompatibilities and need refactoring first). Skip Ahead will go on vacation and we will have the usual Slow and Fast Ring builds until we are close to RS4 RTM, and then Skip Ahead for RS5 will be introduced while amount of RS4 features have been locked (no new features added) until that RTM is released.


We should not care about build numbers, except for remembering which one is the RTM, like 15063.0 and so forth...the rest is meaningless really.

slicendice said:

No it does not mean that. It means that once RTM is finished MS merge Skip Ahead code with new features into that RTM as much as possible (may exist some incompatibilities and need refactoring first). Skip Ahead will go on vacation and we will have the usual Slow and Fast Ring builds until we are close to RS4 RTM, and then Skip Ahead for RS5 will be introduced while amount of RS4 features have been locked (no new features added) until that RTM is released.


We should not care about build numbers, except for remembering which one is the RTM, like 15063.0 and so forth...the rest is meaningless really.

Exactly.

larc919 said:

It would be great if Microsoft changes that and decides to keep Skippy in play.

Can't see that happening. Simply too much time effort would be required to keep two different Fast ring forks alive.

On another note, some half a year ago I promised to make this tutorial next weekend. As this is the first weekend since then , I finally got it made:

Tweet

— Twitter API (@user) View on Twitter