Forum Discussion
MSIX Packaging Tool Command Line?
Has anyone succesfully used the MSIX Packaging Tool Command Line functionality? I haven't had any luck getting the packaging process to work with a template, and I can't find a single tutorial or post on the internet addressing it (besides the MS docs, which don't have any troubleshooting help).
I see the create-package command has a verbose option, but I don't understand the error. Is there maybe event logs with additional info?
Here's the verbose logging of my error:
Running the installer
About to start process
- File name: %UserProfile%\Downloads\App\App Client Setup.exe
- Arguments: /S /v/qn
Received code 6 for job 2060 with value 13240
Installer still running
Received code 7 for job 2060 with value 13240
Installer still running
Received code 4 for job 2060 with value 0
App Client Setup.exe failed, exit code = -858993460
Restoring the environment
Starting service. ServiceName : WSearch.
Enabled Service : WSearch
The conversion operation failed with: Process App Client Setup.exe failed with exit code -858993460.
Stopping monitoring session
Stopping the Monitoring session
Stopping reboot listener
Not really sure where to start with debugging this! I proved that I was able to run the installer directly from CMD using these same arguments and it installs fine.
6 Replies
I have an updated version of the original Microsoft scripts for using the command line interface on my Github repository here: GitHub - TimMangan/msix-packaging2 This supports mostly remote packaging, but shows the basics of manipulating the template and calling the command line.
Hi Tim, I've been digging into this for a while with no luck unfortunately. It looks like this script is designed for remote packaging, which is super cool! I've been experimenting with both remote (azure VM) and local, each without success. I would think that since I continue to get that error locally, I should focus in on that before trying to get it remote.
I've tried a few different template files with no change in outcome. Any chance you would have a simple template I could try?
The scripts require that you have the MSIX Packaging Tool installed on two machines; the "controller" where you start and end the process, and a remote "packager" that performs the capture. They were written for Hyper-V control of the remote. In an Azure environment you would have to manually control the "revert to snapshot" and "start" functions of the remote (probably adjusting the scripts), and the remote machine would have to have remote powershell enabled ("enable winrm"). And fix any firewall blocking between those two. Probably want both machines in the same area (either local or azure) as communication between them is touchy.
Thanks Tim, I'll take a look at this!
