Windows Tunnl.dll fails to start as a service.

[Simon Rozman]

Hi,

> Log Name:      System
> Source:        Service Control Manager
> Date:          1/21/2021 9:41:25 AM
> Event ID:      7024
> Task Category: None
> Level:         Error
> Keywords:      Classic
> User:          N/A
> Computer:      MANI-WIN10-TEST
> Description:
> The ProsimoTunnel_if_cbc2a056dfdc25f7 service terminated with the
> following service-specific error:
> The system cannot find the path specified.

"The system cannot find the path specified." <= is your service path correct? Double check it. Mind the path deflection for WoW64 processes. SCM is always native (x64 on x64 Windows, x86 on x86 Windows...). So, the service path must match the path as a native process would see it.

Or is it just the fact that something returns status 2 which is interpreted as ERROR_FILE_NOT_FOUND by the Event Log?

> 2021-01-21 10:04:20.181831: [TUN] [if_1ea7d00c23a616b1] Creating Wintun
> interface
> 2021-01-21 10:04:20.896480: [TUN] [if_1ea7d00c23a616b1] Using
> Wintun/0.8 (NDIS 6.83)
> 2021-01-21 10:04:20.909065: [TUN] [if_1ea7d00c23a616b1] Enabling
> firewall rules
> 2021-01-21 10:04:22.126556: [TUN] [if_1ea7d00c23a616b1] Starting
> WireGuard/0.1.1 (Windows 10.0.19041; amd64)
> 2021-01-21 10:04:22.127580: [TUN] [if_1ea7d00c23a616b1] Watching network
> interfaces
> 2021-01-21 10:04:22.128604: [TUN] [if_1ea7d00c23a616b1] Resolving DNS
> names
> 2021-01-21 10:04:22.135234: [TUN] [if_1ea7d00c23a616b1] Creating Wintun
> interface
> 2021-01-21 10:04:24.156638: [TUN] [if_1ea7d00c23a616b1] Starting
> WireGuard/0.1.1 (Windows 10.0.19041; amd64)
> 2021-01-21 10:04:24.159365: [TUN] [if_1ea7d00c23a616b1] Watching network
> interfaces
> 2021-01-21 10:04:24.159365: [TUN] [if_1ea7d00c23a616b1] Resolving DNS
> names
> 2021-01-21 10:04:24.165375: [TUN] [if_1ea7d00c23a616b1] Creating Wintun
> interface
> 2021-01-21 10:04:24.616820: [TUN] [if_1ea7d00c23a616b1] Unable to create
> Wintun interface: Error registering rings: Error listing NDIS
> interfaces: no interfaces found

Wintun 0.8 is out of our support. Please, upgrade your wireguard-go and Wintun to the latest version first and see if the problem persists.

Why is that important? Because, we completely rewrote the wireguard-go <-> Wintun communication in v0.0.20201118 and v0.10 respectively. The issue you are seeing is triggered in a part of the code that is now gone from wireguard-go and has been rewritten in the new wintun.dll.

(The new Wintun no longer ships as a driver package you need to install, but rather as a self-contained do-it-all DLL. Don't worry, the new wireguard-go knows how to use it. Just add wintun.dll next to it.)

Regards,
Simon