| ▲ | zx2c4 5 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. |
|
| ▲ | sammy2255 4 hours ago | parent | next [-] |
| 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.. |
| |
| ▲ | SturgeonsLaw 3 hours ago | parent | next [-] | | 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... | |
| ▲ | Xunjin 4 hours ago | parent | prev | next [-] | | 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. | |
| ▲ | Leherenn 4 hours ago | parent | prev | next [-] | | 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. | | |
| ▲ | fhn 16 minutes ago | parent | next [-] | | With Microsoft, I assume malice AND negligence first. The hostility they've shown toward their own users tells you everything you need to know. | |
| ▲ | PeterStuer 4 hours ago | parent | prev [-] | | "so I would assume a bug on their side" Why a "bug". | | |
| ▲ | Leherenn an hour ago | parent | next [-] | | I doubt someone manually went and flagged all the accounts as invalid suddenly or whatever and that was their goal.
By a bug I mean some kind of automated action that did not produce the expected outcome. Also because, at least on our side, the account was in an inconsistent state: we were correctly enrolled/validated, but could not access the signing interface. | |
| ▲ | alekratz 3 hours ago | parent | prev [-] | | For something like this, I would generalize a "bug" to encompass both software and human processes. Some decision-maker saw some metrics consistent with spam and enacted a spam-blocking measure. Any decision like this is going to lead to false positives. Maybe they decided "I don't need to confer with anyone", or maybe they did and got the green light even after multiple eyeballs looked at it. I'm not saying that this does any good for Microsoft's already-sullied trust, but mistakes happen and combating spam is a constantly evolving arms race. There's no way any organization is going to get it 100% of the time even after decades of dealing with it. |
|
| |
| ▲ | mavhc an hour ago | parent | prev [-] | | https://techcommunity.microsoft.com/blog/hardware-dev-center... |
|
|
| ▲ | BLKNSLVR 5 hours ago | parent | prev | next [-] |
| Off topic: Thanks for wireguard. It is a truly great piece of software. |
|
| ▲ | e12e 3 hours ago | parent | prev | next [-] |
| 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. |
| |
| ▲ | zx2c4 2 hours ago | parent [-] | | 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. | | |
| ▲ | EvanAnderson an hour ago | parent [-] | | 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. |
|
|
|
| ▲ | EvanAnderson 2 hours ago | parent | prev | next [-] |
| I really appreciate what you wrote in that post re: dropping support for pre-Windows 10 operating systems. |
| |
| ▲ | rkagerer 24 minutes ago | parent [-] | | 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) |
|
|
| ▲ | worble 19 minutes ago | parent | prev | next [-] |
| > 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? |
|
| ▲ | unquietwiki 4 hours ago | parent | prev | next [-] |
| 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... |
|
| ▲ | politelemon 2 hours ago | parent | prev | next [-] |
| Your work is always appreciated. |
|
| ▲ | 4 hours ago | parent | prev [-] |
| [deleted] |
