A new build could now be released next week

Jul 20, 2018 05:00 GMT  ·  By

Microsoft has recently announced that it won’t be releasing a new Windows 10 Redstone 5 this week, as the company most likely came across a blocking bug that needs to be resolved before pressing the go-ahead button.

In a post on Twitter, the official @WindowsInsider handle revealed that the target is now next week, so users enrolled in the Fast ring still has a few more days to wait for a new release.

“The data from Selfhost is in and… we won't have a new Fast ring build this week. We're already on track for a few code changes and are looking forward to next week!” the account tweeted.

Windows 10 Redstone 5 in stabilization phase

While many are eager to try out a new Windows 10 build, it’s important to know that Redstone 5 has already entered the stabilization phase, as the company advances towards finalizing this release.

With Redstone 5 nearly feature-complete, Microsoft is making changes to the way builds are pushed to Windows insiders. The Skip Ahead ring has been reset, and users will soon start getting builds as part of the RS5_RELEASE branch, which signals that we’re getting closer to the final development stages.

While the focus on new features will be gradually reduced, Microsoft has one major bug to address in the next build: the recovery option no longer works in Windows 10 Redstone 5, and this prevents users from returning to a previous version.

“We are currently working to resolve a known issue in Build 17713 that is causing Window Recovery Environment (WinRE) to be inaccessible and causing Recovery/Reset scenarios to be blocked. ‘Reset this PC’ and ‘Advanced Startup’ options under Settings -> Update & Security -> Recovery are affected and not working as designed. As recovery is critical we anticipate resolving this issue in the next build release,” the Windows team said in the release notes of the previous build.

If everything goes right, a new build should land on Tuesday or Wednesday depending on how fast the blocking bug is resolved.