Newsletter Archives

• How to completely prevent Win7 from upgrading to Win10

  Posted on June 8, 2016 at 07:54 CDT by woody • Comment in the Forums

  Just got this question from BF:

  Hello Woody,

  I want to do everything possible to prevent Win10 installing on two Win 7 computers that I use to earn my living.

  I have uninstalled KB3035583 and set Windows Updates to “Check and ask me, etc.”

  Here’s what I’m doing now, daily:

  -Power off every night. Run user data backup before powering off.
  -Confirm Windows Updates is still set to “Check and ask me before downloading and installing”
  -Run Never10 to confirm that the two registry settings are set to disable the update
  Some days, I’ll open regedit and peek to confirm, but Never10 seems to do the trick.
  -Check C:\ to confirm that c:\$Windows.~BT has not been created and downloaded into
  -Search installed updates for KB3035583 to insure it hasn’t been stealthily reinstalled.

  Here are my questions:
  1-Can you recommend any additional one-time or daily steps?
  2-Do you have any concerns about what I’ve already done?
  3-Should I also uninstall KB2952664, KB3150513, and KB3021917?
  4-Will it be safe to turn automatic updates back on after July 29?
  5-Meanwhile, would I be safer just to turn updates completely off?

  Thanks so much for all you’ve written on this.

  You’re working too hard!

  If you want to keep Win10 off your machine, run GWX Control Panel. (Never10 is good, too, but I know GWX Control Panel better.) GWX Control Panel will flip the registry bits, delete the hidden folders, get rid of the icon… everything, all at once.

  You should turn Auto Update to “check but don’t install” per the Automatic Updates tab at the top of this page. Then, every time you manually run updates, run GWX Control Panel again, just to make sure.

  While I’ve been recommending that folks turn off automatic updating for more than a decade, I also recommend that you check and update from time to time. It’s important that you keep updating, for the security patches!

  Some people are rightfully concerned about Win7’s increased propensity to snoop. I haven’t had time to run down all the details – and there are many, many allegations – but for now, I’m not overly concerned about the quantity of data flowing to Microsoft. If you use the Chrome browser, or an iPhone or Android phone or tablet, you’re already sending out a lot of data. I’ve seen no indication that Microsoft is any worse than the Scrooglers or Applers. Conversely, I’ve seen no convincing evidence that Microsoft is any better.

  But if you really, really want to keep Microsoft away from logging your activities, there’s a long list of KB articles you can uninstall, a bad patch list, that you can use, if you’re so inclined.

  No idea what’ll happen after July 29. Lots of speculation, no real answers.

  Windows Patches/Security Bad patch list, GWX, GWX Contol panel

