I have been struck with the infamous update wait at a bad time on a PC without its updates managed as well, and it most certainly pissed me off to no end but in a corp env you can manage that all no differently in Windows 10 than in previous versions.
For the env’s that don’t have it managed, (my opinion is irrelevant) I do understand the scenario MS are in. If they don’t “help” you, then somehow “they” get labeled for producing poor software. Its ridiculous really but I see their dilemma and I can understand how they arrived at the current implementation. I disagree with the idea that it hides it, I do think it manages it for you when it sees you have not done so explicitly (with SCCM etc). It can’t read minds and if no infrastructure is in place, it chooses a default which is simply to err on the safe side. From: [email protected] [mailto:[email protected]] On Behalf Of Jonathan Link Sent: Wednesday, January 18, 2017 10:22 AM To: [email protected] Subject: Re: [NTSysADM] Microsoft announces Windows 7 is a security disaster. You mean MS leveraged pure FUD. The author is simply trying to expose the FUD. Yeah, every piece of software gets updates. Get that. Software shouldn't hide the fact that it has been updated or in the process of updating. On Wed, Jan 18, 2017 at 12:16 PM, Joseph L. Casale <[email protected]<mailto:[email protected]>> wrote: Couldn’t agree more, I don’t do today what I learned had a better way to do yesterday. What that author simply leveraged pure FUD to describe was every piece of software ever written. From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Kent, Mark Sent: Wednesday, January 18, 2017 9:51 AM To: [email protected]<mailto:[email protected]> Subject: RE: [NTSysADM] Microsoft announces Windows 7 is a security disaster. All software is a work in progress.
