acv on Nostr: It works for me when I run the MSI manually and tell it to go ahead anyway, but I ...
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.
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.