Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Share Post: G+ Digg Delicious Reddit Facebook Twitter StumbleUpon
Windows 10 Spring Creators Update Delayed: Should We Be Worried?
You are not allowed to view links. Register or Login to view.       Windows 10 Spring Creators Update Delayed: Should We Be Worried?

Microsoft discovers last-minute bug in Windows 10 update
Apr 14, 2018 07:29 GMT  ·  By Bogdan Popa ·  Share:      
Windows 10 Redstone 4, or as most people call it Windows 10 Spring Creators Update, was projected to launch on April 10, according to people close to the matter, as development has been finalized recently after Microsoft completed the typical steps ahead of a new OS feature release.

Windows 10 build 17133 has long been considered the RTM build of the Spring Creators Update, especially because it was the one that Microsoft pushed to all rings of the Windows Insider program, including the Release Preview, which only receives new builds before public launches.

As a result, pretty much everyone expected the Windows 10 Spring Creators Update to be ready and go live this week on Tuesday, the same day when Microsoft published Patch Tuesday updates.

Only that instead of a new OS feature release, the software giant actually published a cumulative update for build 17133 which included small bug fixes plus this month’s security patches.

Windows 10 Spring Creators Update is still nowhere to be seen and sources more or less familiar with the matter now talk about a delay that could push back the launch up to several weeks. Furthermore, it’s believed that Microsoft could even change the name of the update, so instead of the Spring Creators Update, it might end up using a totally different moniker.

Microsoft could not meet April deadline
If this substantial delay indeed happens, it means Microsoft could miss its target of launching the update in April as originally planned, also impacting the version number that the operating system was supposed to use. Windows 10 version 1803 is a direct hint at the compiling date, as the first two digits represent the year, while the other two are the month, in this case March 2018.

More recently, however, it’s been discovered that Microsoft compiled build 17134, so again, version number 1803 no longer makes sense.

The more interesting thing, however, is the reason why Microsoft actually decided to hold back the release of the still-called Windows 10 Spring Creators Update.

Basically, it all came down to a blocking bug, which technically means that Microsoft cannot develop a fix and address the problem in the existing build, but only compile a completely new build that would be shipped to users.

In other words, the company needs to begin the process of preparing the release of Redstone 4 from the very beginning and complete all the steps mentioned above. A new Windows 10 build could be shipped to users in the Windows Insider program in the coming weeks as well.

Many users rushed to install the Spring Creators Update outside of the Insider program either by building their own ISOs with official ESD files or by joining the Release Preview ring and then returning to the production ring.

Transparency. We need it.
While it’s not yet clear how Microsoft will deal with the bug on these systems, many are concerned their devices would no longer receive updates or be forced to perform a clean-install.

Without a doubt, rushing to install a Windows 10 feature release isn’t the best choice for production devices if the parent company itself hasn’t started the rollout, but on the other hand, this last-minute bug also raises questions as to how quickly users should proceed to actually deploying new Windows 10 versions.

Cumulative updates, which are supposed to be a lot less complex than OS feature releases, are known for causing an insanely big number of bugs on Windows 10 devices, and IT admins and tech pros are now afraid everything could get worse if an update like the Spring Creators Update doesn’t install correctly.

If we want to see the glass half-full, we expect nothing more from Microsoft than inspect the new RTM build thoroughly to make sure it doesn’t make the same mistake twice. This should actually guarantee flawless performance from the very beginning because otherwise, it would all be just a matter of time until customers start complaining about the software giant’s capability of delivering reliable updates for its products.

The other thing that Microsoft needs to do right now is to go for a bit more transparency and tell us what exactly happened and how serious it was the bug that triggered an OS update delay. Time will tell if this strategy would be embraced, but the longer it takes for Microsoft to do this, the more criticism and harsh words are likely to reach the web.

Forum Jump:

Users browsing this thread: 1 Guest(s)