Release date: 25 February 2025

Release notes Master Packager 25.2.9187

Improvements

Master Packager

We fixed multiple minor issues that previously caused extra manual work or confusion.

• Changing a files component in the file editor to a non existing component should create the component. (MPDEV-2221)
• Changing an items component in the feature editor to an existing component should navigate user to the new component. (MPDEV-2240)
• Disable features not applicable for MSP files and only allow editing via Table Editor. (MPDEV-2241)
• Add .MSP type in save dialog when editing a .MSP file. (MPDEV-2242)
• “Remove All Subkeys And Values On Install” should automatically update component KeyPath. (MPDEV-2273)
• Add cascade deletion for “Remove All Subkeys And Values On Install” action. (MPDEV-2311)

Master Packager Toolbox

We created Intune default value settings.

When uploading to Intune, we have noticed that different organizations interpret and use the Developer and Owner fields differently. By default, we assume that the Packager who packaged the app is the Developer in the Intune app properties, while the Owner is the person responsible for the application within the organization. However, if you use these fields differently, you can now modify them before uploading to Intune and set default values in the Master Packager Toolbox settings.
enter image description here

If you use ServiceUI.exe to enable user interaction in Intune for end-users then now you can set that as default installation command line yourself. This change will help you move you closer to eliminate boring parts of packaging.

enter image description here

• Add Owner field for Intune upload. (MPDEV-2250)
• Add settings to set default values for .intunewin packages. (MPDEV-2251)

Master Repackager

We got a few emails from customers saying the package was building with an error. We investigated and found that the application being repackaged has one or more files larger than 2GB. MSI technology does not support files over 2GB, so we created a feature that detects if a repackaged app has such large files. Now, you can repackage apps with files larger than 2GB, see which files haven’t been added to the package, and install those files using other methods, like PowerShell.

enter image description here

Master Repackager has excellent COM mapping logic and with this version we have improved it even more based on new very complex app repackaging experience.

• Add warning during build when repackaged application contains files larger than 2GB. (MPDEV-1971)
• Improve COM component mapping. (MPDEV-2266)

Master Wrapper

Master Wrapper is designed to be the UI for PSAppDeployToolkit. Now, it’s even better as we support the latest version, PSADT 4.0.6, and have improved various scenarios our customers have reported—such as supporting UTF8-BOM encoding and adding settings to remove certain safety mechanisms to speed up wrapping for those using advanced PSADT creation workflows.

enter image description here

• Save PSADT projects UTF8-BOM encoding (MPDEV-2248)
• Add a setting to allow users to save PSADT projects in empty folders or folders that do not follow the PSADT project structure (MPDEV-2282)
• Add a setting to disable prompt to open Files folder after saving project for the first time (MPDEV-2283)
• Update PSADT to 4.0.6 (MPDEV-2319)

Bugs fixes

We have fixed all reported and found issues.

• Master Packager - Correct typos for tooltips in Service Control editor (MPDEV-2298)
• Master Packager/Repackager - Icons cannot be loaded from dll files under System32 folder (MPDEV-2300)
• Master Packager Toolbox - Unescaped file paths in UninstallString registries are parsed incorrectly when building PSADT uninstall command line (MPDEV-2313)
• Master Packager Toolbox - Quotes in UninstallString registries are not preserved for arguments when building PSADT uninstall command line (MPDEV-2317)
• Master Wrapper - Main action sections are not matched correctly in some cases (MPDEV-2249)

Known issues

• $DeployMode is saved as empty string if installation mode is set to default and package is saved from Script Editor section. The issue occurs if package is saved from the script editor section. If package is saved from any other section, it will work correctly. The Issue will be fixed in the next version. We suggest upgrading from this version. Fixed in Master Packager 25.2.9188.