title: Visual Studio 2015/Windows 10 SDK SignTool.exe bug?
body: <p>I have a project that I'm upgrading to Visual Studio 2015 but it's still targeting .NET 4.5.1.</p>
  
  <p>Whenever $(WindowsSDKBinPath) is set to the Windows 10 SDK "C:\Program Files (x86)\Windows Kits\10\bin\x86\" the signtool.exe exits with exit code 255 and the output cuts off like the following:</p>
  
  <pre><code>The following certificate was selected:
      Issued to: XXXX
      Issued by: VeriSign Class 3 Code Signing 2010 CA
      Expires:   Tue Apr 11 19:59:59 2017
      SHA1 hash: XXXX
  
  Done Adding Additional Store
  </code></pre>
  
  <p>Usually an error would show up right here if there was going to be an error but that's it, it's cuts off right here and exits with exit code 255.</p>
  
  <p>If $(WindowsSDKBinPath) is set to the Windows 8.1 SDK "C:\Program Files (x86)\Windows Kits\8.1\bin\x86\" then everything is fine.  SignTool.exe signs the dll without any issues and exits with code 0 like normal.</p>
  
  <p>Can anyone help me figure out how to use the newer signtool or at least know why it's not working?  Below is the target I added to my csproj file to get it to sign after building.  Thanks.</p>
  
  <pre><code>&lt;Target Name="AuthenticodeProjectSign" AfterTargets="AfterBuild"&gt;
    &lt;PropertyGroup&gt;
      &lt;AuthenticodeTimestampServerUrl&gt;http://timestamp.verisign.com/scripts/timstamp.dll&lt;/AuthenticodeTimestampServerUrl&gt;
      &lt;TargetAssembly&gt;$(OutDir)$(TargetFileName)&lt;/TargetAssembly&gt;
    &lt;/PropertyGroup&gt;
  
    &lt;Exec Command="&amp;quot;$(WindowsSDKBinPath)signtool.exe&amp;quot; sign /v /sha1 $(AuthenticodeCertificateSHA1) /t $(AuthenticodeTimestampServerUrl) &amp;quot;$(TargetAssembly)&amp;quot;" /&gt;
  &lt;/Target&gt;
  </code></pre>