confused by file extension(.appx)

%3CLINGO-SUB%20id%3D%22lingo-sub-1528130%22%20slang%3D%22en-US%22%3Econfused%20by%20file%20extension(.appx)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1528130%22%20slang%3D%22en-US%22%3E%3CP%3EI%20used%26nbsp%3B%3CSPAN%3EMakeAppx.exe%20created%20an%20.appx%20file%20from%20my%20win32%20.exe%20file%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fmsix%2Fpackage%2Fcreate-app-package-with-makeappx-tool%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fmsix%2Fpackage%2Fcreate-app-package-with-makeappx-tool%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%2200000.png%22%20style%3D%22width%3A%20643px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F205954i7F3C4F36E9711183%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%2200000.png%22%20alt%3D%2200000.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3Eafter%26nbsp%3B%3C%2FP%3E%3CP%3ECreate%20a%20certificate%20for%20package%20signing%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fmsix%2Fpackage%2Fcreate-certificate-package-signing%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fmsix%2Fpackage%2Fcreate-certificate-package-signing%3C%2FA%3E%3C%2FP%3E%3CP%3Eand%3C%2FP%3E%3CP%3ESign%20an%20app%20package%20using%20SignTool%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fmsix%2Fpackage%2Fsign-app-package-using-signtool%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fmsix%2Fpackage%2Fsign-app-package-using-signtool%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20try%20to%20use%20MSIX%20Packing%20Tool%20and%20convert%20the%20.appx%20to%20msix%20format%20that%20suitable%20for%20Win10%20store.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22111111.png%22%20style%3D%22width%3A%20787px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F205955iA2705FDAE5470EB9%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22111111.png%22%20alt%3D%22111111.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ebut%20it%20said%20'file%20provided%20is%20not%20valid'.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eyour%20comment%20welcome%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1528963%22%20slang%3D%22en-US%22%3ERe%3A%20confused%20by%20file%20extension(.appx)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1528963%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F731336%22%20target%3D%22_blank%22%3E%40aloha999%3C%2FA%3E%26nbsp%3B%20The%20Microsoft%20MSIX%20Packaging%20Tool%20is%20designed%20to%20do%20one%20of%20two%20things%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ECreate%20a%20MSIX%20package%20using%20a%20traditional%20installer%20file%20(msi%20or%20exe%20for%20example)%20through%20recapturing%20the%20installation.%3C%2FLI%3E%0A%3CLI%3EConvert%20an%20existing%20Microsoft%20App-V%20package%20to%20MSIX%20form.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYou%20can%20use%20developer%20methods%20to%20create%20an%20MSIX%20installer%20package%20from%20the%20Win32%20executable%20components%20OR%20you%20can%20use%20this%20tool%20to%20recapture%20the%20traditional%20installer.%20You%20seem%20to%20be%20trying%20to%20combine%20both%20methods.%26nbsp%3B%20If%20the%20cause%20is%20that%20you%20did%20everything%20necessary%20but%20ended%20up%20with%20a%20file%20with%20.appx%20file%20extension%2C%20this%20is%20possibly%20OK%20(some%20early%20vendor%20tools%20didn't%20use%20the%20msix%20file%20association).%26nbsp%3B%20The%20Store%20accepts%20both%20.appx%20and%20.msix%20file%20extensions%2C%20what%20makes%20the%20package%20%22MSIX%22%20is%20in%20the%20contents%20of%20the%20internal%20AppXManifest%20file.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1533733%22%20slang%3D%22en-US%22%3ERe%3A%20confused%20by%20file%20extension(.appx)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1533733%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F731336%22%20target%3D%22_blank%22%3E%40aloha999%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3BWhat%20did%20you%20put%20inside%20the%20.appx%20package%20created%20with%20MakeAppx%3F%20If%20you%20put%20there%20the%20executable%20to%20launch%20your%20application%2C%20all%20its%20dependencies%20and%20an%20AppxManifest%20with%20the%20appropriate%20entries%2C%20then%20your%20package%20is%20as%20good%20as%20an%20.msix%20and%20you%20don't%20even%20need%20to%20use%20the%20MSIX%20Packaging%20Tool.%20You%20could%20submit%20it%20to%20the%20Store%20directly%20as%20Timothy%20said.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20you%20tried%20to%20put%20the%20installer%20executable%20in%20the%20.appx%20package%20and%20then%20convert%20it%20with%20the%20MSIX%20Packaging%20Tool%2C%20that%20will%20not%20work.%20In%20that%20case%20what%20you%20would%20do%20instead%20is%20convert%20the%20installer%20directly%20with%20the%20tool%2C%20i.e.%20put%20the%20.exe%20where%20you%20were%20using%20the%20.appx%20in%20the%20packaging%20tool.%20You%20could%20also%20use%20the%20packaging%20tool%20to%20sign%20your%20package%20when%20it%20is%20created%20in%20a%20single%20step%2C%20instead%20of%20calling%20signtool%20separately.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Frequent Visitor

I used MakeAppx.exe created an .appx file from my win32 .exe file

https://docs.microsoft.com/en-us/windows/msix/package/create-app-package-with-makeappx-tool

 

 

00000.png

after 

Create a certificate for package signing

https://docs.microsoft.com/en-us/windows/msix/package/create-certificate-package-signing

and

Sign an app package using SignTool

https://docs.microsoft.com/en-us/windows/msix/package/sign-app-package-using-signtool

 

I try to use MSIX Packing Tool and convert the .appx to msix format that suitable for Win10 store.

 

111111.png

 

but it said 'file provided is not valid'.

 

your comment welcome

2 Replies

@aloha999  The Microsoft MSIX Packaging Tool is designed to do one of two things:

  • Create a MSIX package using a traditional installer file (msi or exe for example) through recapturing the installation.
  • Convert an existing Microsoft App-V package to MSIX form.

 

You can use developer methods to create an MSIX installer package from the Win32 executable components OR you can use this tool to recapture the traditional installer. You seem to be trying to combine both methods.  If the cause is that you did everything necessary but ended up with a file with .appx file extension, this is possibly OK (some early vendor tools didn't use the msix file association).  The Store accepts both .appx and .msix file extensions, what makes the package "MSIX" is in the contents of the internal AppXManifest file.

 

 

 

 

@aloha999

 

 What did you put inside the .appx package created with MakeAppx? If you put there the executable to launch your application, all its dependencies and an AppxManifest with the appropriate entries, then your package is as good as an .msix and you don't even need to use the MSIX Packaging Tool. You could submit it to the Store directly as Timothy said.

 

If you tried to put the installer executable in the .appx package and then convert it with the MSIX Packaging Tool, that will not work. In that case what you would do instead is convert the installer directly with the tool, i.e. put the .exe where you were using the .appx in the packaging tool. You could also use the packaging tool to sign your package when it is created in a single step, instead of calling signtool separately.