As someone who configures corporate firewalls for Windows backend comms: Not sure I agree with the broadness of some of what’s being detected, but short-circuiting DNS resolution for this stuff is not a tested scenario and has very complicated effects. Use https://www.oo-software.com/en/shutup10 https://twitter.com/BleepinComputer/status/1290409622151532545 …
-
Show this thread
-
Microsoft’s DNS namespace is a disjointed disaster of overlapping service dependencies their own documentation sometimes can’t describe the purpose of. It’s understandable people are suspicious of it in an information vacuum. Even if it’s become better communicated recently.
3 replies 8 retweets 64 likesShow this thread -
Windows 10 has inscrutable subsystems and dependencies. Just going in there with many “privacy” tools WILL break things in ways you will never be able to diagnose. Microsoft brought this on themselves, but still maybe it’s not a bad idea to clean some of the mess up now...
2 replies 8 retweets 51 likesShow this thread -
For example: A Microsoft engineer told me a huge percentage of support tickets about problems with apps from the Store are because people broke a Windows10 subsystem with a “privacy” tool. These unsupported configurations are an utterly massive ecosystem issue for Microsoft.
6 replies 10 retweets 68 likesShow this thread -
And, to be fair to Microsoft, if you don’t like what Defender does for free, just turn it off and use your own antivirus.
6 replies 3 retweets 51 likesShow this thread
I claim not being computer illeterate, but I just couldnt make it stop. Ive done it before- but after 30 minutes of trying to just make the damn process stop eating 40% of my cpu I ended up making a symbolic link to \nul on C:\ProgramData\Microsoft\Windows Defender:stream
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.