• How to permanently remove KB2952664, and maybe speed up your machine in the proceess

    Just got this fascinating email from Tom:

    Lately I’ve been focusing on are your articles pertaining to the different widows patches / monthly windows updates that are trying to get people to install windows10 whether they want it or not. Months ago (before I found AskWoody and the GWX Control Panel) I found that I had the windows 10 GWX icon on my computer, and I had no idea as to what it was, or how it got there. The icon was the start of my education / introduction as to what Microsoft was doing to get people to upgrade to windows 10. As I’m sure most people do, I turned to Google for answers. In a short time I learned that WU KB3035583 is what caused the GWX icon to show up on my computer. KB2952664 was another update that kept popping up as something to be concerned about. I found that both of the updates were installed on my computer. I promptly uninstalled both of them and then hid them when they reappeared. After the computer rebooted the GWX icon was gone and I was a happy camper. From that point on I started doing a google search after the monthly Patch Tuesday WU’s appeared, and definitely before they were installed. That’s actually how I found AskWoody, and also when I started only installing Security updates. Not to long ago I saw the KB3035583 update was offered again. I promptly hid it along with the other KB3035583 that was already hidden. Because of one of your recent articles about KB3035583 and KB2952664 I decided to search my installed windows updates to see if either one was there. I was surprised to see that KB2952664 was. I promptly uninstalled it for a second time, then hid it again when it appeared in the available updates. A few days later while checking on another update, I happened to see that KB2952664 showed in the installed updates, again. After another google search I found that there were a lot of other people who were in the same situation I was in. It seems that anytime the update was uninstalled, it automatically reinstalled itself almost instantly. I then did a search for, “unable to remove / uninstall KB2952664”. Lots of people asked the question but nobody had a definitive way to pertinently remove the update.

    Yesterday I actually found a simple solution that actually did work at removing the update. Hence the reason for the email! I thought your readers might find it useful.
    It’s an easy 2 part process.

    First, from an elevated command prompt enter: (   dism /online /get-packages | findstr KB2952664   ) This pull up all KB2952664 packages. Mine had 10 different versions, for a total of 22 packages.

    To remove them, again from an elevated command prompt enter:
    (  dism /online /remove-package /PackageName:Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.1.3 )  This removes version 6.1.1.3 only.  On machines that also have versions 6.1.0.12, 6.1.3.0, 6.1.7.4, 6.1.8.2, etc. etc. this command must be repeated with the appropriate version numbers.

    Once all versions are processed, run: (   dism /online /get-packages | findstr KB2952664   ) again, and if it doesn’t return any packages, KB2952664 is gone…

    I can’t tell you how much quicker my machine seems to run since the update is finally gone.