Windows SmartScreen thinks nheko is dangerous

[turt2live]

Signing the code (either Standard or EV) should make Windows agree that the file is safe.

[MTRNord]

This could be because the installer isn't signed. I am not sure if there is any other way to prevent that except for singing the setup exe. Sadly certs for signing are extremly expensive. If you know better please tell ^^ Signing Certs start at 175$ (symantec))

[MTRNord]

This could also work: http://stackoverflow.com/a/28359323/4929236 (Still requires an EV cert)

PS hacking via regedit and things like that are possible but not wanted I guess.

[MTRNord]

It could also be the security flag inside the Details of the file. Do a right click and Allow it to be run. If you do that it won't show the SmartScreen.

There is no other way than doing it manually or buying a EV Cert yearly.

[turt2live]

It looks like you can avoid EV certs if you sign the code with a real publisher (right now there is none). Eventually microsoft will build up the reputation for you and you'll get less and less reports. EV skips this reputation building.

[mujx]

I'm not at all familiar with Windows or code signing but from a quick research I came to the same conclusion as @MTRNord . @turt2live is there a free of charge way to handle SmartScreen's warnings?

[turt2live]

Technically there is, it just takes a while. You are able to self-sign the certificate and use it, however it requires time for your certificate's reputation to get high enough to stop the warning. EV is the quick route, despite cost.

[MTRNord]

might be partialy fixed with the qt installer framework. atleast my chrome only seems to scream in about 40% instead of always. But the chrome issue might be related to appveyor not to nheko or the exe itself.

[turt2live]

The rate is probably going down because of constant use. As it builds trust, it'll warn less, although that is mostly on a per-user level.