Able to sign EXE and MSI package but getting issue while signing MSIX package via sign tool

Copper Contributor

I am using windows-sdk-10-version-1903 in the build testing using signtool from the corresponding sdk
With signtools.exe from C:\Program Files (x86)\Windows Kits\10\bin\10.0.18362.0\x86\signtool.exe I get the error

Done Adding Additional Store
SignTool Error: This file format cannot be signed because it is not recognized.
SignTool Error: An error occurred while attempting to sign: C:\Users\abc123\Downloads\msix-hero-3.0.0.0.msix

2 Replies

Hi @AmitTanwar9291,

the error you’re encountering with SignTool might be due to the file format of the MSIX package not being recognized1. This issue has been reported by others as well12.

Here are a few things you could try:

1. Check the version of SignTool:
Make sure you’re using the correct version of SignTool. It was reported that using signtools.exe from Windows SDK 10.0.17763.0 resolved a similar issue1.
2. Check the file format:
Ensure that the MSIX file is not corrupted and is a recognized file format2. You can only sign recognized file types2.
3. Try a different operating system: Note that .msix/msixbundle signing will not work from all operating systems. For example, it will not work on Windows Server 2016.

SignTool Error: This file format cannot be signed because it is not recognized - Microsoft Q&A

docker - SignTool Error: This file format cannot be signed because it is not recognized. SignTool Er...

Known issues and troubleshooting with SignTool - MSIX | Microsoft Learn

If the issue persists, you might want to ask about this in the MSIX development forum.

Please click Mark as Best Response & Like if my post helped you to solve your issue.
This will help others to find the correct solution easily. It also closes the item.


If the post was useful in other ways, please consider giving it Like.


Kindest regards,


Leon Pavesic
(LinkedIn)

Hi Leon,
I'm using the Win 10 operating system and same SDK version installed which you have mentioned. Also, not all the packages are getting corrupted as they are working as expected with self-signed certificate. Do not know how to fix this issue as tried to connect with DigiCert team but they don't have solution for that yet.