{"id":4042,"date":"2025-07-05T08:28:21","date_gmt":"2025-07-05T12:28:21","guid":{"rendered":"https:\/\/www.tmurgent.com\/TmBlog\/?p=4042"},"modified":"2025-07-05T09:00:27","modified_gmt":"2025-07-05T13:00:27","slug":"announcing-tmeditx-6-0-new-free-community-tools","status":"publish","type":"post","link":"https:\/\/www.tmurgent.com\/TmBlog\/?p=4042","title":{"rendered":"Announcing TMEditX Editor 6.0;  also New FREE Community Tools"},"content":{"rendered":"<div style=\"width: 600px;\">\n\n<em><img loading=\"lazy\" decoding=\"async\" class=\"alignleft wp-image-3652 size-thumbnail\" src=\"https:\/\/www.tmurgent.com\/TmBlog\/wp-content\/uploads\/2023\/11\/TMEditX_500x500-150x150.png\" alt=\"\" width=\"150\" height=\"150\" srcset=\"https:\/\/www.tmurgent.com\/TmBlog\/wp-content\/uploads\/2023\/11\/TMEditX_500x500-150x150.png 150w, https:\/\/www.tmurgent.com\/TmBlog\/wp-content\/uploads\/2023\/11\/TMEditX_500x500-300x300.png 300w, https:\/\/www.tmurgent.com\/TmBlog\/wp-content\/uploads\/2023\/11\/TMEditX_500x500.png 600w\" sizes=\"auto, (max-width: 150px) 100vw, 150px\" \/>TMEditX Editor is the licensed and much more capable tool for fixing up MSIX <\/em><em>packages, better than PsfTooling since it doesn&#8217;t have to depend on the Microsoft MSIX Packaging Tool to create the final package.\u00a0 <a href=\"https:\/\/www.tmurgent.com\/appv\/en\/buy\/tmeditx\/tmeditx-download\" target=\"_blank\" rel=\"noreferrer  noopener\">[Download_page]<\/a><\/em>\n\n<\/div>\n\n\n<p>\u00a0<\/p>\n<h3>Introduction<\/h3>\n<p>A major release for TMEditX, version 6.0.0.0 has been released, and along with it a separate release of new Community Tooling for working with MSIX.<\/p>\n<ul>\n<li><strong>TMEditX Editor<\/strong> will continue to be a licensed commercial editor and fixer for MSIX packages.<\/li>\n<li><strong>TMEditX Tools<\/strong> is an MSIX package containing free community tools that aid in the testing and debugging of MSIX packages.<\/li>\n<\/ul>\n<p>The tools included in TMEditX Tools were previously known as part of the TMEditX licensed product.\u00a0 The separation of these tools from the overall package allows us to make this tooling free to the community to use and will allow for some develop independent of the Editor product release schedule.<\/p>\n<p>Information on these two releases is given below.<\/p>\n<p>\u00a0<\/p>\n<h3>TMEditX Tools<img loading=\"lazy\" decoding=\"async\" class=\"alignright size-thumbnail wp-image-4046\" src=\"https:\/\/www.tmurgent.com\/TmBlog\/wp-content\/uploads\/2025\/07\/TMEditX_Tools--150x150.png\" alt=\"\" width=\"150\" height=\"150\" srcset=\"https:\/\/www.tmurgent.com\/TmBlog\/wp-content\/uploads\/2025\/07\/TMEditX_Tools--150x150.png 150w, https:\/\/www.tmurgent.com\/TmBlog\/wp-content\/uploads\/2025\/07\/TMEditX_Tools--300x300.png 300w, https:\/\/www.tmurgent.com\/TmBlog\/wp-content\/uploads\/2025\/07\/TMEditX_Tools--768x768.png 768w, https:\/\/www.tmurgent.com\/TmBlog\/wp-content\/uploads\/2025\/07\/TMEditX_Tools-.png 1024w\" sizes=\"auto, (max-width: 150px) 100vw, 150px\" \/><\/h3>\n<p>So, what is in TMEditX Tools?\u00a0 TMEditX Tools is our free Community Tooling.\u00a0 Anyone can use it free of charge and without restrictions on installation and use.\u00a0 Today, it consists of two programs.<\/p>\n<p><strong>MsixDeploy<\/strong>.\u00a0 This tool is typically used by the packager on their test system to test and debug their new MSIX and AppAttach packages.\u00a0 All without having to use a server or Azure console.\u00a0 For users of our popular community tools for Microsoft App-V, it is equivalent to AppV_Manage, but for MSIX.\u00a0 For a short introduction on MsixDeploy, click <a href=\"https:\/\/www.tmurgent.com\/AppV\/Tools\/TMEditXTools\/MsixDeploy.mp4\" target=\"_blank\" rel=\"noopener\">Short Video on using MsixDeploy<\/a><\/p>\n<p>MsixDeploy provides the following features:<\/p>\n<ul>\n<li>A glance view of packages with extracted information such as what PSF components, and major package extensions, are contained.<\/li>\n<li>Right single-click installation\/uninstallation of any MSIX or AppAttach formatted package, including Vhd\/Vhdx\/Cim.<\/li>\n<li>Right click access to an installed package to view the installation folder or user redirection folder in explorer.<\/li>\n<li>Right click access to view files in the package like the AppXManifest or Config.json files.<\/li>\n<li>Right click access to launch processes inside the target container.<\/li>\n<li>Creation\/Installation\/Uninstallation of Shared Package Containers.<\/li>\n<li>Advanced debugging techniques like live PSF changes without repackaging.<\/li>\n<li>Easy enable\/disable for capturing full process dumps of applications that crash.<\/li>\n<\/ul>\n<p><strong>ParsePsfDebugLog.<\/strong> Newly revamped for this release, this tool is used to quickly parse through the output of a run of an application that has been packaged into MSIX using the debug build of the PSF.\u00a0 The new release is much faster to use and is now organized to help you find the events that are causing the issue you want to diagnose, while making all of the gory detail available on demand.<\/p>\n<p>TMEditX Tools is available for download from our website.\u00a0 It is free to use for anyone.\u00a0 Download page:\u00a0 <a href=\"https:\/\/tmurgent.com\/appv\/en\/resources\/tools-downloads\/msix-tools\/128-msix-tools\/652-tmeditx-tools-install\">TMEditX Tools Download<\/a><\/p>\n<p>\u00a0<\/p>\n<h3>TMEditX Editor<img loading=\"lazy\" decoding=\"async\" class=\"alignright size-thumbnail wp-image-3652\" src=\"https:\/\/www.tmurgent.com\/TmBlog\/wp-content\/uploads\/2023\/11\/TMEditX_500x500-150x150.png\" alt=\"\" width=\"150\" height=\"150\" srcset=\"https:\/\/www.tmurgent.com\/TmBlog\/wp-content\/uploads\/2023\/11\/TMEditX_500x500-150x150.png 150w, https:\/\/www.tmurgent.com\/TmBlog\/wp-content\/uploads\/2023\/11\/TMEditX_500x500-300x300.png 300w, https:\/\/www.tmurgent.com\/TmBlog\/wp-content\/uploads\/2023\/11\/TMEditX_500x500.png 600w\" sizes=\"auto, (max-width: 150px) 100vw, 150px\" \/><\/h3>\n<p>The editor is by now already familiar to most readers.\u00a0 So, I won&#8217;t describe what the editor is, but only what has changed from our last release.<\/p>\n<p>Version 6.0 is a major release due to the many changes to the tool.<\/p>\n<ul>\n<li><strong>Licensing<\/strong>. The terms of the licensing, licensed on a per-user (aka packager) basis, do not change.\u00a0<\/li>\n<\/ul>\n<p style=\"indent: 80px;\">The mechanisms use to implement licensing do change, however. The new mechanism will be a file-based license that is ingested info the product, rather than a GUID.\u00a0 This will allow us to finally support offline activation of the product, a constant request from a portion of our customers.<\/p>\n<p style=\"indent: 80px;\">The new mechanism also solves an issue with the old system that made trial versions unwieldy.\u00a0 People will still be able to download the package from our website and try it out without contacting us as before, including the random chance that it might or might not add the PSF at times.\u00a0 But new customers may request a trial license file to fully unlock the product for a period of time.<\/p>\n<p style=\"indent: 80px;\">Existing customers with current maintenance will receive new license files via email as this release goes out.\u00a0 The new version of TMEditX Editor will install as an update to the current TMEditX, but the additional tools will be missing, and you&#8217;ll need to download the TMEditX Tools package to regain them.\u00a0 Your TMeditX will retain current configurations, and you will need to activate it using the new license file.\u00a0 The TMEditX Tools will need reconfiguration.<\/p>\n<ul>\n<li>PSF Releases v.2025.07.02, v.2025.07.01, and v2025.06.07.\u00a0 The release notes on what is contained are in the following two blog posts: <a href=\"https:\/\/www.tmurgent.com\/TmBlog\/?p=4040\">New in PSF 2025.07.01\/02 \u2013 Confessions of a Guru<\/a> and <a href=\"https:\/\/www.tmurgent.com\/TmBlog\/?p=4035\">New in PSF v2025.06.09 Terminate Children! \u2013 Confessions of a Guru<\/a><\/li>\n<li><strong>TerminateChildren<\/strong> <strong>Fixup<\/strong> introduced as an Available Fixup.\u00a0 This brings back a feature from Microsoft App-V packages that was highly sought after for customers that deploy applications for use in &#8220;Published Apps&#8221; form rather than &#8220;Published Desktops&#8221;.\u00a0<\/li>\n<\/ul>\n<p style=\"indent: 80px;\">Implemented as a new feature of PsfLauncher, this directive tells the launcher that when the launched target program ends, to check if there are any remaining processes that are a child-process of the launched target.\u00a0 If so, the launcher will issue a dialog box prompt alerting the user that their session is still open and allowing them to terminate the child processes to release the session.<\/p>\n<ul>\n<li><strong>New Scripting Variable.<\/strong> When adding application scripts to the package, the scripting previously supported two pseudo-variables, %MsixPackageRoot% and %MsixWritablePackageRoot%.\u00a0 By customer request, we have now added a third variable %MsixPackageFamilyName%.\u00a0 See PsfLauncher scripting documentation on the GitHub Wiki: <a href=\"https:\/\/github.com\/TimMangan\/MSIX-PackageSupportFramework\/wiki\/PsfLauncher\">PsfLauncher \u00b7 TimMangan\/MSIX-PackageSupportFramework Wiki \u00b7 GitHub<\/a><\/li>\n<li><strong>Run Key Fixup.\u00a0 <\/strong>Previously, we detected both Run and RunOnce Keys and reported them as &#8220;Unfixed\/Informational&#8221; items, alerting you to them when in your package but leaving it to you to deal with them manually.\u00a0 In this release, we split these into separate items by key type.\u00a0<\/li>\n<\/ul>\n<p style=\"indent: 80px;\"><em>RunOnce<\/em> Keys remain unfixed\/informational.\u00a0<\/p>\n<p style=\"indent: 80px;\"><em>Run<\/em> Keys now have an available fixup associated with them.\u00a0 If the fixup is used, it will translate the value and turn into an AppXManifest extension for the equivalent of old the start menu &#8220;startup&#8221; folder.\u00a0 Like other uses of this extension, when the package is installed, nothing happens, but (in a persistent OS scenario) each time the user logs back in the command will be run automatically.\u00a0<\/p>\n<p style=\"indent: 80px;\">Additionally, we added a command line option \/AutoFixRunKeys that will turn the fixup into a recommended fixup and automatically apply it to the package when recommended fixups are processed.<\/p>\n<ul>\n<li><strong>Duplicate Shortcuts.<\/strong> The most recent release of the Microsoft MSIX Packaging Tool (even if in isn&#8217;t &#8220;recent&#8221;), made changes that lead to the user seeing duplicate shortcuts.\u00a0 Previously, TMEditX detected and removed these.\u00a0 Changes in the last two release to improve other shortcut scenarios left a small gap where some of these duplicate shortcuts remained, even after processing all of the recommended fixups. This gap is now eliminated and a recommended fixup for duplicate shortcuts will resolve it.<\/li>\n<li><strong>AppPaths<\/strong> to\u00a0<strong>LoaderSearchOrder. <\/strong>Some applications use AppPaths registration to list additional folders with hold dlls for the purpose of getting the LoadLibrary function used to load dlls to look in those additional folders.\u00a0<\/li>\n<\/ul>\n<p style=\"indent: 80px;\">Two releases ago we added a recommended fixup to turn those entries into a package level extension of type\u00a0<strong>LoaderSearchOrder<\/strong> that accomplishes the same thing.\u00a0 Then we discovered that the new extension has a limit of only 5 filepaths, and we saw one app that had over 20 folders it was registering.\u00a0<\/p>\n<p style=\"indent: 80px;\">In the follow-up release we changed the detection to make the fixup be in the Available list, and to not exceed the five path limit, thus supporting up to the first 5 entries.\u00a0<\/p>\n<p style=\"indent: 80px;\">In this release, we return the fixup to the Recommended list but do a better job parsing the list.\u00a0 We remove folders from the list that have no dlls, remove folders that would already be covered by LoadLibrary, and limit the list size to 5.\u00a0 We still recommend using the PsfDynamicLibraryFixup for such apps as the first choice, but this makes for a decent backup option.<\/p>\n<ul>\n<li>A change has been made for how we implement COM CLSID remediation.\u00a0 Due to a mistake in the Microsoft Documentation for AppManifest COM extensions, we were limiting what could be combined in a COM registration.\u00a0 We now recognize that the documentation was in error, and will now combine items when appropriate.\u00a0 This not only reduces the size of AppXManifest files with lots of COM, but it also significantly reduces the confusion of someone trying to read it.\u00a0 It also allowed us to do more remediation (normal adding of missing COM to the package) and less anti-disregardation (spoofing of GUIDS so that we can get things registered when limited by the schemas unnecessarily).<\/li>\n<li>Added support for a type of COM previously unsupportable.\u00a0 The specific case is for a 32-bit managed COM in-process COM object on an x64 operating system that uses mscoree as a proxy.\u00a0 This is a new recommended fixup.<\/li>\n<li>When adding any COM CLSID, check if the filepath is under VFS\\SYSTEM.\u00a0 If it is, check if the file is actually there on the system, or is instead in VFS\\SYSTEMX64.\u00a0 This is an oddity of some MSI installers.\u00a0 If detected, we change the registration to the correct path.<\/li>\n<li>Fixed the incorrect regex pattern used to validate ST_ExcludedDirectory in the VirtualizationManifestSchema.\u00a0 This apparently is a bug in the official schema released in the Windows SDK, but Microsoft has now patched it (or removed the validation check) in the desktop AppInstaller.\u00a0 This bug had prevented us from using what Microsoft calls &#8220;Flexible Virtualization&#8221;.\u00a0 See next item also.<\/li>\n<li>Added new feature that offers a new Available fixup to add &#8220;Flexible Virtualization&#8221; to the package.\u00a0 See our White Paper on what this is for and how it can be used: <a href=\"https:\/\/tmurgent.com\/appv\/en\/resources\/white-paperlist\/651-flexible-virtualization\">Flexible Virtualization (PackageWriteVirtualization)<\/a> The fixup will add both the Desktop6 and Virtualization Properties, along with the unvirtualizedResources Capability, to the AppXManifest.\u00a0 If the PSF MfrFixup is also used in the package, it also adds the override configuration needed in the Config.Json configuration for the fixup.\u00a0 Also added a command line option \/AutoAddfileSystemWriteVirtualization to turn this fixup into a recommended fixup for command-line fixing of packages.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Where to get the release<\/h3>\n\n\n\n<p>The latest version of TMEditX Editor is found at the following link.&nbsp; TMEditX has a fully functional trial mode that can be used to verify just how good it is.&nbsp; <a href=\"https:\/\/tmurgent.com\/appv\/en\/buy\/tmeditx\/tmeditx-download\">TMEditX Download<\/a><\/p>\n\n\n","protected":false},"excerpt":{"rendered":"<p>\u00a0 Introduction A major release for TMEditX, version 6.0.0.0 has been released, and along with it a separate release of new Community Tooling for working with MSIX. TMEditX Editor will continue to be a licensed commercial editor and fixer for MSIX packages. TMEditX Tools is an MSIX package containing free community tools that aid in&hellip; <a class=\"more-link\" href=\"https:\/\/www.tmurgent.com\/TmBlog\/?p=4042\">Continue reading <span class=\"screen-reader-text\">Announcing TMEditX Editor 6.0;  also New FREE Community Tools<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0,"footnotes":""},"categories":[53,57,50],"tags":[52,7],"class_list":["post-4042","post","type-post","status-publish","format-standard","hentry","category-msix","category-packaging","category-tools","tag-msix","tag-tools","entry"],"_links":{"self":[{"href":"https:\/\/www.tmurgent.com\/TmBlog\/index.php?rest_route=\/wp\/v2\/posts\/4042","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.tmurgent.com\/TmBlog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tmurgent.com\/TmBlog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tmurgent.com\/TmBlog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tmurgent.com\/TmBlog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=4042"}],"version-history":[{"count":18,"href":"https:\/\/www.tmurgent.com\/TmBlog\/index.php?rest_route=\/wp\/v2\/posts\/4042\/revisions"}],"predecessor-version":[{"id":4071,"href":"https:\/\/www.tmurgent.com\/TmBlog\/index.php?rest_route=\/wp\/v2\/posts\/4042\/revisions\/4071"}],"wp:attachment":[{"href":"https:\/\/www.tmurgent.com\/TmBlog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=4042"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tmurgent.com\/TmBlog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=4042"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tmurgent.com\/TmBlog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=4042"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}