Jump to content

Recommended Posts

  • FPCH Admin
Posted

The number one complaint people have about Windows 10 is that it forces patches down their throat. Good! There are too many security dolts using Windows who are making the net unsafe for all of us.

 

The Internet needs a warning sign that reads, "You must be at least this smart to use the net." Well, we'll never get that, but Microsoft has made one good step in that direction. With Windows 10 Home Microsoft is implementing automatic patching.

 

05991960ef4f9d10b02790df2d62ade9.jpg

 

 

Automatic Windows 10 patching is a good idea.

 

 

That's great news, but many users hate Microsoft for this Big Brother approach. Anyone who's read most of my work, knows I've disliked many of Microsoft's moves, but this one is a good one.

 

Why? Because year after year it's been shown that most users can't be trusted to keep their systems up to date. That, in turn, means that millions of PCs are pwned every day by malware using bugs, which were patched ages ago.

 

Most botnets are powered by unprotected Windows systems and that, in turn, means all of us get attacked because clueless people won't update their systems. Look no farther than how the obsolete Windows XP now powers a disproportionately large number of botnet attacks.

 

In short, clueless Windows users are one of the biggest reasons why there's so much crap and trouble on the Internet.

 

 

So, like it or lump it, if you're using Windows 10 Home, your system is going to be updated when Microsoft says it's time. The Windows 10 Home EULA now reads: "You may obtain updates only from Microsoft or authorized sources, and Microsoft may need to update your system to provide you with those updates. By accepting this agreement, you agree to receive these types of automatic updates without any additional notice."

 

That means you're computer is going to be patches whether you like it or not. Specifically, if you're using Windows 10 Home you're going to be on the Current Branch. This, in turn, means you're going to get any new features, fixes, drivers and security updates via Windows Update on Microsoft's schedule. The only choice you'll get is whether you want to apply the new code right now or later. That's it.

 

 

In all fairness, the problem isn't just security-stupid Windows users. Some Windows users find the operating system overwhelming.

 

ZDNet's Jason Perlow told me, "It's the 'I saw a weird prompt asking me to update and I am scared' issue. My mother-in-law is one of those types. With Windows 7 and 8.x I had to remote in with TeamViewer to ensure she was patching her machine, and she would even email me or call me on the phone when she got an update prompt. Transparent patch management has been a part of data-center/server IT practice for years; it's high time the end-users got on this train. End of the day the users shouldn't even have to think about scary prompts or be computer experts. The tech should just work for them."

 

 

She's not the only one in that boat. For people like that, I recommend Chromebooks. They've been automatically updating for four years now. And, what a surprise, there hasn't been a single major malware attack on any of them in the four years they've been around.

 

That said, automatic updates aren't a perfect solution. I don't pretend it is. Unlike ChromeOS, where there's only a few dozen systems, there are thousand of different PC models. Historically, there have been way too many Windows patches over the years that break working systems. Even so, automatic updates are better than having millions of out-of-date, unsafe systems on the net.

 

Still, as Ed Bott, ZDNet's resident Windows expert, said, "On the other side of the equation, making this decision means Microsoft takes on a major responsibility to not screw things up. They have to earn the trust that auto updates will work."

 

While Microsoft, "seem to have gotten better than they were say 18 months ago [there was] a defective patch every week," said Bott. Microsoft must improve their patch quality assurance. Bott concluded: "This is a move that has to happen, and some transitional pain is inevitable and cooperation on both sides (Microsoft and its customers) [is] essential."

 

If you're running Windows 10 Pro, you -- or more likely, your system administrator -- will decide how you get updates. You can be on the Current Branch with its automatic update or Current Branch for Business (CBB). With CBB, you can delay patches. The only way you'll get complete control over Windows 10 is if you're running Windows 10 Enterprise with for Long Term Servicing (LTS).

 

What if you can't stand this idea of patches being shoved down your throat? Well, Microsoft isn't publicizing it, but there is a Windows 10 troubleshooter package to give you more control. It's called "How to temporarily prevent a Windows or driver update from reinstalling in Windows 10," KB3073930, This enables you to hide or block Windows Updates and, the most likely source of Windows 10 patch problems: Driver updates.

 

