Along with the release of Windows 10 Insider Preview Build 17134 (Redstone 4) with the Fast Ring, Microsoft has given a little insight into what went wrong with build 17133, that's thought to be the RTM build but was delayed due to a "blocking bug".

The release of Windows 10 Spring Creators Update was expected this month, nevertheless launch date will now be seemingly increasingly inclined to slip into May. Microsoft has stated build 17133 was proving problematic and also company says it wishes to fix problems now, rrnstead of after the fact.

The invention of build 17134 of Windows 10 last month came as both surprising and a disappointment, with those interested in the next big feature update if you know this most likely meant a delay. Announcing provide of 17134 to Windows Insiders about the Fast Ring, Dona Sarkar stated that the last-minute discovery of problems highlighted the significance the Insider program, and thanks participants due to their help.

Dealing with the buggy 17133 build she says:

As Build 17133 progressed through the rings, we discovered some reliability issues we wanted fix. In some instances, these reliability issues might led to a very high percentage of (BSOD) on PCs just like. Instead of establishing a Cumulative Update package to service these issues, we decided to create a new build while using fixes included.

Each of us know much more about the exact nature of the problem, we are seeing a change in approach from Microsoft. As a substitute for rushing to receive the update out and needing to issue a launch day patch -- something which can be immensely problematic on its own -- the company is instead opting to do its time guarantee that the RTM build that does ultimately are conscious of the light of day (whenever that one can) is as roughly perfect as it could reasonably be expected to be.