Theres only one way to hext dnsapi.dll & remove all ms domains from there which does the job flawlessly.
https://forums.mydigitallife.net/th...lemetry-repository.63874/page-68#post-1710912 There is no need to prove it, it was resolved ten years ago. Still, it's up to you to try it, for me it is not an unknown. only the great poets write simply and with the heart
Ok Dear . I stopped arguementing on MDL as warned by staff last time some months ago . Thatswhy its better to accept everything.
Those IP ranges you got them via Wireshark correct? What do you mean "there is not"? Do you mean those domains don't exist? TIA
1. Packet capture tool ie Tshark the very first thing anybody will get is continues connection attempts via dnsapi dll to remote msft ncsi ======> 2. ?
MYTHS AND LEGENDS Among the allegations of Windows 10 spy habits, there are some that our test does not confirm. We even decrypted HTTPS traffic by installing our own root certificate, but we did not find in any outgoing packet: not sending images from a webcam, not sending screenshots of the screen, not sending documents from a flash drive, etc... During all tests (including repeat tests), approximately half of the total traffic is attributed to the system and involves downloading three updates. There are no tracking features in the new version of Windows 10. But, using the recommended settings, Cortana and the deeply integrated search tools and Diagnostic Policy Service become the primary spies. Additionally, Windows Defender sends any files it deems suspicious or potentially dangerous to Microsoft's servers. SmartScreen and Edge (every browser does that) send lists of all searches and web pages visited. The location log records the current geographic coordinates and all physical movements of the device, etc ..... Connection attempts are various, on, Microsoft account, Cortana and ink, certificate, update, Defender, CloudHost, OneDrive etc .... The next update can easily change your privacy settings, so check them often. What has never been changed is Windows firewall rules, So ..... Block all those IP addresses as mentioned before and you will not have any more connections to MS.
I am again saying that i dont want to argue on MDL but that doesnt mean i dont have the concrete evidence . but i am clearly known that its useless to share a concrete evidence on MDL cuz mostly users are not worth of it & they will start abusing or reporting to staff till staff remove it from the thread. seen this several times with me but no more cuz i limit myself since its happening.
Telemetry blocking addresses on the browser 13.82.28.61 2.16.186.169 20.50.102.62 2.16.186.32 204.79.197.203 13.107.42.16 20.82.250.189 20.189.173.6 204.79.197.203 204.79.197.219 204.79.197.200 20.67.219.150 20.189.173.15 204.79.197.203 2.16.186.170 20.82.210.154 95.100.146.42 204.79.197.203 The firewall blocks everything fine! Who else can throw in the addresses of the EDGE blocking?
They are mostly Microsoft update addresses, it is too long a job to cover one by one, read here. As an example, this IP is on your list (13.82.28.61) but this is not the only Microsoft address with an initial 13. ...., there are hundreds of them (13.68.87.47,13.68.87.175,13.68.88.129,13.68.93.109,13.74.179.117,13.78.168.230,13.78.177.144,.........). To cover everyone you need to use Net-Range: 13.64.0.0 - 13.107.255.255, reserved for Microsoft. And so with everyone else IP. In my signature 3.) you can download a file to enter a thousand + Microsoft IPs that you need to block. Of course, you can complete this list (BlokList.txt) of your choice with one IP address, or (Net-Range IP 13.64.0.0 - 13.107.255.255) or (CIDR-IP 13.104.0.0/14), example.
If you want a translator in the browser then remove 204.79.197.219. Guys the goal was not to block all sub-networks, if you block them then EDGE will not work. Selected addresses that are responsible for the transfer, telemetry. We will put on the monitoring, as we will find interesting from the addresses - we will send. Ps: Honestly, telemetry, tracking is impossible to remove, and this is not just Windows - Linux, any build with any kernel, is tracked. There was once a network topology scheme Home + Pfsense + VPS (china+VPN) + Vpn = Online Internet Even with this scheme was detected a device, a location! Location detection is not your IP address. They do not care about it, what address or what DNS. Detection only goes to the hardware ID A network card has an ID, a graphics card has an ID, the processor has an ID, etc. To protect yourself from staring, you have to flash a new NIC ID every time you connect to the internet. Sometimes I hear from people that they never use a google account, so they don't get tracked. I explain to people. How do you picture it? Situation: You're sitting at home, the door opens - a man walks in and starts searching your house? He doesn't introduce himself, so you don't recognize him? I don't care if he introduces himself or not! You see him and you don't care if he has papers or not! It's the same with Google. He doesn't care if you have a passport or if you ran across the Mexican border!