Conversation

Yeah, I think the solution is getting an OV code signing certificate which is probably ~$70-100/year. I don't know the cheapest option. An EV certificate appears to start out as reputable but costs ~$200-300/year and the EV verification process likely involves further costs too.
Can also use OV code signing instead of EV (cheaper) but it will take longer for the executables to be trusted. A self-signed certificate may be better than nothing. It's possible that it will help the reputation of the previous releases transfer over to the current ones.
1
1
It sounds like an EV code signing certificate will outright get rid of the warnings. An OV code signing certificate is a lot cheaper and it won't be marked as from an unknown publisher but there will likely still be warnings. It would presumably get better over time though.