Hi Friedrich,

My client is using a dual code signing certificate and he noticed that
recently he is getting the "unknown publisher" warning in Windows 10.

So we did a test using my Build Automator install. I have one install
with dual code signing and one with my latest certificate which is SHA2

The results: http://www.screencast.com/t/a57gF4yaqJB

The dual code signed one was fine, but the SHA2 only is showing the
"dangerous app" warning! This is on Windows 10 Home 64bit with all the
latest updates (checked as of yesterday afternoon)

I have smartscreen turned ON on my machine, but for the dual code signed
install it does not show up and I get the same UAC screen as for the
dual code signed.

Where is all this going??? Can we expect to get all installs
intercepted by SmartScreen every time a new build goes out or what can
we do?

Does my client need a SHA2 only certificate to code sign his installs?

Best regards,

Arnor Baldvinsson
Icetips Alta LLC