What exactly does KB2952664 do?

I decided, after reading some threads on other fora, that I would disable this Diagnostic Tracking Service.  I will look after the next reboot to see if that Service is still disabled.

--Barry Finkel

I just mistakenly installed this patch: KB3068708.

That patch appears to be a follow-on/replacement to KB3022345.

KB3068708 appears to be yet another attempt by Microsoft to get telemetry data. Here's an excerpt from Microsoft's description:

"This update introduces the Diagnostics and Telemetry tracking service to existing devices. ....

[...]

The diagnostics tracking service collects diagnostics about functional issues on Windows systems that participate in the Customer Experience Improvement Program (CEIP).  ...

[...]

This update contains the following two manifests that are occasionally updated by the Diagnostic Tracking Service:

• telemetry.ASM-WindowsDefault.json
• utc.app.json

The two files are marked as static files in the update. When an advanced user runs the System File Checker Tool (sfc.exe), the files are unintentionally flagged as corrupted. There is no impact or actual corruption on a device that is running this update, and this issue will be fixed in a later service update."

I interpret the above ("the files are unintentionally flagged as corrupted") to mean that KB3068708 has the same bug as its predecessor (KB3022345 ... which has the same warning in its description).

Here's more information on KB3068708:

http://www.infoworld.com/article/2930713/microsoft-windows/microsoft-re-re-releases-kb-2952664-kb-2976978-and-kb-2977759.html

I only discovered the above information after I had installed KB3068708.

I had three choices:

1. Do nothing; leave KB3068708 installed. Microsoft has not earned enough trust for me to select this option.
2. Uninstall KB3068708. Microsoft's track record (buggy patches) makes me worry that uninstalling KB3068708 might leave something behind (that would later cause problems). Again, my lack of trust in Microsoft.
3. Disable the Diagnostic Tracking Service. I chose this option since it is easy to do and easy to undo (if necessary). ... and disabling the service should stop the telemetry data from being sent without my permission.

I see lots of reasons to ignore some patches, and the possibility that Microsoft is using one to spy on its customers without their knowledge or consent is a pretty good one.

To each his own, I guess.

I am not at my computer at 3AM, so I cannot easily start a Wireshark trace to see what is being sent to MS via the new task that runs then.  And I assume that the packets would be encrypted, so a trace would be useless, except to get the IP address of the destination IP server.

If you wanted to get more information on the MS Compatibility Appraiser task (without having to get up at 3am), you could change the time of day (in Scheduler) when the task runs.

Not only do I never intend to upgrade my current computers to Windows 10 (or 8.1), but I have lost trust in Microsoft ... so I have hidden all windows "nagware" patches/upgrades (such as KB2952664, KB2990214, KB3035503).

If Microsoft wants its customers to install Windows 10, then rather than using "nagware" to trick/nag people into installing it, they should create an Operating System that is so good, and so compelling, that people will be lined up waiting to install it. Unfortunately, it appears that Microsoft has forgotten how to create such an Operating System.

I will continue to install patches when I see them in Windows Update.  I see no reason to ignore a patch, unless I have read that the patch introduces problems.  I am not at my computer at 3AM, so I cannot easily start a Wireshark trace to see what is being sent to MS via the new task that runs then.  And I assume that the packets would be encrypted, so a trace would be useless, except to get the IP address of the destination IP server.

My Task Scheduler window says that the MS Compatibility Appraiser task will next run at 4:16:17 AM tomorrow morning.  I assume that the run time is variable across the various Windows machines so that the destination server is not flooded with data at 3AM every morning.

--Barry Finkel