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: 0) by Anonymous Coward on Tuesday August 11 2015, @01:29AM
SP3 or SP6? The last Win2k release was SP6, SP3 was the Win2k point release updating the EULA after XP came out (Been to long to remember anything else about it except that it fucked up what packages you could uninstall and made the 2k license more like the XP one.)
(Score: 2) by MichaelDavidCrawford on Tuesday August 11 2015, @02:03AM
Im not always on the ball as to what updates have been released.
Yes I Have No Bananas. [gofundme.com]
(Score: 2) by captain normal on Tuesday August 11 2015, @07:22AM
Wow! Where have you been for the last 15 years? Welcome back to Earth.
Everyone is entitled to his own opinion, but not to his own facts"- --Daniel Patrick Moynihan--