Microsoft explains why it delayed Windows 10 version 1803 release
Microsoft planned to release the Spring Creators Update for Windows 10, Windows 10 version 1803, last Tuesday on the April 2018 Patch Day.
The company decided against the rollout of the new version of Windows 10 in what seemed like a last minute attempt at preventing that a buggy release hit consumer systems worldwide.
Microsoft did not reveal back then why it decided to delay the release of the new version; in fact, the company never confirmed that April 10, 2018 was the day that it planned to release Windows 10 version 1803 to the public.
Rumors started to spread quickly after journalists with sources inside Microsoft started to claim that Microsoft delayed the release. While most experts agreed that the delay must have been caused by a larger issue that Microsoft detected in the last minute, speculation ranged from a serious security issue to bugs that decreased system stability.
Microsoft revealed yesterday evening on the official Windows Experience blog why it had to delay the release of the Windows 10 Spring Creators Update:
As Build 17133 progressed through the rings, we discovered some reliability issues we wanted to fix. In certain cases, these reliability issues could have led to a higher percentage of (BSOD) on PCs for example. Instead of creating a Cumulative Update package to service these issues, we decided to create a new build with the fixes included.
Microsoft noticed a bug that caused an increase in reliability issues on machines build 17133, the build of Windows 10 version 1803 that Microsoft selected for distribution to release systems.
The bug led to an increase in Blue Screen of Deaths according to Microsoft and it may have caused other issues as well as Microsoft gives BSODs as an example but does not reveal other issues the build may have caused.
Microsoft could have pushed a day zero cumulative update for the operating system if the bluescreens and other issues occurred during use and not during boot or installation.
Closing Words
While I don't have access to all the facts, I think that Microsoft did the right decision in postponing the release of the next Windows 10 feature update. Windows customers don't lose anything as they may continue to use the version of Windows 10 that is installed on their devices.
Past releases have shown that even smaller Windows updates result in an increased number of bugs and issues that Windows users experience after installation. Bigger feature updates are no exception to that,
Related articles
- Block Windows 10 Updates with StopUpdates10
- How to delay the Windows 10 Spring Creators Update
- Windows 10 "keylogger" setting moved in Windows 10 Spring Creators Update
Thank goodness I blocked all updates since 13…14 months now, and don’t have to worry for a moment, what damage Microsoft may do next…..just so I can have one of their latest “useless” bloat features.
Stability is all that matters to me.
Likewise. It’s 2018 and you shouldn’t have to waste time and energy worrying about whether or not a new build will break something on your system every time an update comes along.
I agree we are in the 21st century the upgrades should be working. My tablet has win 10 home and I cannot turn off the update to version 1803. It just keeps trying to upgrade with no errors. It does the restarts and then restores the previous version 1709. My Destop has win 10 Pro and I have it delayed for 90 days. I wish I could set for the 22nd century. LOL
Windows is not a priority for Microsoft anymore.
There will be more “delays” in future.
Microsoft has moved on to more profitable projects.
Microsoft just announced the launch of Linux-Powered Azure Sphere Initiative to Secure IoT Devices.
Yes, Microsoft Linux..
Thank goodness I blocked all updates since 13…14 months now, and don’t have to worry for a moment, what damage Microsoft may do next…..just so I can have one of their latest “useless” bloat features.
Stability is all that matters to me…
Martin, apologies for the duplicate comment, but for the third time in recent days, your commenting system has timed out, with a big error….then leading to reposting, then leading to duplicate! Having said that….right now, no comments are showing on this thread at all….yet a few mins. ago, there were three showing!!
Since our business is to sell and service PC’s, I rejoined the Windows Insider program on the fast ring, using Paul Thurrott’s “Magic Window” method, to install the new build and check it out on my laptop. There were no surprises. No new apps, no changes to my settings. It might be the smoothest feature update yet. If interested, check out Thurrott’s tip: https://www.thurrott.com/windows/windows-10/156650/new-redstone-4-rtm-build-resets-magic-window
Makes no diff here, I may stay on 1703 til 10-9-18 when 1809 rolls out :p
Thankfully I am on Windows 7 and happily enjoying all the things I need without bloated regular 900 MB updates and 4 GB “upgrades” ruining my set-up every few days. I think I will avoid Windows 10 till they realize this “service” and continuous huge updates thing isn’t working. :)
Updates are monthly, and upgrades are twice a year.
If I’ve told you ONCE, I’ve told you a THOUSAND times, don’t exaggerate! :)
Compared to the service packs from prior Windows versions, updates for W10 are relatively frequent and don’t undergo extensive testing before release.
The question is, “How come M$ did not catch the BSOD bug earlier since Build 17133 for Win 10 1803 RTM had already been released some weeks ago for Alpha-testing by the Windows 10 Insiders’ Fast and Slow Rings.?”
Most likely, it’s because the number of Win 10 Insiders has dwindled a lot since the novelty of being first-in-line previewers during the early 2015 has already worn off.
……. Today, most Win 10 Insiders are IT Admins doing free-testing for M$’s feature updates/upgrades and cumulative updates on about 10% of their Win 10 machines before actual deployment of the updates/upgrades company-wide.
Imagine if this BSOD bug for Win 10 1803 RTM had not been caught last-minute by M$ = many Win 10 Home users get the BSOD when forced auto-upgraded to Version 1803 by M$ as free Beta-testers.
Expect more of this bug scenario for future Win 10 Versions and cumulative updates unless M$ reinstates her QA or Update-Testing Department.
Who cares…
Me!!
Clearly you cared enough to click over here and leave a comment. :D
This is what happens when you fire all your software testers and rely on home usrers to do s/w testing.
Remember, the rapid twice-per-year Win 10 upgrades is mainly for M$ to prevent Win 10 license buyers from using it for about 10 years until EOL, like how they previously could with Win XP and Win 7.
Eg companies that buy Win 10 Ent Volume Licenses can no longer use it for about 10 years unless they have also bought additional 3-year Software Assurance(SA or Upgrade Insurance) or monthly/yearly subscriptions or the twice-as-costly LTSC/LTSB edition or convert their purchase to a lease Enterprise Agreement which comes with mandatory SA.
……. Without paying the above ‘extra ca$h’ to M$, they can only use Win 10 Ent for about 2 years since each Win 10 Version has an EOL of 18 months only.
For Win 10 Home & Pro license buyers, their computers will likely be made obsolete by M$ after reaching 4 to 5 years old because of OEM hardware device being EOL’ed, ie the 4 to 5 yo Win 10 Home & Pro computers can no longer be updated or upgraded, … similar to how Apple’s iOS upgrades have made 4 to 5 yo iPads and iPhones obsolete or un-upgradable.
……. Since Win 10 was only launched on 29 July 2015, expect many 4 to 5 yo Win 10 Home & Pro computers to be un-updatable and un-upgradable from 2019 onwards.
“Windows 10 as a Service”.? = No thanks. Staying on “Win 7 as a Product”.
Settings/Update & Security/Advanced Options/Defer feature updates: set that at least to 30, for peace of mind…
I am anticipating the spring update! I’ve often wondered if the complainers currently use Windows (7, 8, or 10), and if so, why do you stick with it? I would think that if Windows was hated so much, folks would have moved on by now. Just curious…
I have a friend who runs down MS constantly, yet his OS’s for the last 10 yrs? All Windows. Granted MS seems very useless and stupid sometimes, especially their ‘update’ system of things, but to me maybe it’s also a case of having such a huge user base (1 billion +) means it’s virtually impossible to get their arms or head around all of it and do everything nice and smooth and in perfect control.
I will tell you why I am sticking with it. And I think this is not only my case. I stick with it not because of the operating system. I stick with it because most of the software and games I have bought work only on Windows. Windows is just the bridge for my software and games. In reality it’s a monopoly, I can’t use them anywhere else. I have spent a lot of money on my software and games and not using them is not an option for me. I would definately won’t miss WIndows as an OS.
I am using Windows 7 sp1 with updates blocked in the last 3 years. It is stable with 90% of portable apps. It “just works”.
Will switch to MacOS in the near future.
It’s not like many consumers have a choice with regards to desktop operating systems. Unfortunately Linux is rarely used in workplaces and doesn’t support a lot of the programs compatible with Windows. MacOS is more costly and has more-or-less similar issues with Linux when it comes to software.
Those “complainers” may simply be users who are stuck with Windows for one reason or another. They probably figured the least they could do is vent about Windows 10’s issues in hopes of the unlikely scenario that Microsoft begins changing their tune.
The only reason MS is still relevant in the consumer space is because of components like Win32. The day MS abandons them is the day you can expect people to jump ship.
While I applaud Microsoft for intervening at the last minute this doesn’t excuse all the other times they pushed out flawed and unnecessary updates to consumers. It was bound to happen after they stopped caring about quality assurance.
This is precisely the reason why I’m no longer in a rush to upgrade to a newer builds: they’re buggy as hell during the initial roll-out. To users wondering whether now is the right time to upgrade I’d recommend waiting until more issues with version 1803 have been addressed, which will take at least a few weeks or months.
The only updates that should be required are those relating to security. With the exception of that, most users couldn’t care less about Microsoft’s “modernization” of Windows and just want a computer that works and gets the job done.They didn’t ask to be guinea pigs for an operating system that seems to be perpetually in beta.
After more then 20 years of Windows, this year I gave it up. Way too much problems with 10. Everytime updates that cause more problems then they solve. Upgrades create often havoc. Farewell, Windows as a ‘service’ isn’t for me. And many people around me think the same. I use a Mac right now for production work. Other systems here are in the process of being transferred to Ubuntu. Unfortunately, for Linux there is still no Office 365. I don’t need it, but employers often demand it because of stupid templates. That’s what the Mac is for. Microsoft seems to have lost its understanding with customers completely since Windows 10. :-/