Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG]: Windows Defender Uninstaller Script Doesn't Remove the MsMpEng.exe #128

Closed
jeffogu opened this issue Feb 25, 2022 · 3 comments
Closed
Labels
bug Something isn't working

Comments

@jeffogu
Copy link

jeffogu commented Feb 25, 2022

Description
Windows Defender uninstaller script doesn't remove the MsMpEng.exe.
Started it with adminstrator privileges and tried it for a few times again but nothing changed.

OS
Windows 10 x64 Pro Version 21H1

@jeffogu jeffogu added the bug Something isn't working label Feb 25, 2022
@brootware
Copy link

Hi @jeffogu , could you give a more specific on which particular script it is? So we can reproduce. Please use the bug report's instructions on reproduction steps

@femdiya
Copy link

femdiya commented Mar 14, 2022

@jeffogu I don't think that it is supposed to do that
So the flag should be a feature request if I'm not wrong.

undergroundwires added a commit that referenced this issue Aug 28, 2024
Refactor Windows scripts to run as TrustedInstaller using PowerShell
instead of batch files. This improves code reuse and enables more
complex logic for system modifications.

Key changes:

- Add function to run any PowerShell script as TrustedInstaller
- Refactor existing functions to use new TrustedInstaller capability
- Enable soft deletion of protected registry keys and files (#412).
- Resolve issues with renaming Defender files (#128).

Other supporting changes:

- Enhance service disabling to handle dependent services
- Use base64 encoding of 'privacy.sexy' to avoid Defender alerts (#421).
- Add comments to generated code for better documentation
undergroundwires added a commit that referenced this issue Aug 28, 2024
Refactor Windows scripts to run as TrustedInstaller using PowerShell
instead of batch files. This improves code reuse and enables more
complex logic for system modifications.

Key changes:

- Add function to run any PowerShell script as TrustedInstaller
- Refactor existing functions to use new TrustedInstaller capability
- Enable soft deletion of protected registry keys and files (#412).
- Resolve issues with renaming Defender files (#128).

Other supporting changes:

- Enhance service disabling to handle dependent services
- Use base64 encoding of 'privacy.sexy' to avoid Defender alerts (#421).
- Add comments to generated code for better documentation
undergroundwires added a commit that referenced this issue Oct 29, 2024
This commit adds disabling missing low-level Defender service/drivers,
improve disabling existing ones, and improve their documentation.

Key changes:

- Add disabling missing Defender services.
- Add disabling missing Defender processes.
- Add soft-deleting of missing service files
- Fix `ServiceKeepAlive` value #393, #426
- Add disabling system modification restrictions for persistent Disable
  service disabling.
- Recommend more Defender scripts on 'Strict' level

Other supporting changes:

- Add more documentation for related scripts.
- Move disabling `SecHealthUI` to disabling Windows Security.
- Fix `DisableService` attempting to disable the service even though its
  disabled.
- Add ability to disable service on revert in
  `DisableServiceInRegistry`.
- Improve categorization for simplicity, add new categories for new
  scripts.
- Add ability to run `DeleteRegistryValue` as `TrustedInstaller`.
- Rename some scripts/categories for simplicity and clarity.
@undergroundwires
Copy link
Owner

Fix released as part of 0.13.7 🚀. The file is now removed/moved. Feel free to test it and open new issue if there are any other issues. Thank you again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants