[v1.0.216] Cannot launch WinSCP

[spiderock98]

Describe the problem:
Cannot launch WinSCP on lastest release v1.0.216. Back to 1.0.215 and its back

To Reproduce:
Use shortcut or right-click menu

[cnrenil]

Log in console:

error_handler.ts:45 ERROR Error: Uncaught (in promise): Error: Command failed: D:\Tools\WinSCP\WinSCP.com /keygen C:\Users\24844\AppData\Local\Temp\tmp-43856-flIBf8GEB0Bi /output=C:\Users\24844\AppData\Local\Temp\tmp-43856-flIBf8GEB0Bi

Error: Command failed: D:\Tools\WinSCP\WinSCP.com /keygen C:\Users\24844\AppData\Local\Temp\tmp-43856-flIBf8GEB0Bi /output=C:\Users\24844\AppData\Local\Temp\tmp-43856-flIBf8GEB0Bi

C:\Users\24844\AppData\Local\Temp\tmp-43856-flIBf8GEB0Bi is empty
and i believe this is a bug

[oPhilMehr]

Hi all,

I have the same problem since updating to Tabby version 1.0.219 (Windows 10 Host (10.0.19045)).
With Tabby version 1.0.215, opening WinSCP worked fine.

Some additional info: It only seems to affect SSH hosts configured with a public/private key authentication.
SSH Hosts with password authentication still work fine.

On my host, only empty C:\Users\user\AppData\Local\Temp\tmp-xyz-abc files were generated, too.

Output of WinSCP would be:

C:\Users\user>"C:\Program Files (x86)\WinSCP\WinSCP.com" /keygen "C:\Users\user\AppData\Local\Temp\tmp-26388-kIX2D9gFfNF2" /output="C:\Users\user\AppData\Local\Temp\tmp-26388-kIX2D9gFfNF2"
File 'C:\Users\user\AppData\Local\Temp\tmp-26388-kIX2D9gFfNF2' does not contain private key in known format.

I think, the "error" happens somewhere when Tabby tries to export the (vaulted) key file.
In my case, the keys are not stored in the Tabby vault, but in the file system.

Authentication method -> Key
Private keys -> file://C:\Users\user\.ssh\privkey

I haven't tried yet whether WinSCP (or the export of the key for WinSCP) works when the key is stored in the Tabby vault.

Best regards,
Philip