Not enough control for you? You want real power over your system? Well, come on over to Linux. The operating system, Mint 17.2 in particular, is fine. Otherwise, I don't want to hear about how unfair it is that Microsoft is pushing updates on you. Years, decades, of misuse has shown that most users can't be trusted with basic security.

 

Source : zdnet

~I know that you believe you understand what you think I said, but I'm not sure you realize that what you heard is not what I meant.~

~~Robert McCloskey~~

  • FPCH Admin
Posted
Years, decades, of misuse has shown that most users can't be trusted with basic security.

 

This kind of says it all.

~I know that you believe you understand what you think I said, but I'm not sure you realize that what you heard is not what I meant.~

~~Robert McCloskey~~

Posted

I'm a bit, for and against...... I can see both sides of the argument.

 

The number one complaint people have about Windows 10 is that it forces patches down their throat.

In all fairness, I think most of this is down to mistrust of windows updates.

If there's a serious error with a windows update.... everyone gets hit.

I'm sure if they had thought this through properly, they could have given users the option of delaying updates for up to 7 days.

Then if there was a big problem, users that hadn't yet been affected could turn off the updates until a fix was made available.

 

First time there's a big crash, someone will try fetching a law suit against M$ because they'll state they had no option but to accept the update.

I'll put money on that.

 

Why? Because year after year it's been shown that most users can't be trusted to keep their systems up to date. That, in turn, means that millions of PCs are pwned every day by malware using bugs, which were patched ages ago.

Can't argue with that.

I still see systems that don't even have SP1 installed on Win7 systems.

 

Microsoft isn't publicizing it, but there is a Windows 10 troubleshooter package to give you more control. It's called "How to temporarily prevent a Windows or driver update from reinstalling in Windows 10," KB3073930, This enables you to hide or block Windows Updates and, the most likely source of Windows 10 patch problems: Driver updates.

Seems more of an after thought.... but at least it's something.

As long as the system can boot up so that the troubleshooter can be run.

  • Like 1
76c90dd0e79a714317a8daeecc1584d2.png

Posted

This is why I say there should have been a 7 day deferral option in the Windows Updates....

 

20 Windows Automatic Updates from hell

 

November 2001: The UPnP patch debacle

April 2004: Windows 2000 bricked

April 2006: The pretax predicament

April 2006: Windows Genuine Spyware -- er, Advantage

August 2006: The IE patch that created a new buffer overflow hole in IE

December 2007: Internet Explorer crashes on sites with lots of graphics -- like msn.com

April 2008: Quicken suddenly stops working

All through 2009, 2010, 2011: Bad .Net patches

March 2009: The XP AutoRun blocker that didn’t

December 2010: Patch brings down Task Scheduler

January 2011: A reliability update that wasn’t

April 2012: TurboTax won’t print

May 8, 2012: Duqu patch installation failure

February 2013: Blue screens on Internet Explorer 9

April 2013: More blue screens

August 2013: The biggest, baddest bungled batch ever

November 2013: Outlook 2013 gets special treatment

May 2014: Windows 8.1 Update won’t install, Microsoft backs off its deadline

August 2014: Blue screens all around, Microsoft recommends you manually yank the patches

December 2014: Roughly a quarter of all the patches this month generated problems

  • Like 1
76c90dd0e79a714317a8daeecc1584d2.png

Posted
Well I'm gonna pick on you Allheart55 just because you said your for it. So how do you troubleshoot tomorrow when you box won't work? You have no idea what happened or where to start. This is the reason I am totally against pushed updates. They are a techs nightmare! As far as users not installing them?? Well those people can probably be socially exploited into clicking something that loads rogue software regardless of patches. So my view on this is like the locks on your car, yes they stop the honest people but someone can still break a window and steal your car.
  • Like 1
  • FPCH Admin
Posted
There is a way to delay the Windows 10 updates, Gimbo, so I'm not overly concerned with it at this point.

~I know that you believe you understand what you think I said, but I'm not sure you realize that what you heard is not what I meant.~

~~Robert McCloskey~~

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...