Remote server 0.226.0 crashes on Windows due to missing application manifest

[K-Finlay]

Reproduction steps

1. Update Zed to preview 0.226.0
2. Connect to a Windows machine via SSH remote development
3. The remote server binary downloads/installs but fails to start

Current vs. Expected behavior

Current: The remote server crashes at startup with exit code 0xC0000139 (STATUS_ENTRYPOINT_NOT_FOUND). The connection hangs and eventually fails.

Expected: The remote server starts and the SSH remote session connects successfully (as it does with 0.225.9).

Root cause: The 0.226.0 remote server binary is missing its entire .rsrc PE section, which means no Windows application manifest.
The 0.225.9 binary has one that declares Windows 10 compatibility and a dependency on Common Controls v6.
Without it, Windows loads the legacy comctl32.dll v5 instead of v6, which then causes a crash.

I confirmed this by extracting the manifest from 0.225.9 and embedding it into 0.226.0 using the UpdateResource Win32 API. The patched binary runs as expected.

Zed version and system specs

Zed: v0.226.0+preview.182.8da83f8521d383c123d022455fac01f4f26ba0af (Zed Preview)
OS: Linux Wayland bluefin 43
Memory: 30.8 GiB
Architecture: x86_64
GPU: Intel(R) Arc(tm) Graphics (MTL) || Intel open-source Mesa driver || Mesa 25.3.5

Attach Zed log file

Zed.log

Relevant Zed settings

settings.json

Relevant Keymap

keymap.json

(for AI issues) Model provider details

No response

If you are using WSL on Windows, what flavor of Linux are you using?

None

[yeskunall]

Hey @K-Finlay thanks for the report! I’m taking a look right now.

[yeskunall]

John (@/reflectronic) already made a PR that will fix this.