Items in this section allow you to control what you want the tool to recommend.  These are presented in the form of opt in/out selections.

• Pre-Psf.  Add an item in the Pre-Psf recommended fixes for the removal of uninstaller shortcuts and files.  Determination is if the shortcut or file contains the word "install". 
• VC Runtimes. We will always detect VCRuntime components in the package, including those added by the PSF. You have an option to remove them from the package and replace with the native Microsoft VCRuntime redistributables (both x86 and 64)
  • Opt-In: The tool will not add the VCRuntime files required by the PSF, and if the package contains replaceable VCRuntime files, a fixup will be added to the recommended fixes to remove them.  You are responsible for adding the necessary VCRuntimes to client systems natively.  The PSF needs the 2015-2022 packages.  Before running this fixup, check the fixup detail or Depedendencies tab to see which older versions the app may have required.
  • Opt-Out: The tool will add VCRuntime files needed by the PSF when applied.  VCRuntimes will be detected and a fixup added to the Optional fixups list.
• ILV. Always add Installed Location Virtualization (ILV) to packages.  If the PSF MfrFixup is added, it will be set to IlvAware mode.
• Desktop Shortcuts. Most companies don't want packages adding shortcuts to the user's desktop, and when this is not enabled, we remove them from the package.  Opt-in to this item if you don't shortcuts published to the user desktop and they will be removed.
• Windows.Shortcuts. The MMPT now adds the Desktop7 extension for windows.Shortcuts, but these usually cause bad shortcuts to appear.  When we add the PSF, we fix the reasons that they needed them, except for shortcuts intended to be delivered to the user desktop.  Opt-in for this removal.  If you opt-out, we'll fix up any issue with the windows.Shortcuts.
• Start Menu Folders. With this opt-in, we'll add in a fixup to add the folders for shortcuts if present in the original installation.  The exception is if there ends up being only one shortcut, then we'll remove the folder.  We also add a folder if multiple shortcuts to the start menu are in the package (after other cleanups) and will use the package name for the name of the folder.
• Control Panel Applets. Normally when these are seen they will be Available fixups and not automatically applied. Opt-in for this item if you want these in the Recommended list.
• Fonts. Opt-in if you want a fixup in the recommended list to register any fonts in the package missed by the MMPT.
• Min Version. Some extensions require the package MinVersion to be increased or the extension doesn't work.  With this opt-in enabled, we will update the MinVersion field in the package whenever one of these extensions is added.  The downside is you then can't install the package on older OSs.  Opt-out and we leave it alone, but you might not get that extension working.

These settings control what to do before building the package.

• Package Version. When set, we'll automatically update the last available field of the package version by one.  Maybe you like this, or maybe not.  You can always set the version in the Properties tab instead.
• Last Version Octet. Microsoft reserves the last field of the version for apps uploaded to the Microsoft Store.  You are probably not doing that, so check this box if you are uploading to the store and cannot use all four fields.
• Analysis Report. Check this to save a copy of the Analysis Report when you save the package. This is a small xml file that contains the details you see on the analysis page, as well as details of the changes made by TMEditX to the package.

These settings control what to do before and after building the package.

• Sign Package should be checked to perform package signing.  Without it, the remaining signing option, and all of the signing Method fields will be ignored.
• With the "Update Package Publisher from cert" checkbox selected, TMEditX will ensure that the Publisher field in the AppXManifest file matches the subject field of your certificate automatically, updating the manifest when you save the package.

Currently, three signing methods are supported.  The additional fields will depend upon the type selected but should be self-evident.  

• You can use signtool with a password protected PFX file.  This could be your self-signed certificate, or if you use a public CA and they still support PFX files.
• Digicert KeyLocker based signing where the actual certificate is securely stored in their cloud-based service.  This technique still uses the signtool is included inside this product, but you must install and configure the KeyLocker tools externally.
• Digicert (or potentially other Token based certificate).  These are certificates stored on an HSM device like a secure USB drive.  We officially support Digicert, and again you'll need to install the DigiCert/Thwate application externally.