TMEditX is the licensed and so much more capable tool for fixing up MSIX packages; better than PsfTooling since it doesn’t have to depend on the Microsoft MSIX Packaging Tool to create the final package. [Download_page]
Features and Fixes
- PSF v2024.10.26 added to this version. See What’s new in PSF v2024.10.26? – Confessions of a Guru for details.
- Feature: Support for Control Panel Applets and associated COM Servers.
- The traditional registration of these are ignored by the Microsoft MSIX Packaging Tool.
- By default, when detected these are placed as Available fixups and are not automated.
- Using a new configuration option in TMEditX you can set these to be Recommended fixes when detected. Alternatively, a new Command Line Option was added /AutoFixControlPanelApplets also.
- This feature was requested to allow end-users to manage Java certificates.
- Feature: Add support for a new PSF feature to be able to disable a user from running multiple instances of an applications simultaneously in their user session.
- It is performed by both PsfLauncher and PsfFtaCom.
- Due to rare usage, it is not automatable but must be applied to the package manually.
- This can be done via a checkbox on PsfLauncher in the Psf Editor dialog.
- There is also an Available fixup for this.
- When applied, is applies to all applications within the package. Manual editing of the config.Json file can limit which applications is applies to.
- Feature: Added back the ability to run scripts either outside or inside the container.
- We lost this ability when Microsoft made an OS change several years back.
- This appears as a checkbox in the PsfEditor in the scripts areas.
- Feature: Added a detection that a new version of TMEditX is available. This is detection only, not an automated update.
- Requires internet access.
- A new sub-tab will appear in the File Menu (where you set options, open and save files, and request conversions to AppAttach) when a new version has been released.
- The page will display the current and new version and provide either links or instructions on getting the new version.
- Feature: A new command line option /AnalyzeOnly was added. The purpose of this is to allow the creation of an XML analysis report file without fixing up the package.
- It is the same analysis report file that would be saved in the package.
- Other command line options are not supported.
- After the /AnalyzeOnly switch, the path to an xml file must follow. The typical command line looks like:
TMEditX.exe /AnalyzeOnly PathToXmlOutputFile PathToMsixInputFile
- Change: When PsfLauncher files are added to the package, the package name will be prepended to the filename.
- This is a customer requested change to make it easier to identify the package from tools that monitor and report or try to control (i.e. security tools) processes.
- PsfFtaCom already did this.
- Change: Changed the package extraction software. Although the progress bar display of the unpacking is lost, the new technique can lead to a 50% reduction in the time to unpack the package.
- Fix: Don’t default to add a timestamp server when not specified. This is needed for air-gapped systems at some customers.
- Fix: Fixed a but in the PsfEditor scripts UI where the end-script browse button would update the start-script file.
- Fix: When IsFrameworkPackage is set in the Properties tab, the value in the AppXManifest must be all lower case.
Where to get TMEditX
The latest version of TMEditX is found at the following link. TMEditX has a fully functional trial mode that can be used to verify just how good it is.
