Windows 10 Spring Creators Update Delayed Because of Higher Percentage of BSODs

Adjust Comment Print

The reported build is from the RS4 branch, which caters the following Windows 10 update.

Supremo of the Windows Insider programme, Dona Sarkar, dropped a hint last night as to what might have occurred with the release of build 17134 to the fearless soldiers on the Fast ring.

Microsoft admitted yesterday that the reason it did not launch the Spring Creators Update for Windows 10 last week was because of technical issues the company encountered with the supposed final release.

According to Windows 10 sleuth WalkingCat, Microsoft appears to have renamed the Spring Creators Update -formerly known as Redstone 4- to the "Windows 10 April 2018 Update", a naming scheme that makes more sense.

Guggenheim Capital LLC Decreases Position in Comcast Co. (CMCSA)
The stock of Intel Corporation (NASDAQ:INTC) has "Sector Perform" rating given on Friday , August 28 by RBC Capital Markets. Cahill Financial Advsrs Inc, a Minnesota-based fund reported 19,547 shares. 107,800 are owned by Cardinal Capital Mgmt.

The discovery of build 17134 of Windows 10 last week came as both a surprise and a disappointment, with those looking forward to the next big feature update realizing that this nearly certainly meant a delay. These issues could have potentially led to more BSODs on PCs. 'In certain cases, these reliability issues could have led to a higher percentage of (BSOD) [Blue Screens of Death] on PCs for example.

Insiders can download the new build by Checking for Updates in Settings.

It would probably take another week for Microsoft to release today's build to all the rings to test it for any last minute issues. A "hustle" is another word for a con, and so perhaps Ms Sarker could have chosen a different word in relation to a product which has caused so much frustration for its end users. As Build 17133 progressed through the rings, we discovered some reliability issues we wanted to fix. It has no new features but simply corrects the problems in Build 17133 - which should have been the version that we saw being released as stable.

Comments