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, Funny) by Anonymous Coward on Monday August 10 2015, @10:13PM
Fuck you M$.
I live Free.
On Win7
(Score: 0) by Anonymous Coward on Tuesday August 11 2015, @07:17AM
"Fuck you M$.
I live Free.
On Win7"
Win7 is open source now? Did I miss something?
(Score: 3, Funny) by wonkey_monkey on Tuesday August 11 2015, @07:22AM
Yes. You missed "the joke."
systemd is Roko's Basilisk