es3n1n/defendnot

An even funnier way to disable windows defender (through WSC api)

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 35 minutes ago
Added to GitGenius on September 18th, 2026
Created on May 7th, 2025
Open Issues & Pull Requests: 3 (+0)
GitHub issues: Enabled
Number of forks: 296
Total Stargazers: 3,680 (+0)
Total Subscribers: 31 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 1.2 hours
Mean response time: 14.8 days
90th percentile: 4.9 days
Tracked items: 31

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 248 days
Stale 30+ days: 1
Stale 90+ days: 1

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (6)
  • enhancement (3)
  • question (3)
  • information (2)
  • invalid (2)
  • wontfix (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

defendnot is a tool that disables Windows Defender by registering a fake antivirus through the Windows Security Center API.

The tool addresses the problem of disabling Windows Defender on Windows systems by leveraging the Windows Security Center interface rather than directly attacking Defender itself. It works by registering a fake antivirus product through the WSC API, which causes Windows to treat Defender as redundant and disable it. The approach includes an optional supplementary script that can strip additional Defender functionality by modifying registry policies related to real-time monitoring, behavior monitoring, cloud reporting, and signature updates.

Developers considering this tool should understand that it requires administrator privileges and may need temporary disabling of real-time protection and tamper protection before execution, as Defender will otherwise block the tool from running. On newer Windows 11 builds, Smart App Control may also need to be disabled first. The tool persists by adding itself to autorun to maintain the fake AV registration across reboots. The optional extra-strip script is separate because registry modifications are complex to reverse cleanly. This tool is suited for scenarios where legitimate system administration requires Defender to be disabled, though users bear full legal responsibility for compliance with applicable laws.

The project shows active maintenance with a documented reverse-engineering writeup explaining the WSC API approach. The codebase is written in C++ and includes both a loader binary and batch scripts for optional extended stripping of Defender policies. The tool acknowledges its limitations transparently, including the requirement to remain on disk for persistence and the complexity of cleanly undoing registry changes made by the optional extra-strip script.