Microsoft Delays Windows 10 Spring Creators Update Because of 'Higher Percentage of BSODs' (bleepingcomputer.com)
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.
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.
Windows 10 Spring Creators Update 2018:
Coming the Winter of 2019.
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!
I havn't seen a BSOD in Windows in over a decade now myself.
I have had major processes get stuck, slowing the PC to a crawl, forcing me to reboot to fix it. Random bits of hardware not detecting only for me to reenable it (Wi-Fi, Touchscreen mostly).
The last time I got a BSOD was over a decade ago and I think it was on Windows XP.
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
I've been using the latest Win10 update and my computer is justttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttt
Anons need not reply. Questions end with a question mark.
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.
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
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
This is why I have Windows, MacOS, and Linux computers at home -- hopefully at least one group of them works at any given time
Sounds like my system. Every month or so the Windows update messes up my wifi or my display driver. Generally takes anywhere from 30 minutes to 2 hours to get my computer back to working correctly.
This is probably because the new default is to just reboot when Windows crashes.
tl;dr: Windows doesn't "BSOD" anymore unless you explicitly ask it to display the BSOD screen.
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.
Om, nomnomnom...
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.