WireGuard for Windows "cq is corrupt" panic in rio_windows.go after insufficient buffer space

Joshua Sjoding joshua.sjoding at scjalliance.com
Thu Apr 8 23:41:08 UTC 2021

To my knowledge the log is complete. I didn't see any personally
identifiable information in it so I sent it as-is without
modification. It was produced directly via WireGuard's save button on
the Log tab.

On Thu, Apr 8, 2021 at 4:13 PM Jason A. Donenfeld <Jason at zx2c4.com> wrote:
> Hi Joshua,
> Thanks for the log. It seems like Windows' Registered I/O extensions
> still are causing issues...
> Is the log that you sent me "complete"? I'm asking because it appears
> there are only 2032 WSAENOBUFS lines, rather than the 2048 or 2047 or
> 2049 that I'd expect to see.
> Jason

More information about the WireGuard mailing list