The TMEditX Editor operates as follows:
Analysis
When opening the package, the package is unpacked into a temporary folder in the user's %temp% folder. Then the package analyzer is run. It is also re-run after many of the fixups are applied, as fixing certain issues may alter the list of what additional fixes are recommended.
This analysis compares the state of three things, along with the governing policies set in the tool configuration (possibly overridden by command line parameters):
- Evidence of what the native application installer intended in the way of integrations.
- The current state of the AppXManifest file and integrations defined there.
- The capabilities of the fuller AppXManifest schema.
A long series of potential improvements to the package are then developed, based on our years of experience in making MSIX packages better. Over 100 scenarios are considered. Based on policy, these are ordered up into lists of things that should or could be done.
The analysis is then displayed on the Analysis tab of the software, as an ordered list that would be performed from top to bottom, grouped into sections.
- Pre-Psf: Things that need to be done prior to consideration of adding the PSF. This includes transforming the package from a form created by a third-party source into the form that the Microsoft MSIX Packaging Tool would have used, filtering out unwanted file and registry entries, and defeating things like Squirrel updaters.
- PSF: Whether the PSF is needed, what components are needed are shown. The PSF may be added and configured here.
- Recommended Fixes: Specific fixes that we recommend.
- Optional Fixes: This will include items that would have been recommended, except that configuration turned them off. It also includes some standard things that are possible but not routinely performed on packages.
- Informational and Unfixed: This area shows a number of things that we detected but could not fix at this time, as well as other information about the software in this package that you should be aware of.
Applying Fixes
There is a button at the top to apply default fixes. This will be any Pre-PSF, PSF, and Recommended fixes. These are performed from the top down as you see them on the display. For many of the fixes, after applying a fix there will be a reanalysis and you may see the list on the screen change, possibly removing or adding items to the list. For example, when we perform file cleanup, the PSF might no longer be needed.
If you want to be more selective, you can choose to manually apply the fixes instead. If you do, you should work from the top down.
Manual Editing
You can also use the other tabs at the top of the tool to access editors for different parts of the package. Note that the config.json and AppXManifest editor pages have their own apply buttons that you must click so that your edits are validated for syntax.
Save off your Package
When you are ready, save off your package. If configured, the saved package will also be signed, and if AppLocker/Windows Defender Application Control policy files were configured those will be generated too.