But while using Wintun is an improvement over tap-windows, it doesn't change the need for constant context switches from kernel space (where the "real" network stack lives) and userspace (where OpenVPN and wireguard-go both live).
On Windows, that means being a proper in-kernel device driver.
Ditching userspace components of the WireGuard stack on Windows, and keeping everything in-kernel means changing WireGuard to work on Windows the way it works on Linux already.In fact, WireGuardNT began as a direct port of the Linux in-kernel WireGuard implementation.
The end result is a deeply integrated and highly performant implementation of WireGuard for the NT kernel, that makes use of the full gamut of NT kernel and NDIS capabilities.".
WireGuardNT is available for testing in the general Windows download for WireGuard now, as of version 0.4.Next, create a key named WireGuard, and within that key, a DWORD named ExperimentalKernelDriver.