This stuff is a pain, but in the long run it's a good move in terms of computer security. Certificates cost in the vicinity of $100 at the entry level, and you can look up instructions/tutorials on the commands used to perform the signing.

Demonstrates that the data they're receiving is the same data you packaged up, ie: it hasn't been messed with somewhere in the middle.Ĭode signing is a little fiddly, but it's easy enough.

If you're willing to put your name on something saying it's safe then people are more willing to trust it. That encodes data into your executable that does two things:

To do this, you buy yourself a code signing certificate and sign your application before you send it to people. The scariest bit of that warning screen that appears is 'Unknown Publisher', and you can change that so that it says your name instead.

However, you can make that screen a heck of a lot less doom-and-gloom if you code-sign your application. Click to expand.You can't completely prevent it from happening without your program becoming widely used enough that SmartScreen learns to recognise and trust it.

Windows protected your pc run anyway