Comment by zx2c4
12 hours ago
As I mentioned in the mailing list post, the Microsoft paperwork shuffling matter got dealt with rather quickly, following all the attention the HN thread from the other day got. And now we're finally out with an update!
NT programming is a lot of fun, though this release was quite challenging, because of all of the toolchain updates. On the plus side, we got to remove pre-Win10 support -- https://lists.zx2c4.com/pipermail/wireguard/2026-March/00954... . But did you know that Microsoft removed support for compiling x86 drivers in their latest driver SDK? So that was interesting to work around. There was also a fun change to the Go runtime included in this release: https://github.com/golang/go/commit/341b5e2c0261cc059b157f1c...
All and all, a fun release, and I'm happy to have the Windows release train cooking again.
Good to know everything was resolved, but did you ever find out why your signing account was suspended? That's not something you brush off as haha silly Microsoft..
Microsoft are saying it's because those accounts didn't undergo verification for the Windows Hardware Program
https://www.theregister.com/2026/04/09/microsoft_dev_account...
I understand it's because it's a device driver, but why should a pure software publisher which has no hardware product of any sort be required to go through a "hardware program" gatekeeper of what binaries a person can choose to install and run on their own computer?
8 replies →
They should definitely put up a statement addressing it. Moreover what they plan in the future to avoid such traumatic event, this is not a “simple sign program”, this touches fundamental parts of the OS.
Apparently it's quite widespread, so I would assume a bug on their side. That's what support seemed to imply at least. We're still blocked at my company for one month+ now.
"so I would assume a bug on their side"
Why a "bug".
2 replies →
With Microsoft, I assume malice AND negligence first. The hostility they've shown toward their own users tells you everything you need to know.
https://techcommunity.microsoft.com/blog/hardware-dev-center...
Off topic: Thanks for wireguard. It is a truly great piece of software.
Somewhat on the side - but is there a wireguard that works well for ReactOS? Does the windows version just work fine?
Just curious how/if the version support might work out for ReactOS.
Good question! I've never tried. The NT driver makes use of some of the more advanced features of the networking stack, so possibly not. But you never know. I'd love a Wg4React.
ReactOS was, at one time, targeting a Windows Server 2003-level of compatibility. With that in mind I can't imagine current Wireguard would have even a shred of hope of working on ReactOS.
I really appreciate what you wrote in that post re: dropping support for pre-Windows 10 operating systems.
I'd like to snag that latest previous version which still has compatibility with older OS's, anyone have a reliable link handy?
(I couldn't quickly find a "Previous Versions" list on their website)
It looks like all the old files are still hosted on the server. You can just replace the version number in the download links with one of the tags from https://git.zx2c4.com/wireguard-windows.
Hey there, thank you for pushing this out. I saw there's a 0.6.1 update now, that also reboots the machine after updating. I don't remember if it said it'd do said reboot...
> following all the attention the HN thread from the other day got
That's great for you, and no offense, but what about developers who can't get buzz in a HN thread? Are they just doomed? Why is support only available to those who can raise a ruckus on social media?
The broader general problem is that it should not be necessary to attempt amplification of a message via HN or X or other platforms to get a company to have a real human pay attention to something, and write a hand crafted response.
This seems to increasingly be the norm with people who have had their accounts locked, deleted or restricted by automated systems. You have to hope that you can write a message and get it amplified via some sort of platform read by hundreds of thousands of people, and get people to reshare your message, in order to get any form of traction.
If you're not somebody well known, noteworthy or somehow significant in a community your likelihood of having your message successfully amplified is much lower.
Your work is always appreciated.