• Bad patch lists

  Posted on March 11, 2016 at 07:02 CST by woody • Comment in the Forums

  Speaking of elevating comments to the front page, I just got this comment from CAB:

  I’d like to know if this list of MS ‘patches’ to not install(or hacks, whatever you want to call them) is complete, or too many:

  2952664, 2976978 2977759, 3021917, 3022345, 3035583, 3068708, 3075249,3080149, 3083324, 3090045, 3112343, 3136449, 3123862, 3146449

  My response:

  I’ve tried hard to avoid recommending any specific list. Why? Most people don’t have the time or the interest to go back and fix what’s been broken – and there are varying perspectives as to what is “broken” anyway.

  My approach is to go forward with just a few simple rules:

  1. Wait. Don’t install any patches until there’s been a sufficient time to see if they’re causing any problems. That’s what this site is all about – and has been for many years.

  2. In the future, only install security patches for Win7 and 8.1. Don’t install optional patches. Every time I change the “MS-DEFCON” level, I include detailed instructions.

  3. Run GWX Control Panel frequently.

  That’s pretty simple, and it’s a formula just about anybody can follow – along with a few nudges when the MS-DEFCON level changes.

  That said, other folks with “bad patch” lists should feel most welcome to post them here. I’d be happy to pass them on.

  (Reader PO also points to an alternative set of patches on the AddictiveTips forum. I don’t know the principals there, so take the list with much salt.)

  A NEW UPDATE: Here’s the updated list from wdburt1, incorporating observations from Vesselin Bontchev.

  For emphasis: I do NOT recommend that you go into your computer and uninstall these patches. Just be aware of the fact that Microsoft’s snooping routines are changing, and that MS has pushed a whole lotta stuff onto Win7 machines to grease the skids for Win10.

  Here’s the new list. I hope it comes through with the proper formatting. I have shamelessly cribbed some descriptions from Bontchev’s list, most of which were taken from Microsoft’s KB article descriptions.

  My list of Microsoft malware Updated March 14, 2016:

  KB971033–Update for Windows activation technologies*

  KB2876229–Updates Skype, sets MSN/Bing as defaults

  KB2902907–Description not available, update was pulled by Microsoft*

  KB2922324–Description not available, update was pulled by Microsoft*

  KB2952664–Installed itself on RH computer 12/1/15 even though not selected. Installed itself on RH computer in 3/3/16 update even though not checked.

  KB2966583–Improvements for the System Update Readiness Tool in Windows 7

  KB2976978–Performs and collect compatibility appraiser logs in order to ease the upgrade experience to Windows 10

  KB2977759–Compatibility update for Windows 7 RTM (for Windows Customer Experience Improvement Program)

  KB2990214–Update to upgrade from Windows 7 to a later version of Windows

  KB2999226–The Windows 10 Universal C Runtime (CRT) is a Windows operating system component that enables CRT functionality on the Windows operating system. This update allows Windows desktop applications (Windows Store, other apps) that depend on the Windows 10 Universal CRT release to run on earlier Windows operating systems.

  KB3012973–Upgrade to Windows 10

  KB3014460–Update for Windows insider preview /upgrade to Windows 10*

  KB3015249-Update that adds telemetry points to consent.exe in Windows 8.1 and Windows 7*

  KB3021917–Update to Windows 7 SP1 for performance improvements

  KB3022345–Update for customer experience and diagnostic telemetry

  KB3035583 (THE BAD BOY)–Installs ‘Get Windows 10’ app in Win 8.1 and Win 7 SP1 (GWX)

  KB3044374–Update that enables you to upgrade from Windows 8.1 to Windows 10

  KB3046480–Update enables the system to determine whether to migrate the Microsoft.NET Framework 1.1 to a later version of Windows when you upgrade from Windows 8.1 or Windows 7 to a later version of Windows.

  KB3050265–Updates Windows Update Client for Windows 7 (changes system files to support upgrade)

  KB3050267–Updates Windows Update Client for Windows 8.1 (changes system files to support upgrade*

  KB3065987–Updates Windows Update Client for Windows 7 and Windows Server 2008 R2 (changes system files to support upgrade)

  KB3068708–Telemetry (replaces KB3022345)

  KB3072318–Update for Windows 8.1 OOBE to upgrade to Windows 10*

  KB3075249–Adds telemetry points to consent.exe in Windows 8.1 and Windows 7

  KB3075851–Updates Windows Update Client for Windows 7 and Windows Server 2008 R2 (changes system files to support upgrade)

  KB3075853–Updates Windows Update Client for Windows 8.1 and Windows Server 2012 r2 August 2015*

  KB3080149–Telemetry

  KB3083324–Windows Update Client for Windows 7 and Windows Server 2008 R2 September 2015

  KB3083710–Windows Update Client for Windows 7 and Windows Server 2008 R2 October 2015

  KB3090045–Update applies to some reserved devices upgrading to Windows 10 from Windows 8.1 or Windows 7 Service Pack 1 (SP1).

  KB3102810–Update contains improvements for Windows Update Client in Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1. [Second issue addressed is that] svchost.exe process occupies 100 percent of CPU usage when you upgrade a Windows Update client to Windows 10.

  KB3102812–Update contains improvements for the Windows Update client in Windows 8.1, Windows RT 8.1, and Windows Server 2012 R2.[Second issue addressed is that] svchost.exe process takes 100 percent of the CPU usage when you try to upgrade to Windows 10.

  KB3112336–Windows Update Client for Windows 8.1 and Windows Server 2012 R2 December 2015

  KB3112343–Windows Update Client for Windows 7 and Windows Server 2008 R2 December 2015

  KB3123862–Updated capabilities to upgrade Windows 8.1 and Windows 7

  KB3135445–Windows Update Client for Windows 7 and Windows Server 2008 R2 February 2016

  KB3138612–Windows Update Client for Windows 7 and Windows Server 2008 R2 March 2016

  KB3139929–Cumulative security update for IE, carries KB3146449, Woody says avoid

  KB3141092?–Installed itself on LH computer 3/3/16 even though not selected, reportedly piggybacks on Security Update KB3134814 if IE11 is installed

  KB3146449–Updated Internet Explorer 11 capabilities to upgrade Windows 8.1 and Windows 7 (piggybacks on KB3139929)

  * Update added per Vesselin Bontchev 3/13/16 post to Ask Woody

   

  Windows Patches/Security Bad patch list