-
-
Notifications
You must be signed in to change notification settings - Fork 187
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]: Defender warning of "viruses" can't be disabled #413
Comments
Did you initially disable Defender before this? |
No, I did not |
@hihilogic-dev Can you please send the script? |
This should not happen if you did not disable Defender if you do not use privacy.sexy. |
When in doubt, create a script with all tweaks reverted and:
@echo off
- :: https://privacy.sexy — v0.13.6 — Sat, 16 Nov 2024 01:37:12 GMT
- :: Ensure admin privileges
fltmc >nul 2>&1 || (
Comment: the line removal is a fix for the microsoft-introduced windows defender "precaution" against privacy.sexy that I observed. |
Description
I've been trying to run a couple batch files, and even some setup files as well, but it keeps returning an error that there is a "virus or potentially unwanted software". Usually, I would just go into settings and disable it, but clearly the settings has been stripped down and thus there is no way to disable it. Coincidentally, this also means I can no longer run the revert processes, since they are also a batch file, meaning that I no longer have means to restore Defender. Even when pressing the run button on my computer, Terminal will appear for a second and then immediately disappear. I would prefer to have all the settings i have activated reverted, so i can come back to this program at a later date, but I'm not sure how to do this.
Reproduction steps
Not sure what constitutes as a "virus", since a lot of setup files are basically a coinflip on whether it's actually going to run or not
Expected behavior
Refer to the description
Screenshots
No response
privacy.sexy environment details
Windows 11 2023, standard
Additional context
No response
The text was updated successfully, but these errors were encountered: