* Move the vertical slider one notch up so that rull scope is File Name. * The fields are now automatically filled in. * In the next step, browse for the file “%localappdata%\google\chrome\User Data\SwReporter\xx.xx.xx” (select the highest version) and double-click “software_reporter_tool.exe” * Click “Deny” and in the next step “Publisher” * Right-click > Add New Rule (opens wizard) * Then go to AppLocakcer > Executable Rules * Computer Configuration > Windows Settings > Security Settings > Application Control Policies Preventing access on the folder is one sure-fire way of doing it, or using Windows Policy to disable access to the executable (not mentioned above, but can be done without using Chrome policies). Perhaps newer versions disallow you to disable this behavior?Įither way, such an invasive tool that takes waaaay more processing power than 30 open tabs of Chrome itself combined should *definitely* be allowed to be configured. Similarly, the tip to go to Settings > Advanced > Reset And Cleanup do not show the option in the screenshot above anymore (version 90.x).
Maybe they just mean ‘don’t take action and don’t report, but run anyway’ or something like that. The fact that it reports by default, without user consent, is very annoying.Īlso, the suggestions to add the ChromeCleanupEnabled and ChromeCleanupReportingEnabled to the registry don’t prevent this tool from firing up each time you launch Chrome (even though official Chrome documentation says this should work). It seems to be not very effective at what it does, as my antivirus software does much more (keeps whole system clean) but for much less energy. That said, it is very invasive and even on my high-end workstation it regularly spins for 20+ minutes and blocks a full processor core at 100% during that time, causing the computer fan to become rather noisy. If you look at the generated reports, there’s nothing that can lead back to a person (and no, I don’t work for Google, never have, never will, just wanted to clarify this bit). It doesn’t scan any user files, unless, for instance, you upload or download a file through Chrome.
Some nuance here: It actually only scans the folders belonging to, or directly related to the Chrome browser.
0 kommentar(er)
