Is there a good tool or script collection in the wild, that takes care of all the inflational usage of opt-outs of telemetry?

I am thinking of Microsoft products like .NET, powershell cmdlets, Teams, Visual Studio, Office et al. Many of them using common mechanisms like .NET SDK Insight, *CEIP Services aka "Customer Experience Improvement Program", and what not.

From a development point of view I understand the demand to know what your users are doing. From the user's perspective, making data collection/telemetry an "opt-out" is at least morally reprehensible. That is why I believe there must be more users being annoyed about that.

I am talking about this ever increasing mess:


HKLM\Software\Policies\Microsoft\VisualStudio\SQM\OptIn = 0

I was thinking of something like a list of all known variables that need to be set, maybe a tool that does analyze the system and finds them itself? At best including an update to the hosts file for total blocking of identified tracking domains.

Maybe a shim that, when enabled, returns 1 for all environmental variable requests against .*_TELEMETRY_OPTOUT...

In the end, I did not found any straight and transparent solutions/tools for this plague (yet). Who knows good tools or evolving approaches?

3 Answers 3


O&O ShutUp10++ is a free tool that allows you to disable a bunch of different Windows telemetries and similar kind of tracking by selecting them with chekboxes, you can also save the preset for the future. It is updated more or less regularly, but even considering that, note that it's pretty much impossible to disable everything because Microsoft really likes tracking its users and can add additional ways within any update.


This solution is a different approach than what you've asked for...but you could setup a Pi-hole in your network and block telemetry at the DNS level.

This has the added bonus of blocking unwanted telemetry for all devices on your network.

There's even a Microsoft Telemetry block list for Pi-hole


A wise man has said, "If you have nothing, then you have nothing to hide."
In the Bible we were given an example of a King that showed another King what he had, and the Lord then told that King that the other King would return with more Kings and take ALL that he had. ALL.

Not to be harsh, but the only tool that I have found that works most sufficiently toward blocking Microsoft telemetry is the user's own keyboard and their own one-at-a-time adjusting of Microsoft's settings.

I think that O&O ShutUp10++ sounds nice and Pi-hole (other than the name) might be nice. But, due diligence dictates that you make reasonably certain that you have personally verified that all of what should be done has been done.

"all known opt-out telemetry from Microsoft"
Not all of that is made visible via the phrase "opt-out". Much of the common user's options out of Microsoft telemetry are not told to the common user by Microsoft.

There are some options that are made available by Microsoft, which are for administrators that should understand the consequences of activating those options. Most of these options have been around since Microsoft Windows NT 4.0, which was (and still is) very powerful and was (and still is) very stable and was (and still is) pre-meditatively anti-hacker. I have never witnessed an NT 4.0 server bank set up correctly that has ever been hacked in all the following years. Thus, there are some options, made available by Microsoft, which Microsoft does not openly advertise to the average and possibly clumsy user. Many are still there in current versions of Microsoft Windows. In the days of NT 4.0, a network administrator had the ability to totally stop all intrusions including Microsoft themselves and every last one of the alphabet agencies. I have seen it done. Unless a user has UEFI on their system, then I suspect that is still the case, but can not herein prove it to you.

The following should take care of the small amount of (Microsoft shown) "opt-out" and the large amount of the rest that you can option out of because Microsoft grants to administrators those further options.

Back up data via copy and paste, not using Microsoft's backup.
Format (NTFS) the hard drive or ss drive.
Start the computer with NO Windows install disk in it.
After BIOS has started, then input the install disk (not before).
From BIOS (and only from BIOS) install Windows.
A little levity: No UEFI. Ooops No wait what? But the bright light bulb that we are supposed to fly around says that we "want" to use UEFI! What? Then NO ONE (not even the alphabet agencies) will have UEFI access to read and change and add-to your computer for their [whatever] reasons.
Search the internet for how to manually input blocks to Microsoft (and others like some CPU companies and some video card companies) telemetry. Then do that.
That should get you about as close as you can get.
Catalog your steps for this, then write a stand-alone C++ program that does all of your work to adjust your (no longer owned due to currently being released as software-as-a-service) Microsoft Windows 11.
Publish the entire code here.

+++ I edited the wording of the previous for more clarity.

+++ Also, now in response to Community Bot response for more details.

@Community Bot, thank you for having an opinion. But your request for further clarity, to a large extent if not all, is in today's current environment not always a wise thing to do as it might be viewed as legally negative to point out directly so called, "telemetry" by an economically powerful corporation beyond what that corporation publicly proclaims to be "telemetry." I am not about to take that chance. Thus I reference the reader to "Search the internet for."

I shall supply two references. The wise man: (Someone from which I have learned). The King: (The Book of Isaiah, chapter 39: verses 1-7: from the King James Holy Bible). You did request specifics. I gave what I felt appropriate.

  • Would you mind inserting a reference explaining how "From BIOS (and only from BIOS) install Windows." reduces telemetry signal sent to Microsoft?
    – Nicolas Raoul
    Apr 25 at 6:09
  • @NicolasRaoul, If a person starts a currently commercially available generally publicly purchased (like from Walmart) computer with a MS Windows install disk in it, and if the hard drive or solid state drive has been formatted in NTFS and has no operating system installed in it, then the computer will usually (at this time) start from BIOS. Then if they (still in BIOS) insert the MS Windows install disk and choose to install the MS Windows from BIOS, then there will be no (I repeat "NO") UEFI installed on the drive. Please look up UEFI, and read the entire history of it very attentively.
    – Line Item
    Apr 25 at 20:02
  • @NicolasRaoul, Highlights from what you should have read: UEFI is an operating system all on its own. It began, with different names, years ago to supply network administrators a back door, (even secret and un-viewed by the user) control at any time over the secondary operating system and the entire computer. This was and still is useful for Network Administrators. It is not in and of itself a bad thing. UEFI is not standardized. Each computer manufacturer and each Operating System developer may at any time, at their own private option, inject any and all code into the UEFI operating system.
    – Line Item
    Apr 25 at 20:13
  • @NicolasRaoul, UEFI from the beginning, via different names, has been useful if it is limited to a closed network and if it is used by company sanctioned network administrators that are fully trustworthy in their work therein. BUT it is risky for the average person to use a computer with UEFI on it which is connected to the internet, due to UEFI's vulnerability to hacking. Example: A bad person or whatever might obtain a computer with that version of any System with UEFI installed on it and reverse code the UEFI and gain access to the UEFI's control constraints.
    – Line Item
    Apr 25 at 20:23
  • @NicolasRaoul, continuing: Thereupon the bad person or whatever might be able to turn on the computer's UEFI operating system without the Windows or other operating system running, and access the entire drive and the camera and the microphone and the speakers (via software that turns speakers into microphones) and watch and record the activity of people in the vicinity of the computer. It is not difficult to break into UEFI. It is relatively easy. I expect that the average US teenager, given enough time (which they seem to have a lot of) could do this. So, you have to think.
    – Line Item
    Apr 25 at 20:35

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.