Windows native hev-socks5-server.exe UDP ASSOCIATE and FWD UDP (udp-over-tcp) not working

[ibrahemesam]

I tried running this config

main:
  workers: 1
  port: 20170
  listen-address: '0.0.0.0'
  listen-ipv6-only: false
  bind-address: '0.0.0.0'
  bind-interface: ''
  domain-address-type: unspec

misc:
  log-level: info

with:
1- linux build (hev-socks5-server-linux-x86_64) running natively
2- windows build (hev-socks5-server.exe) running via wine on linux
3- windows build (hev-socks5-server.exe) running natively

I tested them on my android phone
using SocksTun.apk
I enabled app option ✅ UDP relay over TCP

result:-

on native hev-socks5-server-linux-x86_64 and hev-socks5-server.exe when run under wine: UDP works well

$ dig @1.1.1.1 google.com

; <<>> DiG 9.20.17 <<>> @1.1.1.1 google.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45453
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;google.com.                    IN      A

;; ANSWER SECTION:
google.com.             263     IN      A       216.58.212.46

;; Query time: 184 msec
;; SERVER: 1.1.1.1#53(1.1.1.1) (UDP)
;; WHEN: Mon Feb 09 23:05:47 EET 2026
;; MSG SIZE  rcvd: 55

on native hev-socks5-server.exe when run naitively on Windows 10: UDP not working

$ dig @1.1.1.1 google.com

;; communications error to 1.1.1.1#53: timed out
;; communications error to 1.1.1.1#53: timed out
;; communications error to 1.1.1.1#53: timed out

; <<>> DiG 9.20.17 <<>> @1.1.1.1 google.com
; (1 server found)
;; global options: +cmd
;; no servers could be reached

is there a special config for windows version to get UDP-over-TCP working ??

---

UPDATE: even UDP ASSOCIATE is not working

I tried testing using this tutorial How to Test UDP over SOCKS
Result on native windows:

C:\Users\w.i\Downloads\test>python-3.8.5-embed-amd64\python.exe test.py
SOCKS5 UDP Support Tester
================================================================================
📂 Reading proxies from: proxy.txt
📖 Loaded 1 proxies from proxy.txt

🔍 Testing SOCKS5 proxy: 127.0.0.1:20170
==================================================
✅ Connected with no authentication
✅ UDP ASSOCIATE command accepted
✅ UDP relay endpoint: 127.0.0.1:57578
🔄 Testing UDP relay by sending DNS query through 127.0.0.1:57578
❌ No response from UDP relay (timeout)

================================================================================
📊 SUMMARY
================================================================================
127.0.0.1:20170                     | ⚠️  UDP ASSOCIATE ONLY (relay not working)

📈 STATISTICS
================================================================================
Total proxies tested: 1
✅ Full UDP support: 0
⚠️  Partial UDP support: 1
❌ No UDP support: 0
💥 Connection failed: 0

Result on Linux and Wine:

SOCKS5 UDP Support Tester
================================================================================
📂 Reading proxies from: proxy.txt
📖 Loaded 1 proxies from proxy.txt

🔍 Testing SOCKS5 proxy: 127.0.0.1:20170
==================================================
✅ Connected with no authentication
✅ UDP ASSOCIATE command accepted
✅ UDP relay endpoint: 127.0.0.1:10170
🔄 Testing UDP relay by sending DNS query through 127.0.0.1:10170
✅ Received UDP response from relay (134 bytes)
✅ UDP relay is working correctly!

================================================================================
📊 SUMMARY
================================================================================
127.0.0.1:20170                     | ✅ FULL UDP SUPPORT

📈 STATISTICS
================================================================================
Total proxies tested: 1
✅ Full UDP support: 1
⚠  Partial UDP support: 0
❌ No UDP support: 0
💥 Connection failed: 0

test.py
proxy.txt

[tempask]

我这两天遇到类似问题，不是 windows 下，在 linux 下，udp-over-tcp 方式域名解析失败，对应进程会崩溃（foxyproxy, curl 一样结果），我想自行改代码来纠正对应错误，结果发现对应可执行文件在生成机器上同样的请求没有问题（我是在本地一个 x86-64 ubuntu 上生成的可执行文件），而在对应的 x86-64 的 vps （系统是 debian 12 ）上运行就会有问题，这个生成的可执行文件是静态链接的（native gcc），同时我生成了 musl 版本的可执行文件，我换成 musl 版本的可执行文件就没有问题了，从测试的结果来看对应的源代码很可能没有问题（仅指 udp-over-tcp相关代码），问题跟编译、链接有关系。