06-30-2020 01:07 PM
06-30-2020 01:07 PM
I created MSIX file and later signing the package with this command
signtool sign /fd SHA256 /v /sm /s My /n "ABC Corporation" /t http://timestamp.digicert.com file.msix
But signing failed with this error:
Sign tool Error: This file format cannot be signed because it is not recognized.
Appreciate any suggestions to resolve this issue
07-10-2020 09:13 AM
@Sri-Boddupalli This usually indicates an issue with the package (corrupted file etc.). You should get back to packaging and make the package "simpler" and see if signing works.
07-13-2020 03:53 PM
Hi @Sri-Boddupalli ,
Try setting this registry key:
Under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\AppxSIP; set LogLevel as DWORD to 3
Rerun the Signtool Command and you should see additional logging that may be insightful to your problem.
If that does not help, please share the additional logging with us to review. As with any logs or data you share, please review it before hand for any personal or sensitive information that you would not want to share in a public forum.
07-14-2020 11:44 PM
@Sri-Boddupalli you can try it with the pfx file, maybe it helps;
SignTool.exe sign /fd SHA256 /a /f devcert.pfx /p <pwd> ./abc.msix
07-15-2020 03:33 PM
Thank you guys for your valuable suggestions, appreciate your time on this. This is a repeated post
1) Change the Path to Signtool Location below
C:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0\x64
2) Sign the Package using this command
.\signtool.exe sign /v /sm /s My /n "ABC Corporation" /fd SHA256 /t http://timestamp.digicert.com "<FileLocation>\File.msix"
It was so frustrating to fight with AD team on getting the .PFX file with Password. I understand their security concerns but without that we are pretty much helpless. @John Vintzel @Sharla Akers Any better explanation I can come up with, if our AD team ask why exactly we need .PFX file instead of installing the certificate in cert store and using that? OR if you could develop a Signtool GUI utility that would be wonderful