Slashdot is powered by your submissions, so send in your scoop


Forgot your password?
Microsoft Operating Systems Windows IT

Microsoft Delays Windows 10 Spring Creators Update Because of 'Higher Percentage of BSODs' ( 108

Microsoft has admitted that it had to postpone the release of Spring Creators Update, the upcoming major update to its Windows 10 desktop operating system due to technical issues. BleepingComputer notes: 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.

Microsoft Delays Windows 10 Spring Creators Update Because of 'Higher Percentage of BSODs'

Comments Filter:
  • I find it quite disturbing that they were even considering releasing this obviously faulty build and fixing it later. Do they not care about the name brand? It's already got people pissed off as it is.

    • Well Microsoft haters will hate. Chances are this BSOD is a fairly rare condition, and sending out an update at would introduce the BSOD vs the additional benefits of the update is a decision that will need to be made.

      For all products there is a point where someone will need to say "this isn't perfect, but it is good enough". Because the cost of the flaw is minor while the improvements are great.

      So Microsoft did the responsible thing Considered releasing a product that could possibly BSOD, or make people w

      • > Well Microsoft haters will hate.

        /sarcasm Let's just label people and ignore the reasons WHY MS gets so much hate!

      • by Mashiki ( 184564 ) <> on Tuesday April 17, 2018 @12:32PM (#56452751) Homepage

        Wouldn't surprise me if it's related to driver rollouts. There's a lot of complaints in the fast and slow channels over MS once again deciding to force driver updates on everything. Not only was windows rolling back drivers in some cases, but rolling out drivers that people were using that made their system stable and then overwriting newer signed drivers with MS 'certified' drivers like on a new OS install. It's the biggest thread in the driver section and has been for quite awhile.

        • Yes. With each new twice-yearly release, all the Microsoft drivers have their dates bumped to match the OS build date, even when nothing is changed or fixed. Even if you block/hide a particular driver via Windows update, the "new" driver from the next build gets auto installed again.

      • Well Microsoft haters will hate. Chances are this BSOD is a fairly rare condition, and sending out an update at would introduce the BSOD vs the additional benefits of the update is a decision that will need to be made.

        For all products there is a point where someone will need to say "this isn't perfect, but it is good enough". Because the cost of the flaw is minor while the improvements are great.

        So Microsoft did the responsible thing Considered releasing a product that could possibly BSOD, or make people wait for a big set of improvements which could allow people to hack into their systems, or break something else. They figured the BSOD condition was common enough to not release it.

        The cost of the flaw is not minor to the poor sap whose computer is screwed with an update they aren't allowed to block even if they KNOW their computer will be affected by it. Give the OWNERS of the computers back the CONTROL of the computers which is theirs by rights as the OWNER of that machine.

    • Why do you think it was obviously faulty? "Higher than normal percentage of BSoDs" sounds to me like it takes into account BSoDs caused by non-Microsoft software and drivers. Microsoft can't be expected to hold up a release until they fix everyone else's buggy code. Using simple statistical analysis they determined that the % of BSoDs was higher in the new build, meaning there was likely a BSoD bug present in their own code, which they then rightly sought out to fix.
      • Higher than normal means that they pushed out earlier releases, despite causing a fair number of BSODs. The number of errors is just much higher this time around. The high number of issues caused by an automatic update should be near zero, even after accounting for third party software. And that really was the case for service packs in all earlier releases of Windows.

        The new updater constantly makes bad assumptions, especially regarding the layout and size of EFI system partitions. The number one cause

  • Well, That's Nice (Score:5, Interesting)

    by rally2xs ( 1093023 ) on Tuesday April 17, 2018 @11:25AM (#56452213)

    Meanwhile, the update that I got about 10 days ago broke the ability of this computer to do the "no password required" bootup. It would give an error message and tell me unless I logged out and then logged in myself, my creations wouldn't be accessible in the future. Or something like that. Ran a few diagnostics / fixes such as scannow and it passed fine. So now, rather than run around and try to find the cause, I'm just waiting for the next update to fix it. The laptop is working fine, no problems with no-password bootup. Its just that a month ago, while on a cross-country trek from Virginia to Arizona, something happened (probably another update) and the keyboard and touchpad stopped working. Then, 2 days later, it magically began working again. (Probably another update.) Win 10 computers are getting to be really unreliable because of the updates dicking with them all the time.

    • Re:Well, That's Nice (Score:4, Interesting)

      by ( 3412475 ) on Tuesday April 17, 2018 @01:31PM (#56453283)

      I'm not sure if sarchasm or an actual story. I like the comment either way. The fact a W10 computer can start updating itself without prompt or UI, when connected to whatever network (which might be a Starbucks for all we know), is one of the most scary things ever. And I don't mean security-wise, I mean: "here I go do my once-in-a-lifetime presentation to the money suits with my Windows laptop. YAY! FINGERS CROSSED hoping the fact I'm in a different time-zone with different busy hours, and the fact I didn't set this new WIFI to metered can doesn't get me a reboot, or that Delivery Optimization doesn't resource hog BITTORRENTING updates just as I'm about to seal the deal".

      • Both of my Win 10 problems are absolutely true, and I even forgot one. There was another one a few months ago with the laptop, a Surface Pro 4 that I bought last summer, that all of a sudden booted up with a completely black screen. Since I bought it at Best Buy last summer and also bought a 2 year "extended warranty", I just took it to Geek Squad and let them wrestle with it. They had it fixed in a few hours, so I picked it up that night. But the tech said that yes, another update went south, and cau

      • The fact a W10 computer can start updating itself without prompt or UI

        It can't, and hasn't done so since the first Windows 10 release. What will happen now is that you set active hours during which it will never restart, you also tick the notification box so all you get is a notification telling you that on your next restart it will update, and that will also tell you the exact time it scheduled for the out of hours restart, and even provide you with an option for delaying it, which you can for up to a month.

        Seriously if your presentation is interrupted due to a windows updat

        • So, this prosaic "presenter" will 90% of the times have a managed PC with Win10 Pro, and as likely have an enterprise management suite (e.g. Airwatch) enforcing policies through Administration Templates for Windows update and whatnot, which the user can't control. He won't be able to set any of those policies, and he won't ever get a prompt to an update his company doesn't even know might happen, well, "because Microsoft".

          And the way I talked about higging by p2p updates is pretty fair - if you don't know h

          • Funny your complaints are the same about my remotely administered Windows 7 machine. Just because you may not be the one who doesn't know how to use the settings in their computer doesn't mean that someone else isn't a complete buffoon. The problem is the same, you're effectively complaining about not knowing how to use settings which have a full paragraph dedicated to explaining each of them.

            Also the way you talk about CAs just shows you have fundamentally no idea what you're talking about, especially when

  • by PingSpike ( 947548 ) on Tuesday April 17, 2018 @11:27AM (#56452225)

    Windows 10 Spring Creators Update 2018:

    Coming the Winter of 2019.

  • by the_skywise ( 189793 ) on Tuesday April 17, 2018 @11:33AM (#56452253)
    I've got a SP4 and with whatever update they forced on me last week the windows all think I'm in vertical orientation after it sleeps and won't expand greater than the margin (even though I've left the keyboard attached, have the options set to desktop mode only and the desktop itself is still in desktop orientation!).
    The only way to fix it is a reboot!
    Microsoft - we updated your computer while you slept - figure out what we broke today! What fun!
  • by Gravis Zero ( 934156 ) on Tuesday April 17, 2018 @11:38AM (#56452279)

    I've been using the latest Win10 update and my computer is justttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttt

  • They aren't delaying it for BSODs. Why do they care. They release updates like that all the time.
    What broke is the user tracking software. That is why they are delaying it.
  • by RyanFenton ( 230700 ) on Tuesday April 17, 2018 @11:54AM (#56452365)

    What happens when they have buildings filled to the brim with software engineers working on projects/components, but each new component has a small chance of adding a new bluescreen on a subset of machines?

    The whole point of Windows 10 was supposed to be that it was the end-state, the stage where all further upgrades would be updates to this. But lashing another sail onto the boat doesn't seem to be adding the thust expected, or bring the income desired.

    They really wanted the Windows Store to be the future too - just like Metro was going to be the perfect union of touch-phone interfaces and desktop interactions (well, by forcing everything to just be touch-phone, and insulting anyone that disagreed).

    But no one uses Windows Store. It most certainly is not an improvement on the flawed Apple store or other marketplaces.

    Then there's the data gathering. I'm sure they market that information to folks (in aggregate) - but I'm also pretty sure that they aren't going to see the returns they might dream about for selling access to that information, compared to their dreams of being some super-Google.

    Probably the biggest source of instability has been the DRM and protection systems. Locks and keys designed to, well, lock things up on anything being off tend to... lock things up. And there's teams of teams constantly working on those.

    Windows is still a money machine. PC sales aren't at peak at the instant, but there's still mountains of money for selling OS licenses on most new systems.

    So, they bounce between ideas still - cross compatibility with XBox game images - but they link it with Windows Store, so it's basically like signing a cult marriage contract. Strait up ports of some games, but the same Store logic kills that idea. Tools to help manage things - but they keep making the interface Metro compatible, so folks drop it as soon as they can find a better tool.

    The overall story is that they still have folks there dreaming that their failed pet ideas are still the future, an unlimited income stream that just needs tweaking. They need to identify that, and get past those folks - especially if they're managers.

    Then be OK with just making the best OS they can, without trying to loop everything back into some infinite income stream. The golden goose is good enough - work on the nest, NOT a butcher shop.

    Ryan Fenton

  • At least Microsoft learned from the botched deployment of RS2 (aka Redstone-2, or the "Creators Update") which didn't work well on anything older than Skylake for several months. Looks like it is going to take them similar amounts of time to stabilize RS4 (Spring Creators Update... I wish they would just call it RS4 instead of coming up with meaningless marketing names) but at least they won't hold people's machines hostage in the meantime.

    This is a natural consequence of the new world order Microsoft estab

    • I would love to get a Enterprise edition as it doesn't contain all that telemetry bloatware. In fact, Enterprise is truly a successor to Windows 7 Pro.

      For those that are using Windows 10 Home and Pro, check out O&O ShutUp10 []. The real irony is that O&O is a Microsoft Gold Certified Partner LOL =)

      • I have Windows Enterprise.

        It's just as shitty as my Pro computers. Half the "privacy" features you think you can disable, break other essential parts of the operating system... like Windows Update.

    • So, the more you pay, the later you have to install their software.

      Odd. In most other markets, you'd pay a premium to be first.

    • I've never even seen the term RS2, but I much prefer the simple version numbers like 1709 with the month and year, even if the month code is a lie.

    • At least Microsoft learned

      But did they? You're talking about a supposedly tested release that pasted through the insider program was designated as RTM and then pulled on the day of public release.

      It doesn't sound like they learned anything. It sounds like they majorly dodged some bullet and their QC process is still as fucked up as it has always been. No surprise mind you. It took them close to 14 months to fix the problem turning on their own premium Surface Pro 3 computer when a Surface Pro 4 keyboard was attached, a device they n

  • diversify (Score:2, Funny)

    by Anonymous Coward

    This is why I have Windows, MacOS, and Linux computers at home -- hopefully at least one group of them works at any given time

  • When they laid off most of their QA folks []

    I get end-user testing, early preview releases are a good thing, I preach it and live it but frankly these wholesale massive semi-annual fuck-overs to add one or two "features" is annoying as fuck. Every time there's hardware compatibility problems, delays in releasing them because they're refreshing the whole fucking planet. I get that they want to unify frameworks, that's good but for god's sake stop with this 1GB+ downloads and installs that fail over and over aga

  • Am I the only one who thinks "agile" is a stupid metodology to use on an OS?
    It's supposed to be stable. How does this benefit Microsoft?
    • You're not. But how does this benefit Microsoft? That's not quite the right question to ask. Microsoft will benefit as long as people buy their products. Whether it has something to do with their stability remains to be seen.
  • it's OK by me if the update has a lower percentage of BSODs. You can just add some more in a point release.
  • I always remember a few years ago when they did.... Windows 8? They were bragging that the BSOD was gone........ ...Because it would now be red. Reminds me of when they got rid of the 360's red ring of death - by removing the ring.

Ya'll hear about the geometer who went to the beach to catch some rays and became a tangent ?