BSOD

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.

More precisely, Microsoft says it encountered a higher percentage of Blue Screen of Death (BSOD) errors on PCs, the company's Insiders Program managers said in a blog post yesterday.

Microsoft says that instead of shipping the Springs Creators Update faulty as it was, and then delivering an update later to fix the issues, it decided to hold off on deploying the defective build altogether.

The OS maker says it will create and test a new Windows 10 build that also includes the BSOD fixes, and ship that one instead of Windows 10 Insider Preview Build 17134, the build that was initially scheduled to be launched as the Spring Creators Update on April 10, last week.

New naming scheme for Windows updates?

The delay also appears to have given Microsoft more time to think about its Windows 10 updates naming scheme.

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.

Last year, Microsoft said it planned to deploy two major Windows 10 updates per year, every April and September.

Having the month and year of each update in the name makes it easier for system administrators to track which updates they have installed, as opposed to using codenames such as the Anniversary Update, the Creators Update, the Fall Creators Update, or the Spring Creators Update.

At one point or another, sysadmins would have lost track of what update came before what, and patching would have become chaotic.

Related Articles:

Windows 10's "Controlled Folder Access" Anti-Ransomware Feature Is Now Live

Researcher Bypasses Windows Controlled Folder Access Anti-Ransomware Protection

Microsoft Says Windows 10 Spring Creators Update Will Install in 30 Minutes

Microsoft Releases Tool for Running Any Linux OS on Windows 10

Microsoft Admits It Incorrectly Upgraded Some Windows 10 Users to v1709