Windows 10 Insider Preview Build 17101 Fast + 17604 Skip Ahead Feb. 14 Insider

slicendice said:

It could be but I doubt it is directly related to this issue in particular. One never knows though. MS is always so secretive when it comes to what they changed/fixed/broken. They only tell us all the irrelevant information and leave out all the relevant core and system related information.

It is absolutely impossible to find the root cause and possible workarounds for issues on builds where NO debug symbols are released (which is the case for most builds).

A record of "We changed default font size from 12px to 14px in settings app" is pretty much irrelevant information or is very obvious if one opens up the Settings up. But information like "We re-enabled a kernel feature that enables us to open ELF binaries natively" is very relevant, since it is not obvious and such drastic changes can cause a lot of misbehavior because of all the newly enabled code loops.

Lol. Exactly. But I also realize that they opened the Insider Preview program too widely, so that the average Joe and Jane users with with an almost complete lack of computer use skills, forget troubleshooting proficiencies, can (and often still do) try to run these IP builds on a regular basis.

It never fails to amaze me at the bashing I hear when something doesn't work in one of these IP builds, and more than once I have gotten into (admittedly, even heated at times) exchanges with users right here who vehemently argue that these are ready for RTM use builds, not ßeta builds at all.

I am not pointing any fingers at anyone, and especially not you, though my reply is to you, I am not implying anything by replying. (Had to put that disclaimer in there because I suspect someone might take offense at this post, when clearly you and I are actually agreeing with our trip posts).

CountMike said:

0 Suspended is not binary number here, it just means that none are suspended, 1 suspended would mean that one instance (thread) is suspended but when I look at mine that none are really suspended although some are. In Startup tab, when I open it first time, for a split second shows old way, Enabled or Disabled.

Good catch. I thought it was binary, because all I saw were 0s and a few 1s,. No other numbers at all.

But at least it makes a heck of a lot more sense now lol.

Thanks.

johngalt said:

Lol. Exactly. But I also realize that they opened the Insider Preview program too widely, so that the average Joe and Jane users with with an almost complete lack of computer use skills, forget troubleshooting proficiencies, can (and often still do) try to run these IP builds on a regular basis.

It never fails to amaze me at the bashing I hear when something doesn't work in one of these IP builds, and more than once I have gotten into (admittedly, even heated at times) exchanges with users right here who vehemently argue that these are ready for RTM use builds, not ßeta builds at all.

I am not pointing any fingers at anyone, and especially not you, though my reply is to you, I am not implying anything by replying. (Had to put that disclaimer in there because I suspect someone might take offense at this post, when clearly you and I are actually agreeing with our trip posts).

Actually both views are sort of right.



Insider builds go through several phases

1) initial restructuring - highly buggy

2) addition of major new features (quite buggy especially features)

3) rationalisation of new features already introduced but not many new ones (less buggy)


4) no new features - mainly bug fixes prior to release (fairly stable)

So it really depends where you are in the development cycle whether you can call it very buggy, fairly buggy, moderately buggy, or fairly stable.

cereberus said:

Actually both views are sort of right.



Insider builds go through several phases

1) initial restructuring - highly buggy

2) addition of major new features (quite buggy especially features)

3) rationalisation of new features already introduced but not many new ones (less buggy)


4) no new features - mainly bug fixes prior to release (fairly stable)

So it really depends where you are in the development cycle whether you can call it very buggy, fairly buggy, moderately buggy, or fairly stable.

I wouldn't call 'fairly stable' equivalent to RTM.

Micro$oft might, but *I* don't. [emoji14]

johngalt said:

I wouldn't call 'fairly stable' equivalent to RTM.

Micro$oft might, but *I* don't. [emoji14]

One can ask for full stability only with official MS release but not in any build before fat lady sings.

CountMike said:

One can ask for full stability only with official MS release but not in any build before fat lady sings.

Agreed.

And even then, asking doesn't imply receiving :rotflmao:

johngalt said:

Agreed.

And even then, asking doesn't imply receiving :rotflmao:

That's for sure, otherwise no updates and debugging would be needed, unfortunately, it would mean ideal OS found in country of Utopia only.

Whereas it is more like the State of Confusion (Capital: I don't Know!)

johngalt said:

Whereas it is more like the State of Confusion (Capital: I don't Know!)

Redmond ?

CountMike said:

Redmond ?

No, the city is named I don't know (it's a pun).

Besides, it's Cupertino I'd pick over Redmond for that capital anyway :rotflmao: