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.