DNS Client dependency glitch in Windows binaries

[magicmuffin at firemail.cc]

On Windows the Wireguard client will halt activating a tunnel if:
-The DNS Client service is disabled
-The DNS Client service is enabled, but the hosts file of the operating 
system has sufficiently many entries that it causes the DNS Client to 
lag, which causes a timeout in Wireguard that brings the tunnel down. 
This usually happens when the hosts file is a few megabytes large.

Workarounds:
-Ensure the DNS Client service is not disabled
-Rename the hosts file before bringing the tunnel up