SoylentNews is people
SoylentNews
Microsoft's first cumulative update for Windows 10 - KB3081424 - is causing havoc for some users. How do I know this? Because I spent a good part of my Sunday morning dealing with it, that's how.
The problem, in a nutshell, is that the update puts affected systems into an endless crash loop. The update tries to install, gets to a certain point, fails, and then displays the unhelpful "We couldn't complete the updates, undoing the changes."
If it stopped there things wouldn't be too bad, but because Microsoft now forces updates onto Windows 10 users, the OS kept trying - and failing - to install the update, which in turn placed the system into a periodic crash/reboot loop that put quite a dent in my productivity.
To make matters worse, the tool that Microsoft released to hide or block toxic Windows 10 updates (as reported by my ZDNet colleague Ed Bott) didn't allow me to prevent this update from attempting to install. So I was forced to either abandon the machine until a fix was made available or try to fix it myself.
http://www.zdnet.com/article/windows-10-cumulative-update-causes-reboot-loop-havoc-for-some-users/
Submitted from IRC.
(Score: 2, Interesting) by Anonymous Coward on Tuesday August 11 2015, @02:03AM
due to software and hardware problems in Linux
It doesn't sound at all like the problem is "in Linux".
The problem appears to be in your hardware supply chain--specifically *YOUR* choice of vendors.
Clearly, *YOUR* RFQ did not specify the OS compatibility required.
...and have you contacted The Linux Driver Project?
Last I heard, they had HUNDREDS of guys waiting in line to make hardware Linux-compatible. [googleusercontent.com] (orig) [lwn.net]
Not accepting gratis labor is a sign of a really shitty vendor.
-- gewg_
(Score: 1, Insightful) by Anonymous Coward on Tuesday August 11 2015, @07:37AM
You're making the silly assumption that the hardware is new. IFF you get to spec out the hardware first - yes you can do that. If the hardware's already in place, replacing Windows with Linux solves nothing.
But you also assume that all hardware is available in some Linux form. Not so - there are real life commercial products with no Linux support and _no_ Linux alternative. Some medical equipment and industrial is not available in Linux form - some is still stuck with WinXP. Yes it's a vendor problem, but that doesn't make Linux the solution.
I know of one factory with assembly equipment running on an IBM 704 - which dates back to the '50s. If it works, don't mess with it. The cost of replacing all the equipment just so they could run a Linux PC would make no sense.
You live in a Linux world. I live in the real world.
(Score: 0) by Anonymous Coward on Tuesday August 11 2015, @08:13AM
In that case they probably have an IT department to take care of it, with testing and QA before rolling anything into production, so they probably won't be bitten by forced updates to the consumer version of an OS that was just released.