878 karma · joined October 5, 2016
You are better than 99% of users which is what this issue is about. You are a power user capable of looking after a machine. The problem the people who aren't.
However the former has a different security model and the latter is mainly run by experts. The point is moot.
> I don't know what you mean by "this has to be done", there is no obligation to apply updates. What if I want my computer to run a windows without updates ? Am I not entitled to use my own property as I so choose ?
If your machine becomes a botnet node and causes problems for other people, which is a big problem, then you forfeit the right. The same thing if your apartment leaks water into another one. Be a good citizen.
Failed updates, now that's the only valid part of your point. I've had a few and they weren't disruptive but this is just my case.
However this IS definitely an edge case and it is possible to turn it off. I have run a physical host as a build agent that has uptime of months on Windows 10.
This is administrative competence, not a problem with the product or the use case.
WSUS + Windows server is definitely fine for most workloads though.
That's a terrible analogy. I have been shaming people for bad security practices and self-righteous ignorance for many years (even before 9/11 ironically!).
I've seen too many people have been wrong and had a bad outcome including complete data loss and in one case livelihood being shot entirely. This isn't a random assertion from thin air. You can't trust people to look after their computers.
The global scale of it shows how the end user is less trustworthy than the vendor.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings
Set DWORD IsActiveHoursEnabled to 0.
In your case it should be possible to have a windows "branch" with just critical vulnerabilities patched with binary diffs or something rather than 680-odd Mb patch sets.
See update notifications? At the end of the day, restart and install the updates. It's not rocket science. It doesn't just hit patch Tuesday and then reboot immediately, shafting you. And it doesn't screw your workflow up.
Really this has to be done because even the best of us put it off eternally.
Windows only updates when you're doing something because you're putting everyone else at risk by not running the damn things in and you've had plenty of notice.
My knowledge came mostly from the BBC Micro Users guide and Advanced Users Guide initially. Eventually a dead relative, who I will be eternally grateful for their thought, left me a not insignificant amount of cash and I bought a then new BBC Master!
The books in question:
http://bbc.nvg.org/doc/BBCUserGuide-1.00.pdf
http://stardot.org.uk/mirrors/www.bbcdocs.com/filebase/essen...
This eventually made way for a PC and eventually in the mid 1990s, Linux and then I discovered my father had a 1st edition copy of "Programming C" stashed away in a junk box somewhere. Oh and O'Reilly books. I had crates of them at one point.
I've taken the liberty of taking a quick snap of a random page in "Arithmetic for the Practical Man" to include below for those poor people poisoned by modern textbooks:
http://i.imgur.com/Bg9OiiK.jpg (926KiB)
I see horrible modern behemoths of over a 1000 pages that leave you dazed, confused and full of facts but nowhere to go with them. EE textbooks are even worse on this front than your average mathematics text book. I've seen one proudly promoting over 1500 pages and 1000 illustrations, but doesn't even get as far as an opamp or discuss anything at system level.
From there he was given a calculus book, the title of which I cannot remember. I never got that far.
I suspect you have to at least follow the same path to have the same intuition.
I would rather see it used to leverage an opinion against back doors and surveillance culture but alas this is merely administrative incompetence and failure to either upgrade or airgap systems which have had a clock ticking on them and plenty of notice from the vendor to sort. The buck should stop at the trust IT directors as this was entirely avoidable with a properly managed estate.
Policy controls, poor patching and user education are the root cause of the NHS problems.
However if you want a real turd: Skype for Business. Everything starts with 20 minutes trying to work out if it's working or not which for a random subset of people the answer is nope.
Arrogance, showboating, non-science and anti-pragmatism are the biggest killers.