Microsoft Explains Windows 10 Redstone 4 Delay, Issues New Build
- Mehedi Hassan
- Apr 16, 2018
-
23
Microsoft is today releasing a new build of Redstone 4 to Windows Insiders in the Fast Ring today. Build 17134 is being rolled out to Insiders in the Fast Ring today after delaying the public release of Redstone 4.
Microsoft was supposed to release build 17133 — the rumoured, initial RTM build of Redstone 4 — to the public last week. However, the company internally demoted 17133 as the RTM build after finding a breaking bug. In a blog post today, the company noted that build 17133 included critical reliability issues that resulted in a higher percentage of BSODs on PCs which led to the delay.
Windows Intelligence In Your Inbox
Sign up for our new free newsletter to get three time-saving tips each Friday — and get free copies of Paul Thurrott's Windows 11 and Windows 10 Field Guides (normally $9.99) as a special welcome gift!
"*" indicates required fields
“Instead of creating a Cumulative Update package to service these issues, we decided to create a new build with the fixes included. This just reinforces that Windows Insiders are critical to helping us find and fix issues before releasing feature updates to all our customers so thank you,” Microsoft’s Dona Sarkar said in a blog post, explaining all the drama surrounding the Redstone 4 delay. Of course, it is possible there is a bigger reason behind Microsoft delaying the Redstone 4 release, but I personally don’t want to start any conspiracy theories for the time being.
Either way, Build 17134 will most likely be the Redstone 4 RTM now unless Microsoft runs into another blocking bug. Redmond is expected to start a public rollout of Redstone 4 by the end of this month, although that could change anytime.
Tagged with
Conversation 23 comments
-
skane2600
<p>I don't understand Microsoft's strategy with respect to insider builds. Rather than risk appearing to be late delivering certain features, why not wait until those features are actually implemented and you're ready to release before announcing anything? IMO, what is released in an Insider build and when it is released is entirely disconnected from the bottom line. These are self-inflicted PR problems.</p>
-
skane2600
<blockquote><a href="#263305"><em>In reply to warren:</em></a></blockquote><p>"What's the actual upside to being surprised by new features in your OS?"</p><p><br></p><p>I'd say it has little significance one way or the other unless those features are very complex and difficult to learn. In any case, I didn't criticize announcing features prior to RTM but rather announcing features and target dates for the incomplete releases of the Insider program.</p>
-
dontbe evil
<blockquote><a href="#263260"><em>In reply to skane2600:</em></a></blockquote><p><br></p><p>except it was never announced an released officially to the public from Microsoft … only to insiders</p>
-
skane2600
<blockquote><a href="#263369"><em>In reply to dontbe_evil:</em></a></blockquote><p>Your distinction isn't very meaningful. Anyone can read the blog post that describes the change in plans, not just insiders. In any case, the fact that we are discussing a delay at all suggests that MS's reputation can be harmed (if only among insiders) by premature announcing/scheduling of insider releases.</p>