OO ShutUp1010/3/2023 If there was one single Lineage build for all phones, I'd feel much more comfortable with it. Not to Lineage, where every phone model has its own build and dev team, and each build gets used by maybe a few hundred or thousand people, and reviewed by practically nobody. The "open-source means security because code gets vetted" argument only applies to big projects like Chromium, where hundreds of major corporations with world-class software engineers review, and contribute to the source code. Same exact reason people should strongly consider staying away from LineageOS builds and other such things, where the dev team of half a dozen non-vetted anonymous forum users is responsible for everything running on your phone. See XcodeGhost that got caught way after the fact. Generally, even the idea of using an OS downloaded from a random site (big Linux distributions excepted) is a security nightmare: you're trusting random, anonymous people not to put malware deep enough into the OS image where it won't easily be found. If I missed something or there are new findings, leave a comment.This reminds me of the old "Windows XP Service Pack 4", or Windows 7 Minimalist ISOs that were going around. But with the two approaches outlined here, users should be able to contain telemetry data collection on Windows 10. What I don't know now is whether these services are activated cyclically via tasks or via updates. This should also be what O&O Shutup10 does in the end. Get-Service WerSvc | Select-Object -Property Name, StartType, Status Get-Service DiagTrack | Select-Object -Property Name, StartType, Status You can also query the whole thing using PowerShell with the following commands in an administrative PowerShell console: Set 'Windows Error Reporting Service' (WerSvc) from 'Manual' to 'Disabled'.'User experience and telemetry in connected mode' (DiagTrack) from 'Automatic' to 'Disabled'.To do this, go to Computer Management as an administrator and select the Services branch (or call Services directly as an administrator via the Start menu search. The point of attack is to disable the relevant services for telemetry (DiagTrack) and Windows Error Reporting (WER / WerSvc) via the Services Manager. Which is then set to 0 or 1 and allows or disables error reporting. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting To do this, enter the following commands in an administrative PowerShell console. You can query, disable and also re-enable Windows Error Reporting (WER) using PowerShell with the following commands. Here roughly the web pattern using Windows 10 20H2 as an example: Disable Windows Error Reporting (WER) A few days ago the information also came from Patrick, who implemented the whole thing via PowerShell. Mark writes that the easiest way to disable the services in question is via GPO for the clients and gives the relevant information. Mark Heitbrink already described it in October 2020 on German site in the article Windows 10 Telemetrie und Diagnosedaten richtig abschalten. Maybe the people who download the application from O&O can give feedback if telemetry remains disabled with version.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |