\n\n![\"\"](\"https:\/\/www.tmurgent.com\/TmBlog\/wp-content\/uploads\/2023\/11\/TMEditX_500x500-150x150.png\")
TMEditX Editor is the licensed and much more capable tool for fixing up MSIX <\/em>packages, better than PsfTooling since it doesn’t have to depend on the Microsoft MSIX Packaging Tool to create the final package.\u00a0 [Download_page]<\/a><\/em>\n\n<\/div>\n\n\n
TMEditX Editor is the licensed and much more capable tool for fixing up MSIX <\/em>packages, better than PsfTooling since it doesn’t have to depend on the Microsoft MSIX Packaging Tool to create the final package.\u00a0 [Download_page]<\/a><\/em>\n\n<\/div>\n\n\nThe TMEditX Editor changes in 6.2 include the following:<\/p>\n
- \n
- PSF v.2025.09.19<\/strong>\u00a0<\/strong>which is covered in blog post New in PSF v.2025.09.19 \u2013 Confessions of a Guru<\/a><\/li>\n
- Add flexibility on whether to fix missing fonts<\/strong>. By customer request, we added a configuration option that will place this fixup in either the Recommended or Available list.\u00a0 Previously, this always went to the Recommended list.\u00a0 Also added a new command line option\u00a0\/AutoSkipFonts<\/strong> as a way to disable automatically fixing this for a single package from the command line.<\/li>\n
- Added flexibility on whether InstalledLocationVirtualization should be used.<\/strong> Also by customer request, a new configuration option in the tool allows you to specify to never add ILV to the package (and if MfrFixup is used to disable the IlvAware mode there also).\u00a0 The customer expressed concern in their environment for binary files to look like they are in the redirection area, which happens automatically with ILV using sparse blocks pointing back to the package installation folder.\u00a0 This apparently was an issue for a security monitoring tool.\u00a0 The security tool could likely be configured to allow this, but that is another group…<\/li>\n
- Support for new PSF Debug Logging.<\/strong> The tool will normally configure the PSF with the PsfDebugLevel of 2, which is the equivalent to what we used to get unless you requested the Debug build of the PSF.\u00a0 This provides logging of the PsfLauncher, PsfFtaCom launcher, and the launching of any child processes in the container. There is a new Available fixup to increase the logging level to 4, which is equivalent to using the Debug binaries of the PSF.\u00a0 Manual editing of this value to other levels is also possible on the Json tab.\u00a0 See \u00a0Wiki page for Config.Json<\/a> for the definition of the levels.<\/li>\n
- COM Changes.<\/strong>\n
- \n
- Added detection and new fixup for COM entries that require VB6 runtime<\/strong>.\u00a0 The fixup will add version 6 of the runtime to the package, which will allow for registration of the COM components that use it.<\/li>\n
- Fix issue where app had a bad CLSID GUID<\/strong>, and made sure other COM Guids like Interface and TypLibs are well formed also.\u00a0 Previously we would add these in the AppXManifest and the package would fail to install.\u00a0 Obviously, the app isn’t using COM objects natively anyway.<\/li>\n
- Added additional checking for all COM CLSID, Interface, and TypeLib entries to ensure that they are valid entries in the registry, not just the GUID but that all required fields are present.\u00a0 There are many installers adding garbage<\/strong> into the Classes area for non-COM purposes.\u00a0 We now detect these and report them in the Unfixed and Informational item list.<\/li>\n
- Fix issue where the App registered an Interface with an incorrectly formed path<\/strong>, as in “\\folder\\name.dll”.\u00a0 If we can find the dll in the package, we just correct the entry and process it now.<\/li>\n
- Fix issue with an app that registered a ProgID for COM using a name that included the _ character<\/strong>.\u00a0 This is not allowed natively per Microsoft documentation but works anyway.\u00a0 In the AppXManifest this is not allowed and resulted in a package that would not save.\u00a0 We now detect this and add it into the “unfixable and informational” item list.\u00a0 Testing so far indicates that in most cases, the ProgID in this form may be used as long as it is in the virtual registry without being in the AppXManifest.<\/li>\n
- Added support for COM registration with\u00a0TreatAs<\/strong> and ProgId properly.<\/li>\n
- Improved diagnostics and support for apps with ActiveX<\/strong> COM components.<\/li>\n<\/ul>\n<\/li>\n
- Added code to emit an exit code when TMEditX closes<\/strong>.\u00a0 This value is for use in automation scenarios and provides an indication of the licensing state of TMEditX, package save state, and signtool\/timestamping state.\u00a0 A return value of zero indicates that the package was successfully updated as requested using an active production license key. The values are bit-encoded as follows (other bits are reserved\/set to zero):\n
\n\n
\n Bit Position<\/td>\n Meaning<\/td>\n<\/tr>\n \n 0<\/td>\n Tool was run using an active trial license key<\/td>\n<\/tr>\n \n 1<\/td>\n Tool was run using an expired trial license key<\/td>\n<\/tr>\n \n 2<\/td>\n Tool was run using an expired production license key.<\/td>\n<\/tr>\n \n 3<\/td>\n Tool has not been licensed<\/td>\n<\/tr>\n \n 4<\/td>\n A failure occurred in saving the package (makemsix or makeappx)<\/td>\n<\/tr>\n \n 8<\/td>\n A failure occurred in signing or timestamping the package<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/li>\n - Updated to use the latest libraries used for generation of CimFS packages for AppAttach.<\/li>\n
- Made performance improvements when analyzing packages with lots of COM.<\/li>\n<\/ul>\n\n\n\n
Where to get the release<\/h3>\n\n\n\n
The latest version of TMEditX Editor is found at the following link. TMEditX has a fully functional trial mode that can be used to verify just how good it is. TMEditX Download<\/a><\/p>\n\n\n\n
TMEditX Tools<\/h2>\n\n\n
- Fix issue where app had a bad CLSID GUID<\/strong>, and made sure other COM Guids like Interface and TypLibs are well formed also.\u00a0 Previously we would add these in the AppXManifest and the package would fail to install.\u00a0 Obviously, the app isn’t using COM objects natively anyway.<\/li>\n
- Add flexibility on whether to fix missing fonts<\/strong>. By customer request, we added a configuration option that will place this fixup in either the Recommended or Available list.\u00a0 Previously, this always went to the Recommended list.\u00a0 Also added a new command line option\u00a0\/AutoSkipFonts<\/strong> as a way to disable automatically fixing this for a single package from the command line.<\/li>\n