I am a total newbie here. I tried the Tolaria app and set it uo with claude code, what worked fine. But then I always get this error message:
Error: Failed to spawn claude: %1 ist keine zulässige Win32-Anwendung. (os error 193)
I searched the web and found this solution, but could not get along with it:
This issue has been mitigated by the bundled CLI binary. Since v0.1.20+, the SDK bundles a native platform-specific binary. On Windows, _find_bundled_cli() explicitly looks for claude.exe:
cli_name = "claude.exe" if platform.system() == "Windows" else "claude"
The bundled binary takes priority over shutil.which() discovery, so users will get the correct native executable by default without encountering the WinError 193 bash-script issue.
Additionally, shutil.which("claude") on Windows respects the PATHEXT environment variable and should correctly find claude.cmd/claude.exe even in the fallback path.
Closing as resolved — the bundled binary approach avoids this problem entirely. If you're still hitting this on a recent SDK version, please reopen with details.
Someonoe can help?
I am a total newbie here. I tried the Tolaria app and set it uo with claude code, what worked fine. But then I always get this error message:
Error: Failed to spawn claude: %1 ist keine zulässige Win32-Anwendung. (os error 193)
I searched the web and found this solution, but could not get along with it:
This issue has been mitigated by the bundled CLI binary. Since v0.1.20+, the SDK bundles a native platform-specific binary. On Windows, _find_bundled_cli() explicitly looks for claude.exe:
cli_name = "claude.exe" if platform.system() == "Windows" else "claude"
The bundled binary takes priority over shutil.which() discovery, so users will get the correct native executable by default without encountering the WinError 193 bash-script issue.
Additionally, shutil.which("claude") on Windows respects the PATHEXT environment variable and should correctly find claude.cmd/claude.exe even in the fallback path.
Closing as resolved — the bundled binary approach avoids this problem entirely. If you're still hitting this on a recent SDK version, please reopen with details.
Someonoe can help?