{"id":4173,"date":"2026-02-23T14:05:45","date_gmt":"2026-02-23T19:05:45","guid":{"rendered":"https:\/\/www.tmurgent.com\/TmBlog\/?p=4173"},"modified":"2026-02-23T14:05:45","modified_gmt":"2026-02-23T19:05:45","slug":"new-in-tmeditx-editor-and-tools-7-1","status":"publish","type":"post","link":"https:\/\/www.tmurgent.com\/TmBlog\/?p=4173","title":{"rendered":"New in TMEditX Editor and Tools 7.1"},"content":{"rendered":"\n

Version 7.1 of the TMEditX Editor<\/strong> and the TMEditX Tools<\/strong> are both released today.  This is a feature release, and the post covers both releases.<\/p>\n\n\n\n

TMEditX Editor 7.1<\/h2>\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

\u00a0<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Type<\/strong><\/td>\nDescription<\/strong><\/td>\n<\/tr>\n
PSF<\/strong><\/td>\n\n

Updated to Psf v2026.02.22<\/p>\n

See blog post: Psf v2026.02.22 \u2013 Confessions of a Guru<\/a><\/p>\n<\/td>\n<\/tr>\n

Feature<\/strong><\/td>\n\n

MSIX Bundles.<\/strong><\/p>\n

Support to open an msixbundle file, including those with a .msix extension.<\/p>\n

We are not attempting to allow you to edit the file so much as recognize the format, show you the files and the contents of BundleAppXManifest.xml file.\u00a0 Also added, is the ability to double-click on one of the embedded MSIX files to open that for edit.<\/p>\n<\/td>\n<\/tr>\n

Feature<\/td>\n\n

Alternate Code Pages.<\/strong><\/p>\n

Added detection of apps that use alternative CodePage encoding in their WInPE format.\u00a0 Also added a new Recommended fixup to add the Uap8:ActiveCodePage parameter to the AppXManifest file.<\/p>\n

This is very important for apps that spawn off child apps and communicate over the Console port (stdin\/stdout). These are mostly cross-platform apps build for Linux originally.<\/p>\n

The official documentation from Microsoft for the Uap7:Properties element does not list this new element as an option, and the parameter is also missing from documentation.\u00a0 The Uap7 schema does not mention this new parameter, but it is defined in the Uap8 schema file.\u00a0 We tried adding this to a package and it solved the problem.<\/p>\n

So we added the detection and fixup to the editor, and filed a documentation bug with Microsoft.<\/p>\n<\/td>\n<\/tr>\n

Features<\/td>\n\n

Support for things only seen in Vendor supplied packages.<\/strong><\/p>\n

The following features and changes were made to support packages released in MSIX form from developers.\u00a0 IT will still want to vet and change many\/most of these packages before deploying. In many cases, these packages include things we never see in captured packages.<\/p>\n

    \n
  • The bundle feature mentioned above.\u00a0 You may not want to deploy the bundle, but just the embedded msix file for your architecture, plus possibly a resource or dependency framework package.\u00a0 Because we identify these, you can copy them from the temporary unpack folder.<\/li>\n
  • Added support for ContentType attribute of the FileTypeAssociation element.\u00a0 While not really important to be in the package, we want to preserve the fidelity of what the developer asked for, so have added this support.<\/li>\n
  • Added support for ToastActivatorCLIS for desktop toast notifications in the AppXManifest.\u00a0 Captured installers use a different element.<\/li>\n
  • Added support for some original foundational package level extensions that we assumed has been obsoleted by the COM extension family.\u00a0 This also helps to close the gap on the last (hopefully) missing COM functionality for captured packages – managed in-process x86 COM.<\/li>\n
  • Added uap:ApplictionContentUriRules support to the AppXManifest.<\/li>\n
  • Added support for DeviceCapabilities in the AppXManifest.<\/li>\n
  • Added support for the undocumented schema “getTemplate” seen in several vendor AppXManifest files.\u00a0 These are like the build schema extensions that are not part of MSIX but show up as documentation of the tooling used.\u00a0 We now process these and keep them in the package.<\/li>\n
  • Fixed support for packages declaring “windows.AppExtension” extensions to an application.\u00a0 We never see these in recaptured apps and had an error in our processing of these.<\/li>\n
  • Fixed support for Desktop3:CloudFiles regarding the requirement for IconResource.\u00a0 We think only OneDrive uses this.<\/li>\n
  • Fixed support for Framework and Resource type packages.<\/li>\n
  • Fixed the regex parsing for Uap5:Host to use the ECMA flavor of regex for pattern matching when validating a file.<\/li>\n
  • Fixed support for Uap5:IdentityType in OutOfProcessServer.<\/li>\n
  • Fixed support for the rarely used Uap:EditFlags parameter in FileTypeAssociations.<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
Feature<\/td>\n\n

Newer VCRuntime versions.<\/strong><\/p>\n

Added a detection and warning in the “Unfixable and Informational” area for a package that has a newer version of VCRuntime files than that of the PSF.\u00a0 This should only come up if your version of TMEditX is not up to date.\u00a0 If detected, the package may or may not work correctly.<\/p>\n<\/td>\n<\/tr>\n

Feature<\/td>\n\n

Firewall Rules.<\/strong><\/p>\n

Added a new configuration and three detections associated with Windows Firewall Rules added by application installers.\u00a0 See our research paper for a lot of detail about all of this:<\/p>\n

https:\/\/tmurgent.com\/appv\/en\/resources\/white-paperlist\/658-windows-firewall-msix<\/a><\/p>\n

Via configuration, you may opt in to detecting missing firewall rules and adding them into the AppXManifest, or opt-out to remove any present.<\/p>\n

The detections will either add a Recommended Fixup to add or remove these rules, or an Informational one for the add scenario if there are any that cannot be automatically handled.<\/p>\n

There are some rules that cannot be automatically added; these will appear in the “unfixable and Informational” list. Typically, these are wildcard rules and we can’t add them to the AppXManifest as is. You can manually add these to the AppXManifest once you determine which exe they should apply to.<\/p>\n

Command line parameters for overrides to the tool configuration were also added for this feature.\u00a0 They are \/AutoAddFirewallRules and \/AutoRemoveFirewallRules.<\/p>\n

You may need the new cmdlets in PassiveInstall 3.0 to get the MMPT to capture firewall rules laid down by the vendor installer as part of your installation wrapper script.\u00a0 Again, see that blog post for details.<\/p>\n<\/td>\n<\/tr>\n

Feature<\/td>\n\n

Update While In Use.<\/strong><\/p>\n

Added a new optional fixup to add the Uap17:UpdateWhileInUse property to the package.<\/p>\n

This property does not seem to actually work at this time, and we have asked Microsoft to investigate.\u00a0 But it does no harm to add it!<\/p>\n

It is supposed to solve an issue for the scenario where this package tries to update an installed package of different version and that package is in use.\u00a0 The intent of this feature is to allow the request to be placed in a deferred queue to be completed later, rather than what happens today.<\/p>\n

What happens today depends on how the install was requested.\u00a0 From the AppInstaller GUI, it would kill the running process without warning and install.\u00a0 From other methods, it will fail.<\/p>\n

We like this feature and hope Microsoft will fix it.<\/p>\n<\/td>\n<\/tr>\n

Feature<\/td>\n\n

Improvements to shortcut detection and processing.<\/strong><\/p>\n

Added support for installers that drop .website files to the start menu or desktop, rather than .url and .lnk files.<\/p>\n

Also added support for installers that drop .lnk files that just point to a .url or .website file elsewhere in the package to get to a webpage.<\/p>\n

Also added support for an installer that just drops the http\/s reference\u00a0 as the target of a .lnk file.\u00a0 This one (only) uses the Uap:StartPage element and avoids the need for the PSF.<\/p>\n

Also added support for advertised shortcuts that have a url as the target.<\/p>\n

Also added support for a situation where the package has two shortcuts that used the same named exe file as the target, but using two different filepaths.\u00a0 This was treated as a duplication previously and has now been fixed.<\/p>\n<\/td>\n<\/tr>\n

Change<\/td>\n\n

.Net Runtime Detection.<\/strong><\/p>\n

Improvements to detection of .Net Runtime dependencies for components in the package.<\/p>\n

These appear in the “Unfixed and Informational” list.\u00a0<\/p>\n

Note that when a detection for .Net runtime of 5 or more appears, that or any newer version should be OK.<\/p>\n<\/td>\n<\/tr>\n

Change<\/td>\n\n

Minimum Package Version<\/strong><\/p>\n

In the previous release, we added a configuration feature that would prevent the tool from updating the Minimum OS version of the package.\u00a0<\/p>\n

Normally, the tool updates this field if it adds a feature that only works on that OS or above.\u00a0 Some schema extensions require this field be increased or the feature will be ignored even if on an OS that support it.\u00a0 But updating this field means you can’t install the package on older OSs. So, we added this feature in to avoid the problem.<\/p>\n

Unfortunately, not all schema elements are silently ignored (even if we request it) and including one of those elements in the AppXManifest without increasing the Minimum OS makes it impossible to install the package on back-rev OSs like Server 2022 (and Windows 10).<\/p>\n

Now, if such identified elements are part of the package, we will update the minimum OS version, so that the feature works in all situations where it can work.\u00a0 This is probably better for those down-rev systems as the issue is now detected at package installation time and not at user runtime.\u00a0 The package analysis log also tells you about the change so you can track it at packaging time.<\/p>\n<\/td>\n<\/tr>\n

Fix<\/td>\n\n

Updated VCRuntimes added with the PSF to the now latest version.<\/strong><\/p>\n

The PSF requires VCRuntime redistributables, and TMEditX supplies these to the package when requested.\u00a0 We try to keep the version needed by the PSF in line with the latest version released by Microsoft, so that these will be at or greater than what an application might require.<\/p>\n

We have updated the redistributables in this release to the currently latest version available from Microsoft, 14.50.<\/p>\n<\/td>\n<\/tr>\n

Fix<\/td>\n\n

\u00a0ILV Option<\/strong><\/p>\n

In the previous release we added a new option to opt-out of using InstalledLocationVirtualization. We had a bug and it only took affect if included using the cmdline option.<\/p>\n

This is fixed.\u00a0 Sorry!<\/p>\n<\/td>\n<\/tr>\n

Fix<\/td>\n\n

Are you Sure?<\/strong><\/p>\n

In the previous release we added a new option to ask an “are you sure” like question if the package currently under edit has not been saved if the user attempts to close the window or open a new package.\u00a0 The cancel button did not work.<\/p>\n

We fixed that.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

\u00a0<\/p>\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 7.1<\/h2>\n\n\n\n

\"\"TMEditX Tools is the free tools for packagers wanting to quickly test and debug their MSIX packages.\u00a0 It contains two apps.\u00a0 MSIXDeploy<\/strong> is used to install, uninstall, and debug MSIX and AppAttach packages from your file share without the need of a server.\u00a0ParsePsfDebugLog<\/strong> is a tool for organizing and formatting the debug log output produced when you use the PSF (especially the Debug Psf).<\/span><\/p>\n\n\n\n

MSixDeploy:<\/p>\n