Microsoft acknowledges permission problems with MS16-072 patches | Hacker News Reader

Microsoft acknowledges permission problems with MS16-072 patches

infoworld.com

25 pointsUdo9 comments

Unfortunately, these kinds of issues are normal for patch Tuesday since Nadella took over. His re-doing of QA at MS hasn't helped matters and perhaps is the cause of all these issues. I'm hoping they can get back to their old QA levels soon.

Lots of admins I've spoken to have added longer delays for more testing nowadays. That means a critical Windows update may take 4-8 weeks to get to desktops and servers now. I think MS is playing with fire here with its terrible QA and also making updates mandatory in Win10.

MS has effectively passed the testing it should be doing to its customers. If it wasn't for its monopolistic position, none of this would be remotely tolerable.

I agree with you except for the monopoly part. Chromebooks, Ubuntu, Debian are all viable options.

Well, for businesses that have invested and in a lot of ways locked into MS, its tough to move off.

For home consumers, definitely, its much easier.

All these are viable, and I use a handful of them- however, there's a lot of software that's windows exclusive, and if you're in a corporate environment chances are you're using a bunch of webapps that are IE exclusive. If you're a gamer, graphic artist, modeler, etc, you need directX.

Now, this is all becoming less of a problem (thanks vulkan!) but I would safely say MS has a monopoly still.

c'mon buddy, I hate MS as much as the next guy but this is a far cry from how bad things use to be, at the very least the patch can be removed.

I've been a sysadmin for over a decade now. Patches have never been this bad. Its incredible how there's a major problem pretty much every other month now.

Next time you have to rebuild a domain because of a patch that couldn't be removed, you let me know.

You're ignoring very real changes to the windows test org that happened over the last few years.

http://www.zdnet.com/article/microsoft-layoffs-operating-sys...

I think this is probably a deliberate change, not a bug.

Reply on news.ycombinator.com