Forum Discussion
MSIX Packaging Tool - Package Analyzer
This cmd will show progress via the log entries of the installation attempt and might provide a clue to the issue. You may also have to manually check the event viewer Microsoft\Windows\AppXPackagingOM logs for additional logging not included in the above.
Thanks for this TIMOTHY_MANGAN, having checked the event viewer over, the last entry in the AppXDeploymentServer\Operational area highlights some information that there some remaining cost associated with the Deployment Add operation on my package that potentially un-accounted for?
I have something similar to the article mentioned here.
https://techcommunity.microsoft.com/t5/msix/what-is-the-quot-gap-quot-and-how-do-i-eliminate-it/m-p/2873569#M2758
Performance summary of Deployment Add operation on Package DemoApp_3.10.0.0_x64__xxxxxxxxxxxxx:
Overall time: 12984 ms
Enqueue cost: 531 ms
Dequeue delay: 78 ms
Bundle processing cost: 0 ms
Indexing cost: 625 ms
Resolve dependency cost: 31 ms
Check approval cost: 47 ms
Evaluation cost: 985 ms
Hardlinking evaluation cost: 31 ms
Gap: 15 ms
Stage required cost: 7203 ms
Flushing and closing files cost: 0 ms
Gap: 157 ms
Machine register cost: 265 ms
Stage user data cost: 78 ms
Gap: 47 ms
Registration cost: 1313 ms
Gap: 78 ms
Repository commit transaction cost: 1047 ms
Gap: 390 ms
Data flush cost: 16 ms
Post DeStage repository commit transaction cost: 0 ms
Remaining cost: 94 ms
- GrahamGBJan 30, 2024Iron ContributorI had to use the Get-AppxLog -all parameter to see the related output, but the information above seemed to be the last time stamped relevant output. Prior to that it appears have finished the Add operation, and I am able to launch the application from the start menu, but I see no way to nudge the "Installing MSIX Package" prompt along along. If I cancel it, i can't resume again, as selecting "Analyze Package" again fails as the application is already installed.
- Jan 30, 2024The performance information you posted looks "normal". The "Gaps" seem to be just times that the performance logging knows were spent (by looking at telemetry timestamps that are recorded) but have no specific information about how it was spent.
You would be looking for warning/error events which would indicate potential issues..- GrahamGBJan 30, 2024Iron Contributor
That's what I expected to find, although there are no errors, and the only warnings appear in AppxPackaging/Operational related to Declared namespaces which are inapplicable, and will be ignored during manifest processing.
I have some earlier errors prior to me starting the analysis related to AppExecutionAlias directory missing, with an an error code 0x8007010B, but appears at points where I had upgraded the MSIX Packaging Tool in the disconnected environment with the latest stable release.- Fiza_AzmiJan 31, 2024
Microsoft
Hi GrahamGB
This does not look like a Package Analyzer issue.
We have replied to this thread - Re: What is the "gap" and how do I eliminate it? - Microsoft Community Hub, suggesting uninstalling the package, then retry the Package Analyzer and see if the issue persists.
Thanks,
Fiza
PM, MSIX