Windows Update - How will it change your system?

Anonymous
2016-10-14T16:11:13+00:00

You need to make a decision about where you want to be with your system.

My advice is to change the Windows Update (WU) setting to never.

It really depends on where you want to be with your Windows 7 system.

Woody Leonhard has described the situation something like this.  Note, I am using my own words here and describing it from my own perspective:

http://www.infoworld.com/article/3128983/microsoft-windows/how-to-prepare-for-the-windows-781-patchocalypse.html

Group A:  Roll over and just let MS install what ever they wish on your computer and just don't worry about privacy and the spyware they will install.  With this option you leave WU as Delayed start, and set the WU setting at Recommended.  This is the easy way and requires no effort or concentration.  You just let happen what will.  This is essentially what you have with a Windows 10 system.

Group B:  Refuse to accept any updates except Security ones.  In that case you follow my initial recommendation and leave WU set at Never.  You get the Security only updates from the "catalog".   There is risk here in B.  You are trusting that MS will not put anything in that group that does things you do not want done. A sort of level of trust in MS that I am not sure they deserve.   Keep in mind that they have done the same thing with this set of updates they did in the main one.  It is all one agglomeration of whatever number of security updates they decide to put in it. 

Group C (AKA W): Shut down WU permanently and never again accept a Windows Update.  This group feels that the risk of MS changing their machine in unacceptable ways or even bricking it is greater than the risk of a hacker breaking in because some security patch was not installed.   I suspect that most people who even think about this topic will opt for this.  However since most people think of their computer like a potato peeler, they will not even think about this and things will just happen without them even knowing.  They will be Group A and won't even know it.

I am in Group W and would like to be in Group B.   It depends on whether I can find a satisfactory way for my 150 or so client machines to be updated.  They are average Joes and Janes.

Note that this may not apply to NON-Windows updates such as Office.  I am not sure how you can be in group B or W and do this, but I am working on it.

UPDATE November 19, 2016:

It now appears that B is an impractical strategy for 99% of users.  And, here is the reason why:  When an error is made in a security-only update, if the error turns out not to have a security affect, it may be corrected in a non-security update.  In that case if you were following B strategy, you would be left with an un-corrected defective update installed on your computer.  If you were extremely diligent and knew about it, you may be able to get the correction in specific cases.  This would entail an extreme amount of diligence that few would be willing or able to provide.

The new rollup style of updates that Microsoft is now providing to what we would call Group A, which include all kinds of updates (security and non-security), are cumulative.  That means if you miss a month or even more, it will not matter because by installing the latest month's rollup, you would be up to date.

NOTE well, that Security-only updates are NOT cumulative.  Which means if you miss a month, you may never get the missed updates.

So one strategy that you may wish to consider is following Group C, but still updating .net and Microsoft Office through Windows Update, but installing no Windows updates at all.  It would be advisable in this case that you stop using Internet Explorer because you would not be getting those updates, but instead use an alternative browser.

Then, after following this strategy for some time, if things take a turn for the worse, and you decide you made the wrong choice (Group C with .net an Office updates), you can easily shift to A by simply using the latest offered Rollup offered in Windows Update.

So, as things have evolved, it looks like the vast majority have really only two choices:  A as described above or C (modified as described above).  The good news is that if you follow the modified C strategy, you have a way back to the Microsoft way, that is easy to implement.

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

247 answers

Sort by: Oldest
  1. Anonymous
    2016-10-16T23:17:20+00:00

    I was unaware that SAB worked on 7. I will try it now. Thanks for the tip.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-10-17T00:14:57+00:00

    The current updates for Windows 7 and up seem to be causing problems. There have been at least 6 for windows 7 and 8. And about 15 fro Windows 10 that I have come across.

    Windows Xp has had only 2 plus the support line release an update that broke the connection with DMV camera about a year ago. This is why I told them to get off it.

    Most people are not tech people so they install everything trusting MS that it will work without a problem. But MS has let these people down in the last few years.

    Like you said, this is where many of us have a job to do the clean up.

    Now with MS rollup updates in Oct, I have about 100 computers sitting in my shop to repair since the update broke their computers. This is one of the reason I have not been here on the forums a lot.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-10-17T03:52:38+00:00

     

    Most people are not tech people so they install everything trusting MS that it will work without a problem. But MS has let these people down in the last few years.

     

    Once my WU issues were cleared up, courtesy of the folks on these forums, I stuck around to monitor new developments.  What astounded me was people who came on here with the same problem (WU going into "checking for updates" mode without end) stating, once they had applied the updates as instructed, that they had several hundred updates come in!  Apparently, they had WU set on full automatic and just assumed it was all getting done behind the scenes, never realizing that nothing was happening!  How many more out there still don't realize that they've got a problem?  And think that their computers are automatically protected?  Especially since Microsoft didn't exactly go all out public with their big WU changes in store, etc.  It's scary.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-10-17T04:51:39+00:00

    One of the symptoms of the Windows Update affliction is a slow running system and a svchost Process observed in Task Manager that is running amok consuming large amounts of CPU and memory.

    It was often and still is diagnosed incorrectly as a "memory leak in svchost.exe".

    Well my friends, there is no memory leak in svchost.exe - the problem is in the Windows Services that are running under (being hosted) by that svchost Process.

    Sooner or later by chance, luck or Internet searches somebody would discover that the Windows Update Service (wuauserv.exe) and often the BITS Service (redundant I know) were observed to be consuming all the CPU and memory.

    The extremely popular "solution" to the misdiagnosed memory leak was to disable the Windows Update and BITS Services which stopped them from running and the symptom of the problem was resolved.  You can find this "solution" in lots of places on the Internet.

    Another popular "solution" was to turn off automatic updates which fixed the symptom but not the problem.

    The real problem was not resolved but the symptom of the problem was resolved.  There is a big difference in fixing the problem and fixing the symptom of the problem.

    Now everybody is happy and the afflicted systems are running great again... but of course not receiving any updates.

    Then one day perhaps many months later those folks go to check for updates and it doesn't work or they report this popular problem:

    It's easy to fix that but now the original problem of a svchost running amok has returned.

    They use the various troubleshooter, fixits and communities to fix that enabling the WU Service again but WU still doesn't work - getting "stuck", "taking forever", "nothing happens", "too slow", etc. and their system is running poorly again.  It's that darn svchost memory leak again!  We know how to fix that - disable the WU Service or set Automatic Updates to never check!

    Then they find the right solution that fixes the problem and it's off to the races...

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2016-10-17T05:04:00+00:00

    LOL.

    See - here's the example from abobintxon the last page of

    Windows Update Solution

    Was this answer helpful?

    0 comments No comments