{"id":4214,"date":"2026-05-10T23:16:26","date_gmt":"2026-05-11T03:16:26","guid":{"rendered":"https:\/\/www.tmurgent.com\/TmBlog\/?p=4214"},"modified":"2026-05-10T23:16:26","modified_gmt":"2026-05-11T03:16:26","slug":"announcing-tmeditx-editor-7-2-and-tmeditx-tools","status":"publish","type":"post","link":"https:\/\/www.tmurgent.com\/TmBlog\/?p=4214","title":{"rendered":"Announcing TMEditX Editor 7.2 and TMEditX Tools"},"content":{"rendered":"\n

Today we release version 7.2 of TMEditX Editor and also TMEditX Tools. This post will cover what is new for each.<\/p>\n\n\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\n

The new release contains a number of new features and changes. Importantly, now that we can handle most applications, you’ll notice a bit of focus on some of the other things that customers have asked to be part of their processes.<\/p>\n\n\n\n

Change: Tool Config.<\/strong> While maybe not as important as the features we will cover later, the changes in the tool configuration are the FIRST thing you need to pay attention to. In most releases we add new features and therefore controls over those features that you will want to configure.<\/p>\n\n\n\n

As we have been adding more configurations each release, the UI for controlling this became too crowded. So access to the configuration options editing has moved from a sub-tab of the File tab and promoted to its own tab. Different parts of the configuration are now separated in sub-tabs there, making it easier to find what you want. <\/p>\n\n\n\n

The features below will call out new features that can be controlled by the configuration policy, but here is a video that quickly shows you where the controls have moved to and also mentions a few of them.<\/p>\n\n\n\n

Link to short video about the new options.<\/a><\/strong><\/p>\n\n\n\n

Feature: Create a new blank package.<\/strong> In addition to editing MSIX packages made by the Microsoft MSIX Packaging Tool and other third-party packaging tools, we now introduce the ability to create a package from scratch, without using a recapturing tool.<\/p>\n\n\n\n

Primarily intended to help you create MSIX Modification packages, it can also generate MSIX Framework or Resource packages. The Modification packages can be simple registry or file based configurations\/customizations, or can contain plugins for a packaged app.<\/p>\n\n\n\n\n\n\n\n

We put the basic package together for you, and you just import files and\/or registry items you need. But we have another video to show this.<\/p>\n\n\n\n

Link to short video about the New Package feature..<\/a><\/p>\n\n\n\n

Feature: Added support for uap11:CurrentDirectoryPath.<\/strong> This is one of those missing features of MSIX that we normally solve by using PsfLauncher to fix the current directory for an application. Microsoft added this support a while back, but it only works on Windows 11 and Server 2025. <\/p>\n\n\n\n

While most customers have migrated to Windows 11, most of the RDS servers are still on Server 2022, so everyone can’t use this feature yet.<\/p>\n\n\n\n

Starting with this release, we add support for this setting and default to adding it into the AppXManifest. We still use PsfLauncher to solve the issue today, but once Server 2025 becomes dominant we will be able to remove the use of the Psf from some packages.<\/p>\n\n\n\n

Feature: Two new configuration controls for the PSF.<\/strong> Two new tool configurations, and command line overrides, are added for customers that want to change the way the PSF is configured on a policy or scripted basis. The PSF Features already existed and could be set by hand in the GUI, this just makes them available to automation.<\/p>\n\n\n\n