[I was using the 1.2023.1005 release of MSIX Packaging Tool after the October and November announcements and trying to experiment with the new Package Analyzer capabilities with a packaged MSIX through the Package Editor options.
However, when I initiate the Analyze Package option from the Package Editor, it moves through creating the temporary MSIX package, which I can see is created in %Appdata%/Local/Temp/MsixPackagingTool/DiagOutDir/Logs_number\ along with a number of other files including a config.json & other manifest files.
However once it moves the progress to Install MSIX Package it seems to stall. The log file in the same temporary folder location, denotes the last entries show that it successfully signed the .MSIX package without warnings or errors, however there is no further information listed showing it is doing something.
I am carrying this analysis out in a HyperV virtual machine and have tried increasing the assigned memory from 2048mb to 4096mb and it isn't trying to use all that much of that.
In the absence of an up to date HyperV Quick Create iso image with an up to date MSIX Packaging Tool configured with this update, I have configured this in a disconnected environment.
I have since seen the recent updates including some bug fixes with version 1.2023.1212.0 and initially having installed this update, one of the MSIX packages I was trying to analyse passed through all the expected steps and return no fixup recommendations. However checking other packages has resulted in the same progress bar stuck at Installing MSIX Package and after reverting the snapshots and trying with the same successful package it has hit similar issues.
Clearing the temporary files in the Settings area, doesn't appear to have helped either.
Are there any checks I need to make in terms of configuration to make this more reliable?]
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
ID: 844128aa-2a99-d816-b498-5c4d93e8084f
Version Independent ID: 844128aa-2a99-d816-b498-5c4d93e8084f
[I was using the 1.2023.1005 release of MSIX Packaging Tool after the October and November announcements and trying to experiment with the new Package Analyzer capabilities with a packaged MSIX through the Package Editor options.
However, when I initiate the Analyze Package option from the Package Editor, it moves through creating the temporary MSIX package, which I can see is created in %Appdata%/Local/Temp/MsixPackagingTool/DiagOutDir/Logs_number\ along with a number of other files including a config.json & other manifest files.
However once it moves the progress to Install MSIX Package it seems to stall. The log file in the same temporary folder location, denotes the last entries show that it successfully signed the .MSIX package without warnings or errors, however there is no further information listed showing it is doing something.
I am carrying this analysis out in a HyperV virtual machine and have tried increasing the assigned memory from 2048mb to 4096mb and it isn't trying to use all that much of that.
In the absence of an up to date HyperV Quick Create iso image with an up to date MSIX Packaging Tool configured with this update, I have configured this in a disconnected environment.
I have since seen the recent updates including some bug fixes with version 1.2023.1212.0 and initially having installed this update, one of the MSIX packages I was trying to analyse passed through all the expected steps and return no fixup recommendations. However checking other packages has resulted in the same progress bar stuck at Installing MSIX Package and after reverting the snapshots and trying with the same successful package it has hit similar issues.
Clearing the temporary files in the Settings area, doesn't appear to have helped either.
Are there any checks I need to make in terms of configuration to make this more reliable?]
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.