What exactly does KB2952664 do?

Admittedly, the catalog is horribly indexed.  I was directed to the catalog from the link I posted (I applied the rollup at work and they disable windows update). Their brilliant fix, after I did the legwork, was to tell me to install the rollup.  Since I couldn't find it in Windows Update, I went to the provided catalog link.

It showed 4 items (when I clicked on the link for Windows 7).  2 for Win7, 2 for Windows server 2008 as I recall.  At the time, each of the two had the same description.  I opened both Win7, and one was x86, the other, while it mentioned 64 bit or x64 (I forget), the X64 had AMD in the name.  I think the description said it was for 64 bit systems.  They have since updated it and the names say C86 and X64.  In any case, updating manually from the catalog worked.  Since I was told to do that at work, I did it.

I'm reluctant to apply it to my home PCs, and was really hoping to get some input here.  Soon I'm going to give up and apply the rollup, which basically is defeating the two main reasons I didn't get Win10, buying a system with a built-in death.  (I have enough stuff on my PC, including a PCIe NVMe drive requiring a slew of drivers to even come up, so if I get it wrong I'm in trouble, so I'd be nervous to downgrade to Win10... plus it might not be free by then.)  I didn't want the blind updates, and I didn't want the telemetry.  Well they've added the telemetry to WIN7 which I will on doubt be subject to when I install the rollup.  And for the blind updates (take all or get lost), well I guess I now have to voluntarily do that.

I was hoping for some activity here -- the people who posted about how to disable the telemetry, any news of microsoft releasing just a fix for what they broke instead of forcing "everything INCLUDING the kitchen sink" on us if we simply want to fix what they broke.  So far, nothing.  As I have been saying, if they WANTED to force this on us, it was a brilliant move.  Kinda hard to think that a security update accidentally broke indexing, and just outlook indexing at that.

BDSolomon,

I recommend that you read Woody Leonard's site here.

Woody has categorized Windows users into three groups:

Group A:  those that install everything that Windows Update offers each month. This includes the monthly rollup with all of its potential telemetry (rollup is obtainable from Windows Update).

Group B: those that do NOT install the monthly Rollup, but instead install the monthly Security Only updates for Windows and IE11 (obtainable only from the catalog). Also some misc updates from Windows Update (such as the .NET updates, Office updates) are installed.

Group W:  those that do not install any updates. Not a very good choice considering the malware that has recently been found to take advantage of several vulnerabilities in Windows.

Here is an article by Woody about these three groups.

I choose to be in Group B.

Each month (after Woody's DEFCON system has declared that it is all clear to install updates, see the article on Woody's DEFCON system here), I go to this page, scroll down to the Windows Version I use (Windows 7 or Windows 8.1), scroll to the month/year of the given version's  Security Only updates I want to install, and download the appropriate (32-bit or 64-bit) version of the Windows and IE updates (doing this is much easier than trying to find the appropriate updates in the Windows Catalog).

Once I have downloaded the two Security Only updates (Windows and IE), I install each one. Then, I go to the Windows Update applett in control panel and I change my Windows Update setting from "Never check for updates" to  "Check but let me choose whether to download and install". Then Windows Update will check for updates. and update its list of available updates.

Each month, when Woody issues the DEFCON 3 state, he also reviews the updates and describes which ones are ok for Group B users to install and which ones to bypass. I usually follow Woody's advice and only check/install those updates (in the Windows Update list) that Woody recommends. NOTE: I DO NOT install the monthly rollup update that is found in the Windows Update list (because I have already installed the monthly Security Only updates for Windows and IE). The updates (in the Windows Update list) that I usually install are those for .NET, Office, etc. The main point here is that as a Group B user, I DO NOT want (and do not install) the monthly rollup update found in the Windows Update list.

After I have installed the specific updates (from the Windows Update list) that I want, I change my Windows Update setting back to NEVER.

Of course, this does not guarantee that my computers are totally free from Microsoft's collection of telemetry .... Microsoft could always include telemetry collection as part of their Security Only updates.

To cut down on the telemetry sent to Microsoft, I have disabled the Customer Experience Improvement Program (CEIP) in Windows and Office (and disabled the corresponding Scheduled Tasks) ... along with a few other hacks.

As I mentioned, the above does not guarantee that all telemetry is eliminated, but it's "90% effective with 10% effort".

Tnx for that.  Apparently at home I installed:

2017-06 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4022719).  At work I did both that and 2017-06 Security Only Quality Update for Windows 7 for x64-based Systems KB4022722

Which is supposedly just security BUT a rollup.  I'm confused.  I think I was taking everything labeled security; guess I have to filter it through this site (paranoid note: If I wanted to break into a lot of computers, I'd hack this site and mark the security fix that patches the hole I want to use, as suspicious.)

In any case, I can confirm since I hit the problem on both home and work PCs, that the bug is i both KB4022719 and KB4022722.  BOTH are listed in the microsoft article, and that article lists the problem with the only fix being the rollup.  And indeed the rollup fixed the problem on my work computer.

