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]
Version 5.6 of TMEditX is released.
Description
This release includes important updates from the Package Support Framework (PSF), improved support for apps with COM and other things, and we have fixed the issue in MsixDeploy on Windows 11 24H2.
Details
The release includes the following:
- PSF: Updated to include version 2025.02. 22. See this blog post PSF V2025.02.22 What’s New? – Confessions of a Guru for details on what has changed.
- COM: Added detection and fixup support for COM Interfaces that use a Forward redirection key in their registry registration. This type of registration is no longer in the Microsoft documentation for COM, but must have been at one point as we have seen it in applications from two different vendors.
- COM: Added detection and fixup support for a scenario where a COM CLSID is registered without a typelib but with a ProgId that is used for another CLSID. A new form of Anti-Disregardation is used to solve the conflict in the AppXManifest.
- Protocol: Added detection and fixup support for Protocol Handlers that are dlls instead of exes. This required a different placement in the AppXManifest.
- Opening Packages: Added a backup method to be used to open unusual packages. The first choice is to use our current unpackager , an OS utility which we believe is necessary for packages that have long paths and/or international characters. If opening fails with this API for any reason, we will now try to open up the package using a different method; the same Microsoft utility as is used by the Microsoft MSIX Packaging Tool. For more interesting information we uncovered regarding long paths and the Microsoft MSIX Packaging Tool, see this blog post: https://www.tmurgent.com/TmBlog/?p-3987
- Shortcuts with arguments with wildcards: Fix to the code to add the PSF in order to support shortcuts with arguments like “%*”.
- Shortcuts with working directories with Environment Variables: Fix to the code to add the PSF in order to support shortcuts with working directories that include environment variables like %USERPROFILE%.
- Shortcuts with working directories with other “special” directories: Fix to the code to add the PSD in order to handle shortcuts that want the working directory to be certain special directories.
- COM: A fix to the analysis of COM registrations to use fully case independent comparisons. There were a few placed where case-sensitive comparisons were being used.
- WebView2/Dependencies: A change in how we fixup an application requiring WebView2. Although the app does require the dependency, we are marking the dependency as optional in the AppXManifest due to deployment issues at customers. Similarly, other dependencies we add will be optional for now.
- PSF Dependent VCRuntimes: Changes to the vcruntimes and msvcr dependencies added to the package when certain PSF components are applied.
- DisplayNames: Fix for when adding certain missing components to the AppXManifest, we need to scrub the value in the registry of leading or trailing spaces.
- LoaderSearchOrder: Moved the general case use of adding LSO for folders with dlls from the Recommended list to the Available list. This was added in the last release, and while the general case use can help some apps, it also can hurt others. Also made changes to the Path variable case to limit it to folders in the package, which remains in the recommended list along with the App Paths case.
- PsfFtaCom: Don’t add PsfFtaCom if there is only one application posted to the start menu. Previously a package with a service could also trigger this to be added.
- ExecutionAlias: Added new recommended fixup to add application alias entries to executables that do not have shortcuts.
- Package MinOSVersion: Added a new option in the TMEditX configuration. When enabled, TMEditX will not automatically update the MinOSVersion when adding AppXManifest extensions that require it to be set to get the functionality.
- Applications Tab: In TMEditX, made a small UI change needed on the Applications Tab.
- Package Signing: Added an option in TMEditX configuration to show a separate window when signing the package. This is useful for debugging when adding cloud based signing and custom signing.
- Long Paths: When the package is opened, we now display the longest path of any file in the package. As discussed in https://www.tmurgent.com/TmBlog/?p-3987 the Microsoft Msix Packaging Tool may have dropped files and folders without obvious notice if they would exceed the 255 limit.
- Save Notifications: Added an obvious indication on the tool Options, Json Editor, and AppXManifest Editor pages when it is necessary to click a save button.
- 24H2: Solved the issue in MsixDeploy on Windows 11 24H2 that prevented the currently deployed packages to be displayed.
Where to get the release
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.
