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]: Remove the option to uninstall "Microsoft.Windows.SecHealthUI" #190

Closed
ItsIgnacioPortal opened this issue Jan 6, 2023 · 4 comments
Labels
bug Something isn't working

Comments

@ItsIgnacioPortal
Copy link

Why would anyone want to break the Windows Security UI? There's nothing to be gained from that. furthermore, this option is hidden in the "People Hub" section.

2023_01_06_01_26_01_Window

@ItsIgnacioPortal ItsIgnacioPortal added the bug Something isn't working label Jan 6, 2023
@undergroundwires
Copy link
Owner

undergroundwires commented Sep 28, 2023

Hi, thanks for the report, you are completely right.

  1. All scripts that has security trade-offs should be moved under Privacy over security. So I will move this script to Privacy over security > Hide security options or something similar. People Hub is completely wrong category.
  2. I will add more clear documentation about what this script does, warn that this can lower the protection, and a section about why one might want to disable it (i.e. using another third-party security solutions, reveal forensics data etc.).

This is not something that a typical user would ever want to do, so I guess warning, documentation and isolation will do it.

@undergroundwires
Copy link
Owner

Changed category, title and docs, feel free to let me know if we should add/remove anything or it's fine:

image

undergroundwires added a commit that referenced this issue Oct 6, 2023
- Move removal of `SecHealthUI` app to "Privacy over security" category.
- Emphasize disruptive behavior in the script name.
- Add comprehensive documentation
@undergroundwires
Copy link
Owner

I added the fix, it will be released in next patch. I also took deeper look into why this was under People Hub and I see that it was due to my wrong interpretation of Microsoft documentation about Windows services. I thought there was a tree structure (categorization) where does who does not have name in table are parents of others, but this is not the case. I will also re-categorize some of the other apps (flatten the wrong categories) to fix it.

undergroundwires added a commit that referenced this issue Nov 20, 2023
- Remove incorrect categories and flatten their children.
- Simplify user interface by removing "installed" and "provisioned" app
  categories, listing the apps directly.
- Indent comments to be easily collapse parent category in IDE.
- Improve some of the existing documentation.
@undergroundwires
Copy link
Owner

undergroundwires commented Nov 27, 2023

Both categorization is fixed, the script is documented and moved to insecure scripts category. Everything is there since 0.12.8 🚀. Please let me see if you see anything else @ItsIgnacioPortal.

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

2 participants