UNLESS this is only in the security rollup and not in the other, I think anyone following that site may still need something to fix what that security "fix" broke.

Oh crap.  I fell for it.  The "security rollup" actually contains the previous month's monthly non-security updates.  SO the only reason to really use that is if you WANT their rollup but want to delay a month to let problems be exposed.  Now I'm SURE the problem is in the base security fixes (or it would've hit others a month earlier).  AND I have actually installed the rollup through last month.  I guess I've already done most of the telemetry damage; about all I can do is take the time to search my notes for anything about telemetry and see if I have anything more to disable.

I fell for it.  A security rollup is NOT a security rollup.  It's current security and last months non-security rollup.  They used their words to sucker me and others into taking the rollup.

I guess since I'm badly affected by the bug, and I'm only one month behind in the rollup, I might as well install this one as I desperately need the fix.

BDSolomon,

Microsoft has (deliberately?) chosen update names that are VERY CONFUSING.

Each month there is a ROLLUP update (found by letting Windows Update scan for updates), and there is a SECURITY ONLY update (only found in the catalog). You only should install one or the other.

The ROLLUP update for any given month contains ALL of the previous month's updates (both security and non-security) back to October 2016 (this is for those who choose to be in what Woody Leonard calls Group A). If you choose to always install all windows updates (security and non-security), then each month you only need to install the most current month's ROLLUP and you will get all of the previous security and non-security updates for Windows back to Oct 2016. The ROLLUP update is cumulative. If you skip a month then all you need to do is install the next month's ROLLUP. If you install the ROLLUP, you do not need to install the Security-Only (because the ROLLUP already contains the Security-Only updates, along with non-security updates).

The SECURITY ONLY update only contains the security updates for the CURRENT month (this is for what Woody Leonard calls Group B). If you want all of the SECURITY ONLY updates back to October 2016, then you need to have installed each month's SECURITY UPDATE as it was released. The SECURITY ONLY update is NOT cumulative. If you skip a month, you need to go back and install the missed security only update (if you want to be fully updated with security issues).

For June, KB4022719 was the 64-bit Windows 7 ROLLUP and KB4022722 was the 64-bit Windows 7 SECURITY ONLY update.

You mentioned the Outlook bug (which was in the June updates). My understanding is that the bug only affects outlook clients (that run on your PC) such as Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016.

Here is a site that discusses the Outlook bug.

If you access your outlook mail using a browser, navigating to the outlook.com web page, and signing into your outlook account, then you are not impacted by this bug.

I am in that category (not impacted by the bug), so I have not paid much attention to the the outlook bug or how it is fixed. I recall reading that Microsoft has issued as fix.

In the site I linked to above, expand issue  #5 and you will find a list of fixes for each version of Windows. Do some research BEFORE installing the fix for outlook .... I am not sure if that fix works or causes other problems.

Bottom line seems to be that Microsoft cannot be trusted to do the proper testing before releasing updates. That's why I always wait about 4 weeks before installing any given month's updates. So, for the June updates, I just installed them on July 1.

As far as telemetry, since you already have installed the ROLLUP (KB4022719), then you have Microsoft's telemetry installed. However, I still recommend that you research how to disable the Customer Experience Improvement Program (CEIP) in Windows and Office (and disable the corresponding Scheduled Tasks). Doing that will stop some of the Telemetry.

Tnx.  I read about disabling the telemetry before, and I THINK I did it on this computer (I KNOW I did it on the previous one).  It included settings and disabling services.

The "FIX" they offer for issue#5, which DID work on my work PC, IS the rollup.  As I read it, they're calling it the preview for the July rollup (guessing now that's as opposed to the "security rollup" which as we've now said is really security PLUS rollup.

Guess they got me already, and since I badly need the fix, I have little choice.  They tricked me with that name.

And yes I use outlook at home and work (3 email addresses at home).  Huge message base, and I count on search working reliably and fast, so I am definitely hindered by the bug.  I also confirmed that the recommended rollup fixed the problem at work (IT was real helpful... when they couldn't fix my problem (upgraded Office, rebuilt the index, rebuilt the OST, rebuilt the index again), their only offer was to reimage... and BTW, that would leave me with Win10.  WHICH ALSO HAS THE BUG, AT LEAST SOME BUILDS).  So I googled, found the bug acknowledged, and the various rollups (for different windows releases) as the fix.

I guess I'd be more upset and anxious to get a fix outside of the rollup if I hadn't fallen for their trick with that naming convention.  COME ON, THAT OBVIOUSLY IS A SECURITY ROLLUP, MEANING CUMULATIVE SECURITY FIXES.  Ir is a sucker naming convention for those who have vowed to only take security updates.

I managed to avert the GWX crap (GWX Control Panel told me I was good), but fell for this.  PT Barnum would be proud of them.