Microsoft has never said anything publicly about the next release of Windows 10: it did not communicate an exact launch date, and it did not even confirm the name - Windows 10 Spring Creators Update. That name only showed up on several occasions to users that are members of the Windows Insider program. Most Windows insiders assumed from the little information that was available to them, that April 10th was the launch date. April 10th has passed, and this release was not made available to the public. Here's why:
Windows 10 Spring Creators Update may have been delayed by a security bug which was discovered late in the release process
Microsoft has not said anything about the launch date and why it did not release Windows 10 Spring Creators Update yesterday. However, it did launch a new build for Windows insiders, which fixes several security flaws:
Addresses a PDF security issue in Microsoft Edge.
Addresses an issue that, in some instances, prevents Internet Explorer from identifying custom controls.
Security updates to Internet Explorer, Microsoft Edge, Microsoft scripting engine, Windows kernel, Microsoft graphics component, Windows Server, Windows cryptography, and Windows datacenter networking.
These security updates may be the reason why Microsoft delayed the release of Windows 10 Spring Creators Update.
Windows 10 Spring Creators Update
Windows 10 Spring Creators Update release date is still unknown
Yesterday, Microsoft did not release any statements about when Windows 10 Spring Creators Update will come. Considering the cadence of releases for the Windows Insider program, and their release notes, it is clear that we should have this update soon. If everything goes well, April 17th should be the release date. But this is speculation on our part, based on the little data that we have. Also, some websites have started speculating that the name will be changed from Windows 10 Spring Creators Update to Windows 10 Version Next, or something else. It remains to be seen whether this will also happen. If it does, we will update all our materials about this release, to reflect this change.
What do you think about this delay?
We apologize for misleading you about the release date of this update. We published several materials about April 10th being the launch date, based on the little data that was available publicly. We will keep you posted when Windows 10 Spring Creators Update is released to the public. Until then, leave a comment below and express your opinion about this delay. Were you eagerly awaiting for Windows 10 Spring Creators Update to become available on April 10th?
I welcome a delay in an update when it will to prevent a buggy release. Do it right, do it once instead of following up with endless patches.
BUT, as has already been pointed out, MS should be more transparent. They force us to update, so they have to open about what is happening and when. People need to be able to plan their lives, do backups before these major updates fail to install. People who have not applied major updates since 1607 / Anniversary update have been getting prompts from MS that support for 1607 ended Apr 11. So some of them wanted to jump directly from 1607 to 1803. But now they can’t and they are not supported …
The naming nonsense has to end too. First they use a “secret” name, like Redstone 4 for this release. Then they start releasing various preview “build” and “version” numbers, finally they settle on a “version” number and “public” name like “Spring Creators Update” AND abbreviation “SCU”. At least that what they did with the “Fall Creators Update”. Now they tell us the “Spring Creators Update” is not the name … come on! It is hard enough to match the various public reports from MS and the media during development without them adding another twist to the name game.
They should also add the “public name” to any place they display the build and version numbers, like the WINVER dialog. And they should add a “copy” button to the Winver dialog so people can just copy and paste their full version information when they are asking for trouble shooting help.
Ciprian Adrian Rusen ·
I agree with what you are saying. Your arguments are spot on.
Sarah ·
Maybe these don’t apply, but I received four (4) updates (all successfully installed on 4/10/18)
They are:
•2018-04 security update for adobe flash player for windows 10 version 1709 for x64-based systems (KB4093110)
•2018-04 cumulative update for windows 10 version 1709 for x64-based systems (KB4093112)
•security update for Microsoft Office Compatibility Pack Service Pack 3 (KB4018354)
•security update for Microsoft Office Compatibility Pack Service Pack 3 (KB4011717)
I wish I could have simply uploaded a screen print for you because, of course, any SETTINGS window will not allow us to copy/paste.
Joe BagO'Donuts ·
we shouldn’t have to speculate, Msoft should be more transparent
Ciprian Adrian Rusen ·
Yes. That is true. Their communication could use some improvement.
Discussion (5)
I welcome a delay in an update when it will to prevent a buggy release. Do it right, do it once instead of following up with endless patches.
BUT, as has already been pointed out, MS should be more transparent. They force us to update, so they have to open about what is happening and when. People need to be able to plan their lives, do backups before these major updates fail to install. People who have not applied major updates since 1607 / Anniversary update have been getting prompts from MS that support for 1607 ended Apr 11. So some of them wanted to jump directly from 1607 to 1803. But now they can’t and they are not supported …
The naming nonsense has to end too. First they use a “secret” name, like Redstone 4 for this release. Then they start releasing various preview “build” and “version” numbers, finally they settle on a “version” number and “public” name like “Spring Creators Update” AND abbreviation “SCU”. At least that what they did with the “Fall Creators Update”. Now they tell us the “Spring Creators Update” is not the name … come on! It is hard enough to match the various public reports from MS and the media during development without them adding another twist to the name game.
They should also add the “public name” to any place they display the build and version numbers, like the WINVER dialog. And they should add a “copy” button to the Winver dialog so people can just copy and paste their full version information when they are asking for trouble shooting help.
I agree with what you are saying. Your arguments are spot on.
Maybe these don’t apply, but I received four (4) updates (all successfully installed on 4/10/18)
They are:
•2018-04 security update for adobe flash player for windows 10 version 1709 for x64-based systems (KB4093110)
•2018-04 cumulative update for windows 10 version 1709 for x64-based systems (KB4093112)
•security update for Microsoft Office Compatibility Pack Service Pack 3 (KB4018354)
•security update for Microsoft Office Compatibility Pack Service Pack 3 (KB4011717)
I wish I could have simply uploaded a screen print for you because, of course, any SETTINGS window will not allow us to copy/paste.
we shouldn’t have to speculate, Msoft should be more transparent
Yes. That is true. Their communication could use some improvement.