Sorry, x86_64 version will not be considered for the time being. That will increase the workload of release and maintenance. At present, x86 version can run well in various systems, including Windows 11. Although the system resources cannot be fully utilized, there are no reports of insufficient performance.

The current focus is still on developing new features, and when the development of new features is almost complete, I will release the x86_64 version. Please stay tuned, thank you.

For example, its cmd shortcut starts 32bit cmd because Windows redirected the path to C:\Windows\SysWOW64\cmd.exe . The powershell which starts from Windterm faces the same problem and the 32bit powershell may not able to call 64bit dll modules.

When scanning cmd and powershell to generate the default shells, WindTerm does only automatically scan the 32-bit cmd and powershell, which is intended to provide better compatibility. But as you said, 64-bit modules cannot be run. The solution is very simple, you can create a 64-bit cmd or powershell session configuration by yourself.

• New session and select Shell tab.
• Select Custom from the Shell - Shell drop-down box.
• Input the x64 path of cmd or powershell in the Shell - Shell combo box.
• Done.

The default 64-bit cmd and powershell will be added in the next version, and this does not require WindTerm to be compiled into a 64-bit program. Thank you.

In my test, although using the latest release, the problem of cmd and powershell still exists. Windows will redirect C:\Windows\System32\cmd.exe to C:\Windows\SysWOW64\cmd.exe.
As what Windows does, I think 64bit version is needed to be released ASAP.

You are right, it was the same in my test. And It is currently planned that after switching to the Qt 6.2 in early December, WindTerm 2.4 will provide x86_64 version. Please stay tuned, thank you.