So did anyone get spring creators update?

Faith said:

Microsoft is an American company so they use the seasons based in America. They can call it the Aussie Update for all I care, as long as the update is good an stable that what matters. It's nice to see that they take action for these mistakes before releasing it en masse.

The point is they spend loads of PR trying to show how global they are and immediately destroy that image by use of parochial names. It is just a fact of life, they look after US citizens way ahead of rest of the world. Try buying Windows 10 outside US for same price (allowing for tax differences) as US citizens for example.

EdTittel said:

Yes, Zac Bowden's Windows Central story has indeed spawned a raft of "me-too" follow-ons. Funny how he, and nobody else, can cough up any details on what the nature (or even focus) of the vaguely identified "blocking bug" might be. We'll just have to wait and see what changes by the time 1803 rolls out. I hope somebody will also do some forensics on the two different windows images to see where the differences lie.
--Ed--

What is odd that MS will not comment on this or the fact that their fix 17134.1 is also flawed.

Josey Wales said:

What is odd that MS will not comment on this or the fact that their fix 17134.1 is also flawed.

Why should they?

17134 is an Insider version and MS state categorically Insider versions may have bugs. I find nothing odd about it at all - just par for the course.

If they had officially announced 17134 as being release version, then some explanation might be warranted.

cereberus said:

Why should they?

17134 is an Insider version and MS state categorically Insider versions may have bugs. I find nothing odd about it at all - just par for the course.

If they had officially announced 17134 as being release version, then some explanation might be warranted.

It should at least be told to the insiders that are testing it. The build is not even in The Hub.

Redbatman said:

Maybe this will teach them that instead of overhauling Windows 10 every six months, just leave it alone and concentrate on making a stable OS.

Yep, maybe they should just do it once a year.

Redbatman said:

Maybe this will teach them that instead of overhauling Windows 10 every six months, just leave it alone and concentrate on making a stable OS.

The articles suggesting it will be delayed again had no evidence, and in fact the issue they cited has aleady been fixed in Skip Ahead. So a lengthy delay is almost certainly not the case.

People keep saying bring out updates less frequently. No matter how much testing MS and Insiders do, many bugs do not get detected until OS is out in the wild.

Reality is you will just get a lot more updates all in one go with proportionally more undiscovered bugs and if solution requires a build upgrade, longer time to get fix out there.

The real solution is to allow all users even on Home to defer updates for up to a year. That way, the more cautious can wait whilst "go for it" users trail blaze the build, unselfishly benefiting the more cautious who wait until the teething issues get resolved.