Subject: Fix found (in my case): WSL virtual adapter on the SERVER breaks discovery Same symptom as OP: desktop client stuck on "Looking up for servers..." forever, refresh unclickable. Server = Windows 11 Pro, client = Windows 10 Pro, both on latest Enpass, same Wi-Fi SSID/band, both network profiles Private. What I ruled out first: TCP path was fine: Test-NetConnection <server-ip> -Port <sync-port> succeeded from the client, even with firewalls on (after allowing the three Enpass entries — Enpass, mDNS discovery, wifisyncserver_bin — on Private) OS-level mDNS was fine: ping <servername>.local resolved from the client Firewalls fully disabled on both machines: still spinning So multicast and unicast both worked, but Enpass's own discovery didn't. The fix: the server had a vEthernet (WSL (Hyper-V firewall)) adapter active. I shut down WSL and disabled that adapter (elevated PowerShell): wsl --shutdown
Disable-NetAdapter -Name "vEthernet (WSL (Hyper-V firewall))"
Then fully quit and relaunch Enpass on the server (tray icon → quit — the restart matters, the server seems to bind interfaces at startup). Client discovered the server immediately after that. My guess is the Wi-Fi Sync server binds or advertises the WSL NAT interface (172.x) instead of the LAN interface, so clients either never hear the announcement or get an unreachable address. Note for others in this thread: disabling virtual adapters on the client didn't help me either — it had to be the server's virtual adapter, followed by an Enpass restart. Once a client is paired, sync keeps working even with WSL running again — discovery only matters at pairing time. Hope this helps someone. Enpass team: an interface-binding option (or just preferring the default-route interface) would fix this class of problem properly.