Windows Update 24H2 Build 26100.2314 seem to break this software

[Azuresonance]

Describe the bug

My Shadowsocks-windows doesn't work after a recent windows update (24H2, Build 26100.2314).
From shadowsocks' logs, shadowsocks seems to be proxying socket connections normally, but the downstream application (e.g. Chrome, FreeDownloadManager, etc.) sees a connection timeout.
My other machines with older versions of Windows works alright under the same settings (23H2, Build 22635.4580).

我的机器进行了一次最新的windows更新后，shadowsocks-windows突然不能用。
从shadowsocks的log来看，shadowsocks本身应该是在正常转发连接，但下游应用（比如Chrome和FDM）会遭遇连接超时。
我的其他电脑有老版本的Windows，在同样设置下工作正常。

Environment

• Shadowsocks client version: 4.4.1.0
• OS version: 24H2 Build 26100.2314
• .NET version:

Steps you have tried

1. Turned on Global Proxy in shadowsocks-windows, and changed Chrome/SwitchyOmega to use system proxy, doens't fix it.
2. Tried to use other applications to connect to shadowsocks-windows, such as using Free Download Manager to download ubuntu's ISO with proxy set to localhost:1080, it is still a timeout This means it's not the Chrome/Switchyomega's problem.
3. Tried to use a different machine with older windows version, works.
4. Tried to check the shadowsocks' verbose DEBUG logs, shadowsocks seem to be proxying socket connections normally.
5. Checked my ss-server side backend logs, server is accepting connections normally.
6. Chcked windows firewall settings, shadowsocks-windows is allowed to listen.
7. Checked netstat -ano, shadowsocks-windows process is indeed listening on port 1080.
8. Tried to use Linux's ss-server in WSL2 instead of shadowsocks-windows on the host, it works. This means my machine's internet connection is good.
9. Tried to run shadowsocks-windows in window's compatibility mode (Windows 8 mode), doesn't work.
10. Tried to run shadowsocks-windows as administrator, doesn't work.

What did you expect to see?

The French Wikipedia page (or any other webpage) should be loaded.

What did you see instead?

Chrome saying "fr.wikipedia.org took too long to respond"

Config and error log in detail (with all sensitive info masked)

Shadowsocks-windows' log is as follows. I am using French Wikipedia as an example here, because it has a distinct URL. When I try to access fr.wikipedia.org, I get this in the log, which seems very normal:

2024-12-13 16:36:01.9137|DEBUG|Shadowsocks.Controller.TCPHandler|connect to fr.wikipedia.org:443
2024-12-13 16:36:01.9137|DEBUG|Shadowsocks.Controller.TCPHandler|connect to fr.wikipedia.org:443
2024-12-13 16:36:01.9137|DEBUG|Shadowsocks.Controller.TCPHandler|Socket connected to ss server: home.myexampleproxy.com:11346
2024-12-13 16:36:01.9137|DEBUG|Shadowsocks.Controller.TCPHandler|Socket connected to ss server: home.myexampleproxy.com:11346
2024-12-13 16:36:02.1661|DEBUG|Shadowsocks.Controller.TCPHandler|connect to optimizationguide-pa.googleapis.com:443
2024-12-13 16:36:02.1661|DEBUG|Shadowsocks.Controller.TCPHandler|connect to fr.wikipedia.org:443
2024-12-13 16:36:02.1661|DEBUG|Shadowsocks.Controller.TCPHandler|Socket connected to ss server: home.myexampleproxy.com:11346
2024-12-13 16:36:03.1891|DEBUG|Shadowsocks.Controller.TCPHandler|Socket connected to ss server: home.myexampleproxy.com:11346
2024-12-13 16:36:03.3193|INFO|Shadowsocks.Controller.TCPHandler|home.myexampleproxy.com:11346 timed out
2024-12-13 16:36:04.9407|DEBUG|Shadowsocks.Controller.TCPRelay|Closing timed out TCP connection.
2024-12-13 16:36:04.9407|DEBUG|Shadowsocks.Controller.TCPHandler|connect to fr.wikipedia.org:443
2024-12-13 16:36:04.9407|DEBUG|Shadowsocks.Controller.TCPRelay|Closing timed out TCP connection.
2024-12-13 16:36:04.9528|DEBUG|Shadowsocks.Controller.TCPHandler|connect to fr.wikipedia.org:443
2024-12-13 16:36:04.9694|DEBUG|Shadowsocks.Controller.TCPHandler|Socket connected to ss server: home.myexampleproxy.com:11346
2024-12-13 16:36:04.9694|DEBUG|Shadowsocks.Controller.TCPHandler|Socket connected to ss server: home.myexampleproxy.com:11346
2024-12-13 16:36:05.2378|DEBUG|Shadowsocks.Controller.TCPHandler|connect to optimizationguide-pa.googleapis.com:443
2024-12-13 16:36:05.2536|DEBUG|Shadowsocks.Controller.TCPHandler|Socket connected to ss server: home.myexampleproxy.com:11346

Here is my gui-config.json:

{
  "version": "4.4.1.0",
  "configs": [
    {
      "server": "home.myexampleproxy.com",
      "server_port": 11346,
      "password": "myfancypassword",
      "method": "chacha20-ietf-poly1305",
      "timeout": 5,
      "warnLegacyUrl": false
    }
  ],
  "onlineConfigSource": [],
  "strategy": null,
  "index": 3,
  "global": true,
  "enabled": false,
  "shareOverLan": true,
  "firstRun": false,
  "localPort": 1080,
  "portableMode": true,
  "showPluginOutput": false,
  "pacUrl": "",
  "useOnlinePac": false,
  "secureLocalPac": true,
  "regeneratePacOnUpdate": true,
  "autoCheckUpdate": false,
  "checkPreRelease": false,
  "skippedUpdateVersion": "",
  "isVerboseLogging": true,
  "isIPv6Enabled": false,
  "generateLegacyUrl": false,
  "geositeUrl": "",
  "geositeSha256sumUrl": "",
  "geositeDirectGroups": [
    "private",
    "cn",
    "geolocation-!cn@cn"
  ],
  "geositeProxiedGroups": [
    "geolocation-!cn"
  ],
  "geositePreferDirect": false,
  "userAgent": "ShadowsocksWindows/$version",
  "logViewer": {
    "topMost": false,
    "wrapText": false,
    "toolbarShown": false,
    "Font": "Consolas, 8pt",
    "BackgroundColor": "Black",
    "TextColor": "White"
  },
  "proxy": {
    "useProxy": false,
    "proxyType": 0,
    "proxyServer": "",
    "proxyPort": 0,
    "proxyTimeout": 3,
    "useAuth": false,
    "authUser": "",
    "authPwd": ""
  },
  "hotkey": {
    "SwitchSystemProxy": "",
    "SwitchSystemProxyMode": "",
    "SwitchAllowLan": "",
    "ShowLogs": "",
    "ServerMoveUp": "",
    "ServerMoveDown": "",
    "RegHotkeysAtStartup": false
  },
  "WebProxy": null
}

[Azuresonance]

Update:
I rolled back Windows to 23H2 (Build 22631.4541) using Windows Update Setting, shadowsocks-windows works flawlessly.
This should confirm it is the update causing this.

[Maks-Shemelin]

I have the same issue

[novrain99]

The last version still under maintenance?