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

slicendice said:

I absolutely agree with this statement!

But it makes me wonder what drastic changes the devs has made to cause these issues. I bet they have re-enabled some ancient kernel code for some new and exciting features, like they did for the Linux Subsystem.

The problem was fixed in less than two weeks. I had an AMD and had to skip a build - SO WHAT. It is still early in RS4 development cycle. People forget what Insiders is about - testing stuff! So some could not test a particular build - big deal (for non english that means NOT a big deal)!

Why are people still harping over an issue that is no longer an issue?

If people are concerned about quality of builds, do not use Fast Ring. I used to say builds should be tested more before release etc, but I realised that just slowed down releases on Fast Ring reducing amount of testing overall.

HippsieGypsie said:

Haven't seen nor heard a peep on how they fixed it. Like mushrooms in the dark. You'd think some reason would be given.

MS is not very verbose when it comes to things like that.

cereberus said:

The problem was fixed in less than two weeks. I had an AMD and had to skip a build - SO WHAT. It is still early in RS4 development cycle. People forget what Insiders is about - testing stuff! So some could not test a particular build - big deal (for non english that means NOT a big deal)!

Why are people still harping over an issue that is no longer an issue?

If people are concerned about quality of builds, do not use Fast Ring. I used to say builds should be tested more before release etc, but I realised that just slowed down releases on Fast Ring reducing amount of testing overall.

I fully agree with everything in above quote!

It may not be a "big deal" but on the other hand I'm also looking for new stuff to test and MS's is not providing any explanation about cause of problems like that. Being an insider also implies having inquisitive mind and thinking. Any testing like insider versions should be done in scientific way.

CountMike said:

It may not be a "big deal" but on the other hand I'm also looking for new stuff to test and MS's is not providing any explanation about cause of problems like that. Being an insider also implies having inquisitive mind and thinking. Any testing like insider versions should be done in scientific way.

Since all we get is a compiled version of the code i.e. a black box, then no matter what - it either works or it does not.

Sure you can be curious why a build was not released, but really it is irrelevant as you do not test build that are not released to you. Frankly, I do not see much point in explanations that detract from the point.

I fail to see how Insider testing can be anything more than random testing.