The location of WireSock logs depends on the mode in which WireSock is operated. When running as a service, logs are stored at C:\ProgramData\NT KERNEL\WireSock VPN Client. For console application mode, logging happens directly in the console. In the case of WireSockUI, logs are only accessible in the specific tab where you attached your screenshot.
From the screenshot you’ve provided, it seems the Wireguard handshake isn’t being acknowledged, causing the tunnel to attempt restarts and continuously send new handshakes. Notably, if your VPN provider’s app connects without issue, it’s important to mention that VPN providers often use the reserved fields of the Wireguard protocol for specific purposes. Cloudflare, for instance, does this but still supports the standard Wireguard client. Without detailed information about your VPN provider, I cannot discount the possibility that they might be using similar techniques or subtly nudging users towards their own client software.