Fail2ban for Windows: EvlWatcher, wail2ban and Fail2Ban4Win
On Linux, fail2ban reads the logs and bans addresses that keep guessing passwords. Windows logs every failed logon too, but blocks nobody. Several free projects bring the fail2ban idea to Windows – EvlWatcher, wail2ban and Fail2Ban4Win are the ones people find first. Here is what each one does well, how well it is maintained, and when one tool for bans, live firewall view and security check may fit better.
- The idea: read failed logins from the Windows event log and block the attacking address with a Windows Firewall rule.
- EvlWatcher: a Windows service with a management console – but its README says the project is discontinued, and the repository is archived.
- wail2ban: PowerShell scripts with growing ban times – archived since 2020, “No Maintenance Intended”.
- Fail2Ban4Win: a Windows service that bans whole /24 subnets; configured in a JSON file, no user interface.
- When Coinetic may fit better: you want a maintained tool that bans across many services, shows every connection live and checks your settings.
1. Why there is no fail2ban on Windows
fail2ban itself scans log files and bans addresses with too many failed logins by updating firewall rules. Its README describes the installation on Unix-like systems and does not mention Windows. On Windows the failed logons are in the Security event log (Event ID 4625), not in text files – so Windows needs its own tools.
2. EvlWatcher
EvlWatcher's README calls it “basically a fail2ban for windows”, with pre-configured defaults and install-and-forget use. A Windows service scans the event log for unsuccessful logins; in the example rule, more than five failures within two minutes put the address into a firewall rule named EvlWatcher for two hours, and repeat offenders go onto a permanent ban list after three strikes. Rules are an event source plus a regular expression in config.xml. A management console shows banned and whitelisted addresses, live activity, settings and a rule tester. It can be installed silently, for example by Group Policy. It is free (MIT licence).
Status: the README states that the project has been discontinued; the repository is archived and read-only. The last download linked is version 2.1.62 from May 2024.
What it did well: a ready-to-use default for RDP, a console with a rule tester, and silent mass deployment.
3. wail2ban
wail2ban describes itself as a Windows port of the basic functionality of fail2ban. It is a set of PowerShell scripts that watch configurable event IDs – by default failed Windows logons (4625) and failed SQL Server logins (18456) – and block an address with a temporary firewall rule after five failures in two minutes. Ban times grow with every repeat offence, up to three months. It has a whitelist, excludes the computer's own addresses, and can list or lift all bans. It is free (BSD-3-Clause).
Status: the repository was archived by its owner in November 2020 and carries a “No Maintenance Intended” badge.
What it did well: simple, readable scripts and escalating bans for repeat attackers.
4. Fail2Ban4Win
Fail2Ban4Win is a background Windows service that listens for Windows event log entries and blocks IP ranges in the Windows Firewall. It groups attackers into /24 subnets; after 10 failures from a subnet within 24 hours, that subnet is banned for one day, repeat offenders longer. The example configuration covers Remote Desktop and OpenSSH. It runs on Windows 7 SP1 / Server 2008 R2 SP1 or later with .NET Framework 4.7.2, is configured in configuration.json (the example starts in dry-run mode, so nothing is blocked until you change it), and has no user interface of its own – bans are visible in wf.msc or with PowerShell. It is free (Apache-2.0).
What it does well: subnet bans catch attackers who rotate through neighbouring addresses, and it supports old Windows versions.
5. Coinetic AI Security: bans, and the whole picture
All three tools do one job: turn failed logins into firewall bans. Coinetic does that too – maintained, with signed automatic updates – and adds what a ban script cannot show:
- Bans across services: Remote Desktop and Windows logons in every plan; VPN (RRAS / NPS), SQL Server, MySQL, PostgreSQL, Exchange, hMailServer, OpenSSH, VNC and FTP in Pro. Port scans, trap ports and repeated knocking in every plan; web attacks and floods on IIS, nginx, Apache and Caddy in Pro. IPv6 attackers are banned by /64.
- Whitelists under your control: you decide which addresses – offices, partners, monitoring – count as your own.
- Under Attack mode for botnets that try once from thousands of addresses – a case where per-address bans cannot keep up: admin ports close to the internet while LAN, VPN, web and mail keep running.
- Phone unlock: Remote Desktop stays invisible to the internet until you unlock it from your phone – nothing left to guess.
- Live firewall log with the rule behind every allowed and blocked connection, who owns each address, and a ban list with expiry.
- Coinetic network list (Pro): attackers seen by at least two independent Coinetic users in the last 7 days are blocked before they reach you.
- Security check with one-click, reversible fixes, and Ask AI (Pro + AI) to explain any ban or failed login in plain words.
- Silent deployment for many machines:
CoineticSetup.exe /quietby GPO, Intune or RMM.
At a glance
Only facts the projects state themselves; where they do not say, the cell is left empty (–).
| EvlWatcher | wail2ban | Fail2Ban4Win | Coinetic | |
|---|---|---|---|---|
| Free / open source | Yes (MIT) | Yes (BSD-3-Clause) | Yes (Apache-2.0) | No; 30-day trial |
| Maintained | Discontinued, archived | Archived 2020 | – | Yes, signed automatic updates |
| Runs as | Windows service + console | PowerShell scripts | Windows service, no user interface | Windows service + app (Simple and full view) |
| Windows versions named | – | – | Windows 7 SP1 / Server 2008 R2 SP1 or later | Windows 7 SP1 / Server 2008 R2 SP1 to Windows 11 / Server 2025 |
| Remote Desktop / Windows logons | Yes | Yes (4625) | Yes | Yes |
| SQL Server | – | Yes (18456) | – | Yes (Pro) |
| OpenSSH | – | – | Yes | Yes (Pro) |
| VPN, MySQL, PostgreSQL, Exchange, mail, VNC, FTP | – | – | – | Yes (Pro) |
| Other event sources by configuration | Yes (regex) | Yes | Yes | – |
| Longer bans for repeat offenders | Yes (permanent after 3 strikes) | Yes (up to 3 months) | Yes | – |
| Subnet bans | – | – | Yes (/24) | IPv6 by /64 |
| Port scans and trap ports banned | – | – | – | Yes |
| Web attacks and floods | – | – | – | Yes (Pro) |
| Live firewall log with the rule behind each connection | – | – | – | Yes |
| Outbound control: ask before a new program connects out | – | – | – | Yes |
| Phone unlock for Remote Desktop | – | – | – | Yes |
| Security check with one-click, reversible fixes | – | – | – | Yes |
| AI security analyst | – | – | – | Yes (Pro + AI) |
Download Coinetic, install, done – it starts protecting at once. 30 days free with all features, no payment details. From $20 per computer per year.
More comparisons: IPBan and RdpGuard · all comparisons · more guides: all Coinetic guides.
Frequently asked
Is there a fail2ban for Windows?
fail2ban itself is documented for Unix-like systems. On Windows, free projects such as EvlWatcher, wail2ban and Fail2Ban4Win, and products such as IPBan, RdpGuard and Coinetic, do the same job: they read failed logins and block the attacking address.
Is EvlWatcher still maintained?
No. Its README says the project has been discontinued, and the repository is archived. wail2ban has been archived since 2020.
Can I move from EvlWatcher or wail2ban to Coinetic?
Yes. Uninstall or stop the old tool and remove its ban rule, then install Coinetic. It keeps its bans in its own rules, named Coinetic Ban list, so they never mix with other rules.
Will an automatic ban lock out my own administrators?
In Coinetic you decide which addresses – offices, partners, monitoring – go on the whitelist; they are shown, but not banned.