What's New in Version 12

IntuneWin package creation

The program now supports creating packages in the IntuneWin format. This feature is available in the Architect edition of the program. To create an IntuneWin package, set up a wrapping project, configure the installations to be included, and specify their silent deployment command-line parameters.

Both new and existing wrapping projects can used to generate packages in either MSI or IntuneWin format — you simply choose the format during package generation. IntuneWin packages created by the program support including multiple installations into a single package.

Publishing MSI, MSIX, and IntuneWin packages to Intune

The program now not only creates packages but also publishes them directly to Microsoft Intune. You can publish all supported formats: MSI, MSIX, and IntuneWin. The ability to publish packages to Intune is available in the Architect edition of the program.

In the Packages view, a new action for publishing to Intune is available. When selected, it opens a step-by-step wizard that guides you through the publishing process. The program can create an Intune application from the selected package. Once the application is created, you can assign it to users and devices directly in the Intune portal to distribute it across your network.

When you update a package and publish it again, the program detects that it was already published and lets you choose whether to create a new application or update the existing one. For IntuneWin packages, it is also possible to supersede existing applications, either by installing the new application over the old one or by uninstalling the old version before installing the new one.

MSIX package creation in the Enterprise edition

The Enterprise edition now supports creating MSIX packages. This includes both repackaging existing installations into MSIX and building new installations in MSIX format. Previously, MSIX packaging was exclusive to the Architect edition.

Improved automatic installation tracking

Installation monitoring was enhanced to automatically track setups built with modern installation frameworks. This allows the program to detect when an installation is complete and automatically start project creation and package generation. Thanks to these improvements, popular applications such as Microsoft Teams, Slack, Discord, and others can now be repackaged in automatic mode with precise end-of-installation detection.

New Windows 11 skin

The program now includes a Windows 11 inspired UI skin with controls similar to those in Windows 11. This skin is applied by default in new installations.

.NET requirement check improvements for MSI

The list of supported requirement checks for MSI packages was extended. In addition to .NET Framework, the program now supports checks for .NET Runtime, ASP.NET Core Runtime, and .NET Desktop Runtime.

If needed, you can specify the required versions of these dependencies. During deployment, the program will verify their presence and skip installation with an error if the specified dependencies are missing.

Monitoring environment check improvements

The monitoring environment check dialog, shown before monitoring starts, has been improved. It now provides detailed instructions on how to resolve detected issues and allows fixing them individually by closing running processes or stopping services that may affect monitoring results. If multiple issues are found, you can fix them all at once.

Additionally, if certain processes should remain running during monitoring, you can now add them to the process filters so their changes are excluded from monitoring results. Processes can be added to filters directly from this dialog and managed later in Preferences.

Tracking source project updates for packages

The program now automatically tracks changes in source projects for all packages. If you generate a package and later modify its source project, the package is detected as outdated by the program. When you test or publish it, the program will prompt you to either regenerate the package with the recent changes or keep the existing version.

This feature helps ensure packages stay up to date and reduces the risk of forgetting to rebuild them after modifying the source projects.

New and improved features

• Enhanced monitoring to support packaging of files with reparse points
• Updated package requirements to include the latest Windows builds
• Added an option to copy an existing project when importing into a new program version
• UI updates and improvements: Welcome view enhancements, improved side panel, better DPI support, and more

Resolved issues

• Fixed an issue with exporting projects larger than 2GB
• Fixed a potential issue with signing packages using Azure Key Vault