Tunnel is not getting installed

[rsunny2012]

Hello,

I have installed Wgserverforwindows and created server and client. Until this point everything was working fine. since remote desktop is not working, i have installed teamviwer and rebooted the machine. after reboot, I see that sharing is disabled and tunnel is not getting installed
i dont see wg server network interface as well

how do i fix this issue

[rsunny2012]

i have attached the error message

[micahmo]

Hi @rsunny2012, is there any error when you press "Install tunnel service"?

Can you try running these commands in an admin PowerShell and let me know what happens and if there are any errors?

.'C:\Program Files\WireGuard\wireguard.exe' /uninstalltunnelservice wg_server

.'C:\Program Files\WireGuard\wireguard.exe' /installtunnelservice $env:appdata\WS4W\server_wg\wg_server.conf

[Darkskills127]

I have the same problem. No error displayed. The bug appears randomly on W10 server, W11 server, etc...

Running those commands do nothing. No Windows event or anything to debug.

[patrickleehua]

same problem in windos10

[swillis12]

Same issue here, any workarounds?

@micahmo Attempting to run the above commands (needed to fix the path on the second one) results in an error like this:

Failed to connect NIC 61F35063-F58F-4442-B35A-9ED9D0FD8343--712ED1FC-D690-5B8C-AF21-C212193471A6 (Friendly Name: ) to port 2B16ADBF-319B-41B6-8F0B-F10A4E04D43C (Friendly Name: ) on switch 7734E770-88FB-4FED-B358-DFE3F3433F52 (Friendly Name: ), status = Object Name not found.. UniqueEvent = 80.

The original error that Event Viewer shows when clicking "Install tunnel" from within WGS4W is as follows:

Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C009000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name.

Note: This is on Windows 10

[dcrowson]

I just ran into this same issue. I think it has something to do with ports that are reserved. Using this command, I could see that 51820 was reserved, giving the access denied when trying to start the tunnel:

netsh int ipv4 show excludedportrange protocol=udp

I think this command and a reboot fixed it and allowed the tunnel to start:

reg add HKLM\SYSTEM\CurrentControlSet\Services\hns\State /v EnableExcludedPortRange /d 0 /f

This was on Windows 10.

Dan