Does it actually disable the background process, or just turned off in the user interface? Take for example the WiFi Sense feature, you can turn it off, but doing so does not stop the WiFi connection information being uploaded to MS. You'd need jump through loops to actually disable WiFi sense. While this does not mean that the privacy settings would behave the same way, it certainly does not instill much confidence in these settings.
The Windows 10 telemetry and diagnostic services are what they are for an OS that sold as a service. The official purpose is that this data slurp enables MS making Windows 10 better and more secure, or something along the line. For an OS that provided as a service, that's somewhat fine. Certainly, there are some questions about the depth of data collection, but it is here to stay.
On the other hand, Windows 7 and 8.x had been sold as a stand alone OS and not as a service. That did not stop MS from retrofitting these OS' with the same telemetry and diagnostic services. For that matter, Office 2013 had been retrofitted with telemetry data collection as well. So, what's the purpose of retrofitting these systems? The chances are that MS will not make these systems better and more secure the same way as it does Windows 10. In which case, the purpose of these retrofits seem obvious...
I find it ironic that if the government collects all of your data through their dragnet, most people strongly disagree with it. Pretty much forgetting that the government is just a "central clearinghouse", the actual collection is done by corporations...
My only complaint with the Metadata collection is the CPU cycles and network traffic. You can say it's minimal, but when market your OS to tablets and 2n1's that have significantly less CPU power it sometimes is not minimal. For the average laptop or desktop you probably won't notice it, assuming you have an avg. broadband connection. However, for the resource constrained, it's annoying. There should be a simple on-off switch. This would also satisfy the tinfoil crowd. Going with analytics, this reduction in data would be fairly small compared to the overall population.
There's no default for the "Diagnostic and Usage" settings, well, the default is to ask the end user during the installation of OSX. The he/she has to select "Yes' or "No" before the installation proceeds. Is disabling this setting actually disables data collection? AFAICS, yes; at the very least, I have more trust in OSX than I have in Windows from version 7 to 10 from the telemetry perspective...
The performance impact of the Windows telemetry and diagnostics logging services can be substantial with older hardware. I am sitting next to my Lenovo ThinkPad T430 that has no open applications. Every once in awhile, I hear the CPU fan spinning up that last for a minute or two, meaning that the CPU utilization had increased close to 100%. Opening the task manager shows the "Task Manager" as the only app, can see its CPU utilization around 70% and quickly dropping to zero. At least the scheduled data collection and transfer stops, if and when activity is detected.
While the T430 is about four years old, it does have a Samsung EVO 850 SSD, 256GB. It's a good thing it does, all of the collections are done a lot faster...
About a week ego, the system was running on an HDD and that was the last time defragment process had ran.
Windows Defender is not active, installing an AV disabled it. CLR NGEN, isn't that for developers? It is certainly part of the .Net framework and on my Windows 10 there isn't much of it:
Why would MS need to run "Compattelrunner.exe", isn't that part of the Win10 upgrade utility? Besides, there are many more connections to MS on a much more frequent bases, depending on the type of data collections, updates, etc.
On a quad-CPU system with SSD drive, the system should not just decide to utilize the resources to the point that the CPU gets a heavy load. Idling or not...
Overview - Process Hacker), keep the process list visible and leave the machine to idle for a few minutes and you'll see various processes start up and perform maintenance tasks.
It takes a rather long time for ngen to perform these background tasks, You can force ngen to perform all pending tasks by executing the following:
1. Right-click the start button and select Command Prompt (Admin)
2. Run the following commands:
%windir%\microsoft.net\framework\v4.0.30319\ngen.exe update /force /queue /verbose
%windir%\microsoft.net\framework64\v4.0.30319\ngen.exe update /force /queue /verbose
%windir%\microsoft.net\framework\v4.0.30319\ngen.exe executeQueuedItems /verbose
%windir%\microsoft.net\framework64\v4.0.30319\ngen.exe executeQueuedItems /verbose
Prepare for lots of console spam while executing the last two commands, don't worry about any errors you might see as they are perfectly normal. This is what ngen would have done when your machine was idle
From what I've seen this only runs once a month and doesn't re-collect error logs and dumps from the previous month, I have my telemetry set to basic and it's barely even used 10MB of disk/network resources since December.
Application Insights - app monitoring| Microsoft Azure
The only real way to find what is being done in the background is by doing what I described above and disabling the screensaver and have PE or PH showing the process list when your machine is idle... Over a few weeks you'll start to notice quite a few maintenance tasks being done by lots of different software and the telemetry is nowhere near as resource hungry as the other tasks.
You can actually view the resource usage of the Telemetry process using the built-in Windows Task Manager.
1. Open Task Manager
2. Select the App History tab
3. Select the View menu and click the "Show History for All Processes" menu.
4. Locate the entry for "Microsoft Compatibility Telemetry"
It's just rolled over into the new month 3 days ago. Here are the top resource hog items on my system recorded just in the last 3 days:
Here is the Telemetry process... As you can see it's barely even used any resources:
Last edited by dmex; 08 Mar 2016 at 23:20. Reason: typos
Great post dmex, thanks!
You are correct... Most AVs do background and scheduled scans, if you enable them. On this system, these are disabled, but the real-time protection is on that could not cause high CPU load. The definition update is scheduled daily, instead of the default 30 minutes.
I've seen ngen in action, after the Windows update. It didn't take long, but caused the CPU fan to spin up.
The app history for this system does not have the "Microsoft Compatibility Telemetry" process, but the system is only ten days old. That might be due to couple of reasons, other than being "too young". One is that this system is a clean install of Windows 10 Professional 64-bit. The other is the custom installation, where everything that could be disabled had been disabled during the installation routine. Afterward, every telemetry services, schedules and processes that had been identified as unnecessary were disabled. The default apps that could be uninstalled had been uninstalled, while others disabled in either startup and/or removed from the background process. That includes Cortana as well, the taskbar shows "Search Windows" only.
The only telemetry agent that shows up in the app history is "Office Telemetry Agent", it used one second CPU time before it had been disabled.
This laptop haven't been used much as of yet, it is in the process of building it that includes disabling telemetry and other chatty services. It's not that I'd have anything to hide, I don't. I just want to, or rather like to control what's going on with the OS and apps. Off to remove OneDrive, it's getting on my nerves with its popups...