WinSCP fails both manually and automated on W10 20H2 with latest tool build

I think its related to a registry key creating that Tim M talked about earlier.

Chacon

Microsoft

Oct 28, 2020

Hi xenappblog

I tried converting WinSCP and I believe the error you are seeing is due to an invalid protocol association. The MSIX Packaging Tool creates this protocol association:

<uap10:Protocol Name="s3" Parameters="/Unsafe &quot;%1&quot;">
  <uap:DisplayName>s3</uap:DisplayName>
  <uap:Logo>Assets\dav.png</uap:Logo>
</uap10:Protocol>

It should be using uap3:Protocol, not uap10:Protocol. There are other protocol associations, but only this one seems to be invalid.

To fix this you can edit the manifest file manually using the Package Editor. To do this, in the "Create new package" page of the tool, click "Package editor" instead of "Create" and then look for the "Open file" button at the bottom of the page.

xenappblog

Copper Contributor

Oct 29, 2020

Thanks Luis that worked. Here's the script if anyone wants to play
https://github.com/haavarstein/Applications/tree/master/Misc/WinSCP

Forum Discussion

WinSCP fails both manually and automated on W10 20H2 with latest tool build

Resources