How ionuttbara/windows-defender-remover works
Project type and purpose
• This is a CLI‐driven, Windows system‐tweaking tool—a collection of scripts, registry modules, and an optional executable wrapper—designed to disable or remove Windows Defender and related security components on Windows 10+.
• There is no “frontend/backend” in the web sense; instead it comprises a command‐line entrypoint, a PowerShell/registry module engine, and many “.reg” files that are applied to the system.
File structure
• Top‐level entrypoints:
• Script_Run.bat (batch file that launches the process)
• PowerRun.exe / PowerRun.ini (elevation helper)
• Defender.Remover.exe (native wrapper for /r automation)
• Core scripts:
• RemoveSecHealthApp.ps1 (PowerShell to remove SecHealthUI)
• @Management/RegistryUnifier.ps1 (unifies and applies .reg files)
• Module folders (sets of .reg files):
• Remove_Defender
• Remove_SecurityComp
• Remove_SecurityComp_moduled
• Remove_defender_moduled
• Configuration & packaging:
• LICENSE, README.md, .github templates
• Script_Run.bat orchestrates the overall workflow
README for additional insights
• The README lists every component being disabled or removed (Windows Security Center services, VBS, SmartScreen, Telemetry, etc.).
• It describes two modes:
1. Interactive via the .exe or batch + PowerShell scripts
2. Automated via Defender.Remover.exe /r or passing parameters to the batch/PowerShell
A. User & Invocation Layer
• User double‐clicks Script_Run.bat or Defender.Remover.exe
• Optionally passes flags (/r) for unattended runs
B. Elevation Layer
• PowerRun.exe / PowerRun.ini ensures the process runs as Administrator
C. Orchestrator Layer
• Script_Run.bat (or native EXE)
• Calls PowerShell scripts (RemoveSecHealthApp.ps1, RegistryUnifier.ps1)
D. Module Engine
• RegistryUnifier.ps1 collects and applies all .reg files
• Removes Appx packages, executes DISM commands, bcdedit, etc.
E. Module Repositories
• Remove_Defender/*.reg
• Remove_SecurityComp/*.reg
• Remove_SecurityComp_moduled/*.reg
• Remove_defender_moduled/*.reg
F. External Dependencies (OS services & tools)
• Windows Registry
• DISM.exe (for Appx removal)
• PowerShell host
• bcdedit.exe
• Windows Security Services (wscsvc, SgrmBroker, etc.)
Relationships and data flow
1. User → Script_Run.bat (or .exe)
2. Script_Run.bat → PowerRun.exe (requests elevation)
3. Elevated process → Orchestrator (batch or EXE logic)
4. Orchestrator → PowerShell scripts (RemoveSecHealthApp.ps1, RegistryUnifier.ps1)
5. RegistryUnifier.ps1 → loads each .reg file and invokes DISM/cmdlets
6. OS services & registry are modified accordingly
7. Feedback/status → user console output
Architectural patterns & design principles
• Modular design: registry tweaks are separated into named folders.
• Orchestration script invokes modules in sequence.
• Single responsibility: each .reg file or .ps1 addresses one feature area.
• Layered elevation: batch → elevation helper → PowerShell → OS commands.
Details to capture
• Explicitly show the four module directories and that RegistryUnifier.ps1 iterates over them.
• Optional “Defender.Remover.exe” automated path.
• Use of PowerRun.exe for privilege elevation.
• Final effect targets: Windows Registry, Windows Services, Appx Packages, Boot Configuration.