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) by frojack on Tuesday August 11 2015, @04:49AM
Crossing my fingers that the company IT department does not force us to upgrade to Win10.
In my day job, where we knew months ago that our software would work under 10, we still Like Windows7, but have no objection to Windows 10.
In fact, for end users we prefer it, because Microsoft has made it harder for end users to arbitrarily decide to install software in some random ass location, and started protecting the root of the drive (just like linux).
Everything we use, and everything we write works just fine under 10.
No, you are mistaken. I've always had this sig.