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, @08:20AM
You are contradicting yourself. That has not killed Exchange Server off yet.
I used to work as a sysadmin, and I can tell you that every single time an email disappeared, an Exchange Server was involved. While email is not officially guaranteed anything, the protocol does make it really hard for a mail to get lost. The sending mail server does not remove a mail from the queue before the next hop mail server explicitly has acknowledged and taken responsibility for it.
We used email for some automated data exchanges (no human involved, e.g. from one financial system to another), and the only times mails were lost... Exchange Server.