There is no 0.5.3 release.

It works for me without being signed. I don't know why it doesn't work for you.

In order to sign the release I have to

* Learn what these four things are (which in my mind I have no idea how they differentiate or relate): a burn bundle, a cabinet, a package, an MSI. And the documentation is terrible.

* Then I have to install more tooling and more fragile setup crap.

* I will have to maintain an identity somewhere. My windows computer is explicitly insecure, I take NO effort to secure it, it is for low-value stuff only.

IMHO windows is not worth it. Can you upgrade to Linux or MacOS?

Reply to this note

Please Login to reply.

Discussion

It works for me when I run the MSI manually and tell it to go ahead anyway, but I presume it has an update feature because occasionally it stops launching because the binary has changed.

Because the 'new version' wasn't on github, I checked the installed programs list and see its 0.5.3 so something did update the program and change the binary.

Perhaps the auto-update feature can be disabled on Windows, if it's not going to be signed because it stops working if the binary changes.

I don't know where this 0.5.3 version came from, if there is no 0.5.3 release or auto-updater.

I haven't run it successfully or decrypted my key with it, so I'm probably ok, but something changed the install on Windows without my input.

#[1]