Copy Handler is being signed with SHA1 instead of SHA256

Currently Copy Handler is signed with default settings of signtool executable, defaulting to SHA1 signature.
However Microsoft has updated the Authenticode rules in a way that SHA1 signatures with newer timestamps are considered invalid (appears in IE and Edge as corrupted signature) and starting with 1st of Jan 2017, it will be treated as if there is no signature at all.

It seems the following article has some more information and the possible solution:
http://support.ksoftware.net/support/solutions/articles/215805-the-truth-about-sha1-sha-256-and-code-signing-certificates-