For those who use VPNs:
The WireGuard project has announced the experimental release of a Windows NT kernel module for the VPN protocol. For now, it's hidden behind a registry tweak (WireGuard version 0.4 and above), which can be added with, in a command prompt:
Restart WireGuard and you'll be using the in-kernel implementation rather than the userspace-go version. Initial results suggest full gigabit with 0% CPU usage over Ethernet, and >600Mbps with minimal latency over WiFi 6. This is a significant jump over the previous userspace implementation, and puts Windows networking performance on par with that of Linux, OpenBSD etc. Congrats to Jason and the team.
As the 'experimental' tag denotes, this is early doors. I've found absolutely no issues under heavy testing and throughput has been amazing (Windows 10 Enterprise x64/Windows 10 Pro for Workstations, Intel I211 NIC) but there have been a few reports on Reddit of blue/green screens with some Win10 and Win11 installs. The posters didn't seem very technical though, so a pinch of salt required perhaps (underlying issues, incorrect application of the reg key etc).
Edit: Kernel driver version 0.2 released (part of the WireGuard app update) to address a crash in Windows 10 and 11.
The WireGuard project has announced the experimental release of a Windows NT kernel module for the VPN protocol. For now, it's hidden behind a registry tweak (WireGuard version 0.4 and above), which can be added with, in a command prompt:
Code:
reg add HKLM\Software\WireGuard /v ExperimentalKernelDriver /t REG_DWORD /d 1 /f
Restart WireGuard and you'll be using the in-kernel implementation rather than the userspace-go version. Initial results suggest full gigabit with 0% CPU usage over Ethernet, and >600Mbps with minimal latency over WiFi 6. This is a significant jump over the previous userspace implementation, and puts Windows networking performance on par with that of Linux, OpenBSD etc. Congrats to Jason and the team.

As the 'experimental' tag denotes, this is early doors. I've found absolutely no issues under heavy testing and throughput has been amazing (Windows 10 Enterprise x64/Windows 10 Pro for Workstations, Intel I211 NIC) but there have been a few reports on Reddit of blue/green screens with some Win10 and Win11 installs. The posters didn't seem very technical though, so a pinch of salt required perhaps (underlying issues, incorrect application of the reg key etc).
Edit: Kernel driver version 0.2 released (part of the WireGuard app update) to address a crash in Windows 10 and 11.
Last edited: