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

martyfelker said:

Maybe tomorrow more likely next week. 17050 released to buildfeed. I'd like more information on the A/B thing. Will people be informed about what sub-ring or whatever they choose to call it, they are on? I'm concerned that this may have significant impact on the discussion on the forum going forward.

I would be more concerned if it did not have a significant impact. As the old saying goes "If there is one thing worse than being talked about, it is not being talked about" :-D.

cereberus said:

I would be more concerned if it did not have a significant impact. As the old saying goes "If there is one thing worse than being talked about, it is not being talked about" :-D.

Not sure I understand you. Personally, I am on the Skip Ahead track (or at least I was when I last checked - I'm in Linux right now). And yet I have no assurance that I would not be assigned to the B category - which would be contradictory by definition. In general somebody being on the B track would hardly seem to be an "Insider". I hope there will be more of a clarification of this when the next build is released. How could the A and B versions be the same build? These are but a few of the questions that are involved. I will need to scroll back the conversation to find the link to an apparent Feedback Hub discussion but I have little reason to think that that is more looked at than this forum by MS employees. It seems dated by a week or more in some cases.

magilla said:

I think you’re right Marty, more likely next week— and it will be interesting to see what happens to feedback dialogue as a result of the new sets, etc that will be differentially distributed/allocated.

It will be definitely interesting times ahead if Microsoft once again attempts to carve out different classes of Insiders. Remember many of us have been thrown off Skip ahead and had to use the registry hack to return. I can't fathom this decision but then again they are not paying me the big bucks.

Update:

#WindowsInsiders we’ve hit a bug that prevents UWPs from opening so we will not be flighting a new build today. Have a great weekend!

Tweet

— Twitter API (@user) View on Twitter

Definitely a good reason to par on flighting a build, especially after the AMD fiasco

johngalt said:

Definitely a good reason to par on flighting a build, especially after the AMD fiasco

Agree....

This buggie kinda puts a dent in the "One OS across all your devices".

I think Insiders are putting a lot of pressure on the devs and testers -- been there, done that, even wore the panties...in corporate...hey, it's not fun.

Having said that-- they seem to be doing OK... just saying (WAAS is about hustle... LOL)

Superfly said:

I think Insiders are putting a lot of pressure on the devs and testers -- been there, done that, even wore the panties...in corporate...hey, it's not fun.

Having said that-- they seem to be doing OK... just saying (WAAS is about hustle... LOL)

If the Insiders are putting a lot of pressure on the devs and testers and MS are responding then the Insiders are doing a good job and their views are being taken on board.

DooGie said:

If the Insiders are putting a lot of pressure on the devs and testers and MS are responding then the Insiders are doing a good job and their views are being taken on board.

Fair enough... but releasing a build that precludes a specific CPU is premature IMHO... surely beta builds need to garner info from the broadest spectrum?