April 10, 2026
Bureaucracy or bat‑signal?
WireGuard makes new Windows release following Microsoft signing resolution
Microsoft lifts the block, WireGuard ships — was it mob power or a mix‑up
TLDR: WireGuard’s Windows app is updated after Microsoft quickly reactivated its driver‑signing account, and users can install now. Commenters are split: some say it was routine bureaucracy, others argue public outrage forced action and worry about a growing pattern that could hurt smaller developers.
WireGuard just dropped a long‑awaited Windows update after Microsoft unblocked its driver‑signing account — and the internet can’t agree whether that fix was bureaucracy doing its thing or a crowd‑powered rescue. Project lead Jason Donenfeld says there’s no conspiracy, just paperwork gone sideways that got resolved fast once chatter on Hacker News and X pulled attention to it. But the comments? Oh, they’re spicy.
Some users are cheering the release itself: bug fixes, speed boosts, and cleaner code. There are even nerd‑pleasing touches explained in plain English, like changing certain connection settings without dropping your internet and better handling for tricky networks. The built‑in updater will nudge you, or you can grab the tiny installer here. So where’s the drama? Commenters keep asking: if the online mob hadn’t shown up, would this have been fixed at all? One user rattled off a list — LibreOffice, VeraCrypt, now WireGuard — and asked if this is a pattern of legit apps getting stalled until public outrage flips the switch.
Others echo Jason’s calmer take: a clerical hiccup, not a plot. Jokes flew about “summoning the Twitter bat‑signal” and “opening a support ticket via memes.” Either way, WireGuard’s back on Windows, and the community’s arguing about who actually made it happen.
Key Points
- •WireGuard released updated Windows components: WireGuardNT (kernel driver) and WireGuard for Windows (management app/CLI/UI).
- •New features include per-allowed-IP removal without dropping packets and support for very low MTUs on IPv4 connections.
- •The release focuses on bug fixes, performance improvements, and code streamlining by raising the minimum supported Windows version.
- •Toolchains were modernized: EWDK for driver builds, Clang/LLVM/MinGW for userspace, Go for the UI, and EV code-signing infrastructure.
- •A prior Microsoft driver-signing account suspension was quickly resolved after public attention, enabling the release to proceed.