News for hackers. Stuff that matters.

A comment on The woes of Windows 10. Parent comment

Re:The woes of Windows 10 by eumoria on Thursday February 02, 2017 @02:31PM (#13553713)
Every time I hear about updates being "forced," yes, Microsoft did some shady things to trick non-tech people into the upgrade which I agree is shady. However any competent IT manager would know how to stop that from happening. Even a cursory google search shows you how to remove the windows update that starts the upgrade. Also all computers on a network domain will not auto update. Each time I read of an IT manager who says he/she was "tricked" into upgrading all I read is "Incompetent IT Manager Makes Massive Mistake"

EDIT: I should probably reference the single small command that stops the bugging notifications and upgrade. Open admin level command line:

wusa /uninstall /KB:3035583

[ Parent | on HN ]
Re:The woes of Windows 10 by Pica_soO on Thursday February 02, 2017 @03:34PM (#13554381)
Black UI magic, to shove users into a certain direction, that needs to be yanked from the registry and forbidden via group policies- and that can be defended?

You know a OS is in a bad spot, if it gathers followers, who attack criticizing experience reports and anecdotes. Who needs truth if one has beauty?

Windows job was to provide a easy, trap-free OS, one where you wouldn't spend weeks with a bomb-defusal kit, looking at the upgrades blowing up systems.

Well at least the victims of the landmine dont have to worry about shipjumping converts of the holy church of the foreboding fruit snapping at them for heresy.

[ Parent | on HN ]
Re:The woes of Windows 10 by Retr0spectrum on Thursday February 02, 2017 @02:46PM (#13553866)
Clearly something has gone very wrong when an IT manager allowing a software update is considered to be making a "Massive Mistake".
[ Parent | on HN ]
Re:The woes of Windows 10 by shubb on Thursday February 02, 2017 @04:51PM (#13555078)
Not trusting vendors is part of the job. IT departments will typically turn off automatic updates from vendors, and instead role them out in an automated way that they control.

If they are too slow in doing that, then they are doing it wrong sure. But Microsoft updates do brick computers, undo obscure enterprisy settings, or role out unevenly across your estate so people are on different versions. You want to see if that happens to someone else before you roll out.

This is even more true with windows based servers, where you'd probably want to switch in an alternative or do everything at 3am on Saturday morning.

[ Parent | on HN ]
Re:The woes of Windows 10 by Terr_ on Thursday February 02, 2017 @05:43PM (#13555650)
> Not trusting vendors is part of the job.

But at the same time, for an OS company being trustworthy is part of their job.

[ Parent | on HN ]
Re:The woes of Windows 10 by eumoria on Thursday February 02, 2017 @10:02PM (#13557313)
I do agree with this... Microsoft handled this terribly and the opt-out should have been obvious and permanent.
[ Parent | on HN ]
Re:The woes of Windows 10 by eikenberry on Thursday February 02, 2017 @04:47PM (#13555017)
Small companies like this usually don't have an IT person at all, let alone a manager.
[ Parent | on HN ]
Re:The woes of Windows 10 by wtallis on Thursday February 02, 2017 @05:04PM (#13555219)
> I should probably reference the single small command that stops the bugging notifications and upgrade.

Temporarily stops; that update didn't reliably stay dead.

[ Parent | on HN ]