What exactly does KB2952664 do?

One more tidbit.  I tried to rename ConpatTelRunner.exe, and the response (in an Administrator cmd window) is "Access is denied".  So, MS has made this executable "permanent", if it is installed.

BDSolomon,

Sorry you got taken in by Microsoft's obtuse naming conventions.

As far as PREVIEW updates, these are just pre-releases of the coming month's ROLLUPs. There is no corresponding preview for the coming month's SECURITY ONLY updates.

This is just another example of Microsoft using their customers as un-paid beta testers rather than using some of the $20+ Billion they receive in quarterly revenue to invest in proper testing of code before release .... it's cheaper and easier to let their customers do the testing.

I understand that you needed the outlook fix that (at this point in time) could only be obtained by installing the PREVIEW releases .... but now be very careful because you could have picked up other bugs from the PREVIEW release you just installed (be sure to keep all critical data/files backed up). Watch sites like Woody Leonards to keep aware of any reported bugs found in the PREVIEW release.

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.

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 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.