Guys this thing is like a virus. No matter what i try to do this thing always comes back . There are plenty of tutorials on the internet going through all the steps on how to avoid the privacy violations that is windows 10. What services to disable, what registry keys to set, ect. I even tried to a github project that tries to do everything to get rid of these privacy violations in windows 10:
What even makes me angrier than the privacy violation is the how much resources from your pc this stuff can suck down. I'm a heavy vm user. I generally use the latest version of vmware workstation. It seems like everyday i'm asking myself why my vm is so dog slow and i open task manager only to find out that the "Microsoft Compatibility Telemetry" service is sucking all my disk and/or cpu resources. I don't have the luxury to host all my vms on SSDs but for the most party the vm shouldn't still be starved for disk resources because it will have the entire disk to itself and all of my disk are fairly recent 7200rpm disks. VMs will of course always be somewhat resource constrained compared to a regular pc but running 1-2 vms on a high end pc with plenty of ram should not be to much to ask.
Anyways after i tried to disable everything i could as far as telemetry is concerned i rebooted and i took a screenshot (attached). This isn't even near the highest resource utilization i've seen. A lot of times it will be hogging ~90% of the CPU and i've commonly see it hog > 90% of the disk. You can see from the sceenshot that the cpu is struggling (red highlighting around the column). I wasn't doing anything on the vm at the time. I didn't even have a browser open. My AV is windows defender. The only other background task i have running is dropbox which was already synced (haven't updated any files for awhile).
I've considered renaming the executable but that might totally screw up windows. I don't know. With the current test tonight i'm running an I7-3770 with 32GB memory.. The VM was allocated 8GB memory and 4 vCPUs. It was the only vm running and i wasn't doing much on the host PC.