For a long time I kept a rebuild on hand: PeerBlock 1.1 linked against a newer libcurl that actually supports TLS, so the automated list-update feature could talk to https:// endpoints again. The original post on this site had a link to that rebuilt installer.
The upstream repository hasn't seen a commit in nearly a decade, and the binary I used to host on Mega is long gone. I don't recommend installing PeerBlock on a modern Windows machine — the kernel driver it relies on (WinPkFilter) predates current driver-signing requirements, and the whole premise of a user-space application-level IP blocklist is better served by other tools today.
What to use instead
Depending on what you actually wanted PeerBlock for, any of these will do the job better in 2026:
- Windows Firewall with a PowerShell import script — any blocklist in CIDR form can be loaded as a set of
New-NetFirewallRuleblock rules. Native, kernel-level, no extra driver. - pfBlockerNG (on a pfSense/OPNsense box) — a router-level blocklist is strictly better than a per-machine one: it protects the whole network and uses the same list formats.
- uBlock Origin — for browser-level filtering, which is where 90% of what people used PeerBlock for actually happens anyway.
- Pi-hole / AdGuard Home — DNS-level blocklisting, trivial to run on a Raspberry Pi or any small Linux box.
If you really want to rebuild it yourself
The code is on GitHub. The HTTPS problem is one line in src/pblibcurl — the bundled libcurl was compiled without the WinSSL backend. Rebuild it with ./configure --with-winssl (or use a prebuilt libcurl-winssl DLL from the cURL project), drop the DLL into the PeerBlock output directory, and list updates over HTTPS start working.
I'm leaving this post up largely for historical context — and as a reminder that software in the "set-and-forget" category eventually stops being either.