It’s the top result if you searched in GitHub about removing Microsoft edge, while it’s not detected by Windows Security, Eset or Kaspersky (the best av vendors) it’s being detected by other av engines, is it a false positive?
It’s the top result if you searched in GitHub about removing Microsoft edge, while it’s not detected by Windows Security, Eset or Kaspersky (the best av vendors) it’s being detected by other av engines, is it a false positive?
its running setup.exe with the values --uninstall --system-level --force-uninstall, which sound good as long as the setup.exe is actually the MSedge setup file as it claims, current checksums do not match though, but this could be that the setup was changed from now and when it was added last year, but you can’t verify it. That being said, the rest of the code does indeed remove the residue edge from the system, which if the exe wasnt uninstalling it would cause problems as you operated it. That being said, yes you can’t verify it without knowing the current setup file version, and having the original to validate the checksum.
Didn’t realize Edge actually had a file named setup.exe used for uninstalling. Though it’s quite suspicious they’d include their own file instead of using the one already included with Edge.
I’m still looking into it myself tbh, so far I checked the checksums of the file itself, and the one that was active for the commit date 1/6/23 and the current edge installer exe, none of them match the file in the repo I don’t personally trust it either. The command line parameters are valid though, as in they appear to match the expected command line for the setup.exe file that should be in
%PROGRAMFILES(X86)%\Microsoft\Edge\Application\xxx\Installer, with XXX being your edge version.