You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I barely managed to run this script on Win11 24H2 after a few hours. The Script_Run.bat file is permanently blocked by the system. I unzipped the contents of the archive and tried to add the folder to the exceptions. This trick worked before. But after installing this update, adding the folder to the Windows Defender exception was “Blocked by administrator”. After some reserch, I disabled the blocking, but the exclusion folders were still not added - the menu opened, but nothing happened. After some time, I found a solution that you can create a corresponding branch in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows Defender\Exclusions\Paths
And in it the parameter DWORD32 with the path name and a value of 0. After a reboot this worked and Defender released the folder. I think you should add these routines before running the script. Or at least add them to the manual.
The text was updated successfully, but these errors were encountered:
tried just now DefenderRemover on win 11 24H2 and all work fine. just on first run defender lock exe file (and delete) but need to open defender, turn off real-time protection, then run again DefenderRemover.exe then reboot pc and all defender is gone. wonderful
I barely managed to run this script on Win11 24H2 after a few hours. The Script_Run.bat file is permanently blocked by the system. I unzipped the contents of the archive and tried to add the folder to the exceptions. This trick worked before. But after installing this update, adding the folder to the Windows Defender exception was “Blocked by administrator”. After some reserch, I disabled the blocking, but the exclusion folders were still not added - the menu opened, but nothing happened. After some time, I found a solution that you can create a corresponding branch in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows Defender\Exclusions\Paths
And in it the parameter DWORD32 with the path name and a value of 0. After a reboot this worked and Defender released the folder. I think you should add these routines before running the script. Or at least add them to the manual.
The text was updated successfully, but these errors were encountered: