We replied with this blog post.

Yes. It is possible - just not straight out of the box. Let me show you how to do that with Master Packager Suite Community (free).

Steps​

1. Create a new MSI using Master Packager.

   

2. Go to Custom Actions -> Predefined Actions -> Add new Predefined Action. These are our pre-built MSI Custom Actions with a simple user interface to solve common app packaging problems with an MSI, and they work excellently under the system account that Intune and Configuration Manager use.

   

3. Select and add "Apply HKCU registries to all users". Why not "Remove HKCU registries from all users"? Because that one is designed to remove a whole registry key, however the ask is to remove only a specific value. For that we do not have a simple UI, yet.

   

4. Edit the registry content that needs to be removed. The trick here is to replace the value data with a hyphen "-".

Before:

Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\I Need This Key Forever]
"You Can Delete Me"="Please"

After:

Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\I Need This Key Forever]
"You Can Delete Me"=-

This change will make the "Apply HKCU registries to all users" action delete the registry value instead of setting it.

5. By default, "Apply HKCU registries to all users" is executed during installation. If that is the intent, then nothing else needs to be done. However, if you want to remove this registry value while leaving the key intact on MSI uninstallation, then go to the Master Packager Table Editor. Select InstallExecuteSequence and replace the Condition values for the MP_ApplyHKCUForAllUsers and MP_SetApplyHKCUForAllUsers actions from NOT REMOVE to REMOVE~="ALL".

   

Do not forget to add a name, version, manufacturer and a nice icon to the MSI.

Also, if you are creating an MSI that only uses a Custom Action, the MSI will finish installing with an error. Every MSI needs at least one Feature and Component. If you were to create a file, registry entry, etc., Master Packager would create a Feature and Components for you - but not in the case where there is only a Custom Action. To create a Feature and Component, go to Master Packager Advanced Editor -> Features and right-click to add them.

And it is done. We have an MSI that removes an HKCU registry value while leaving the key intact. All of this works under a system account installation with your deployment solution.

Application packaging is not just about finding a silent switch. It is an art to ensure your business applications are there when they need to be, and in a state that helps your business be the most efficient.

And for that it is good to be a Master Packager who knows how to remove a registry value without removing the key for all users while installing it from your favorite deployment system.

If you want to learn more about the art of application packaging and be able to package any Win32 app for your organization, check out our Master Packager courses, where we share our decade of knowledge in a 5-day remote workshop.

This was the fourth year that Cloud Tech Tallinn took place in chilly Estonia, and it was our first time attending. It was a short three-hour drive from Latvia, where the Master Packager team is based.

Every year, we try to support the community by sponsoring one to three events. These are great opportunities to share our knowledge and show off our software capabilities during sessions and at our booth. Our good friends from Robopack and Patch My PC were there as well.

The event took place in the Tallinn Creative Hub. This industrial-looking historic building used to be a boiler house for a power plant. Its 700-square-meter boiler room still contains two giant boilers that played a huge role in the city’s industrial history. Edijs and I had a great view of them; as video game fans, we felt like we were standing right inside a level!

We also got many compliments on our “I am Master Packager” mouse mats. A few attendees even called them “baby yoga mats,” ha ha! :)

Our session on standardizing packaging workflows for Intune attracted a lot of interest. It was great to see so many companies inspired to book a demo and learn the specific steps to bring packaging standardization to their own environments.

Many speakers talked about programming with AI, and we were lucky enough to attend a few sessions ourselves. They were actually fun! Usually, tech sessions can be quite dry, but these speakers were engaging and focused on real-life lessons.

Since this conference attracted so many developers, we saw unexpectedly high interest in the Master Packager Dev solution. This tool lets developers automate MSI and MSIX creation directly within their DevOps CI/CD pipelines. When they heard about the solution, many seemed ready to say, “Sounds amazing, but we probably can’t afford it,” since they’re used to these tools costing thousands of dollars per user. But when they learned our actual pricing, the reaction was usually, “Wow, I’ll take it!”

We’re committed to removing the obstacles that prevent vendors from creating the high-quality Windows application packages that end-users love, enterprises want, and the OS needs.

The next conference we’ll be sponsoring as a Gold partner is our favorite app management event - AppManagEvent. We’ll be there with a booth and a special session, and we hope to see you there in person!

Have an easy or hard package, because you’re a Master Packager!

p.s.

Our “Become a Master Packager” remote workshop is fully booked, and we had to say no to a few people. If you’d like to learn how to package any app with us, register here. If there’s enough interest, we may run another workshop this spring.

Toms

Our mission is to end the endless cycle of re-doing, where developers spend time figuring out how to build an installer while organizations spend time and money fixing them. This cycle creates so much wasted effort and cost around installers - resources that could be directed toward moving the world forward instead of re-doing stuff.

Master Packager Dev is the solution to finally stop this waste. Version 2.0.0 focuses on beauty and user experience for home users. Software developers usually build installers for home users first and only then think about organizations that need to deploy those installers to thousands of devices at once. If we want more developers to choose a solution created by experts, we need to make the installer excellent not only for organizations and their deployment systems, but also for regular home users.

Build beautiful and functional installers​

Install welcome view​

When double-clicking on the MSI we wanted to make everything about installer visible and clear.

• Logo - It should be clear what is the app logo.
• Name - Main title is the app name that is being installed.
• Vendor - Next important component is the vendor and hyperlink behind it moving the user directly to the vendor’s site.
• Version - Version is also a hyperlink moving users to the release notes URL if they want to see what’s new before installing the software.
• Description - Short description about the software you are about to install. We almost never see that implemented so we want to make it a practice.
• Privacy & Terms - All your legal info behind a URL.
• Auto-Update settings - In the right top corner the cog wheel opens settings for user to control auto-update component if the software vendor has enabled this Master Packager Dev feature ensuring their application is always up to date either by silently installing new updates or showing update notification.

It is possible to control the hyperlink and Install button color to match your logo and style. But that’s about it.

The design is created using Windows Fluent Design guidelines, modern and for us beautiful. No options to add custom dialogs. No other ways how to modify this installer UX, because all that leads to waste, complexity and organizations re-doing the package so it can be deployed in their environment. Every component here is for a reason. To solve a problem. Nothing extra. And that’s how it should have been done a long time ago.

It’s time to turn the page so developers can focus on applications while letting Master Packager Dev focus on the installer.

Installation view​

When the installation starts it displays a simple progress bar.

However, if the MSI detects a running conflicting process during installation (which the developer can specify in the project file), it shows a list of processes that the user needs to close. This lets the user clearly see exactly what is holding up the installation, allows them to save their work in these applications, and close the processes manually or by pressing the “Close and continue” button. The installer will then close all conflicting processes for the user.

Installation Completed view​

Finally when the installation is finished user can clearly see that installation was successful with the green checkmark icon and text.

But that’s not all. With 2.0.0 version developers now can specify applications end-user can choose to open straight after the installation. It is possible to add more than one application to open and user can select more than one to open directly from the installer view instead of browsing the Windows start menu and trying to guess the shortcut names.

Auto-updates view​

Another component that many developers try to build their own version is installer auto updates.

With Master Packager Dev you can specify our built-in auto-updater component in the json project file like this:

This will enable either silent updates for the application or notification like this:

Auto-update UI was the main reason that we understood we can make the installation and update experience alike. We took the lessons learned from the update notifications UI and applied them to the installation view, creating a better experience overall.

Developers can choose whether to include the auto-update component in their installers, while end-users and organizations can control whether they want to enable auto-updates. This provides full control for everyone and ensures an excellent experience both for developers building auto-updates and for end-users using them.

Where our auto-update system truly shines is for enterprises. They can enable automatic updates during the first installation through their deployment system, and all subsequent updates happen under the system context, thus no admin permissions are required for limited users.

Other improvements​

We have added more needed functionality and fixed multiple bugs that you can see in Master Packager Dev 2.0.0 release notes here.

———

We’ve spent a lot of time building an installer that solves the problems we’ve encountered while working with, fixing, and creating thousands of installers over more than a decade. A installer that you can get for your own application.

Consider choosing Master Packager Dev if you want to focus on your application - the real source of value, instead of installer.

Master Packager Dev is free for individuals and non-commercial users.

• Download
• Documentation
• Example video

What Changed?​

With Notepad++ v8.8.8, a 64-bit MSI is now available for enterprise IT deployment. The MSI installer was one of the most requested features. On the Notepad++ download page, next to the EXE installer and a few portable zip options, now lies an MSI installer.

How Everyone Deployed Notepad++ Until Now?​

It has always been complicated to modify the current Notepad++ EXE installer to meet enterprise standards in environments where end-users do not have admin rights, including disabling auto-updates and pre-installing specific plugins.

To overcome these issues, IT admins from all over the world have used one of the following methods to deploy Notepad++.

1. Install EXE with available command line options by manually downloading the EXE or using community package managers like WinGet.
2. Download installer from hass.de website where a custom Notepad++ MSI was created and maintained by GitHub user alexhass.
3. Repackaging every new Notepad++ EXE installation into high-quality MSI using paid repackaging software and making required adjustments for the organization’s needs. We have a video explaining how to do that in detail here:

Embedded content

In the Notepad++ GitHub project, maintainer donho mentions that MSI wasn’t created earlier because:

• It was difficult to support multiple languages in MSI
• There were some visual glitches during installation using earlier versions of WiX
• Didn’t want to maintain two installer types

Now, as the Notepad++ project matures, he sees the MSI as a basic and simple installer used solely for IT deployment and nothing more. An MSI he can maintain independently. An MSI that will be available on the Notepad++ website and will not be available in the Microsoft Store based on these comments:

• https://github.com/notepad-plus-plus/notepad-plus-plus/issues/9221#issuecomment-991374797
• https://github.com/notepad-plus-plus/notepad-plus-plus/issues/16767#issuecomment-3508548630

In this blog post, we investigate how good the new MSI is for enterprise use cases.

How Good Is the New Notepad++ MSI?​

The new Notepad++ 8.8.8 MSI is created using WiX Toolset 6.0.2.0.

The MSI itself is minimalistic, simple, and without any ICE MSI warning or errors, which is great.

However, the installer is missing several major requirements to be called an enterprise-ready installer, as it was pointed out by several GitHub users prior 8.8.8 release.

So, what’s good, what’s missing, and how can we make adjustments to have a truly enterprise-ready MSI?

✅ What’s Good in The MSI​

Customization And Overview Paradise​

It’s an MSI. Everything is visible and clear. No surprises and ease of mind for IT admins when deploying it to thousands of endpoints compared to EXE installations, where they often act like black boxes.

Adding plugins​

To install Notepad++ plugins from the app, it requires end-users to have admin rights since the files are installed into Program Files. But now that we finally have an official MSI, it’s super easy to add required plugins. Just create an MST file and place plugins into: “[ProgramFiles64Folder]Notepad++\plugins”. A great example of what you can do with MSI customization.

No Desktop Shortcut​

There is no desktop shortcut in the MSI, which is good. The desktop is a user’s private space, and no application should create shortcuts there by default. This is an especially widely accepted practice in the majority of organizations where application packagers spend time deleting desktop shortcuts from third-party installers.

For developers, the best practice is either not to create the desktop shortcut at all or, at least, to have a property that can be easily used via the command line when deploying to disable the creation of the desktop shortcut.

❌ What’s Missing in The MSI​

No Option To Disable Auto-Updates​

There is no out-of-the-box option to disable Notepad++ auto-updates in the MSI, and this is a must-have. For MSIs targeted specifically for enterprises, auto-updates should be disabled by default.

When building an installer, developers should always take into account that their application may be used by larger organizations where they have application management standards to control application updates themselves.

Another concern, which remains unanswered, is what exactly gets installed when an auto-update is triggered for app installed via MSI. We assume it installs the EXE version on top of the MSI, which complicates things because we couldn’t identify any changes that would prompt auto-update to download the correct installer. This issue is more concerning for home users, who might accidentally install the MSI version of Notepad++ and later receive EXE-based updates on top of the MSI.

No Upgrade for EXE installs​

The MSI does not upgrade the previously installed Notepad++ EXE installation.

It would be excellent if software developers created installers that upgrade all their previous app versions, despite the installation format. The best solution would be to strive to support only one type of installer, so there wouldn’t be a need to worry about multiple installation type upgrade support in the first place.

MSI reliability properties​

Over the years of doing app packaging, we’ve learned to always use specific MSI properties to improve installation reliability, for example, to prevent unexpected machine reboots using REBOOT=ReallySuppress property.

We have a blog post describing these properties here.

Missing functionality in the App​

Comparing MSI-installed Notepad++ with the EXE-installed version, we noticed that Markdown language options (both standard and dark mode) are missing in the MSI installation.

If you need these features, extract files from the EXE installation and install them in the per-user location. We showed how to do this in our Notepad++ repackaging video using the free Community version of Master Packager software and our Predefined Custom Actions.

Missing App Path Registry Key​

It’s a registry key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\App Paths that holds information about the path to executable files. It allows you to run applications without having to type the full path in the Run dialog.

Improving Official Notepad++ MSI as an IT Admin​

Now that you have an official MSI from the Notepad++ team, you can skip repackaging EXE or using other people’s created MSIs, but focus on creating the best version of the Notepad++ package yourself.

Here are the steps on how to do it:

1. Download the MSI
2. Open the MSI with Master Packager (Free community version).
3. Click Transform → New Transform → Save next to the MSI file.

4. In Advanced Editor → Uninstall or Change Programs → Uncheck “Display Modify Button” as it is not needed.

5. Go to Table Editor → Component table.

6. Filter by “UpdaterFolder” and add DONTINSTALL to the Condition column for all filtered components. This will prevent installing MSI components that hold files responsible for Notepad++ auto-updates.

   Note that this will break plugin installation functionality in the app, but that’s ok, as users would need admin rights anyway to install Notepad++ plugins, and enterprise end-users do not have admin rights to do any of this.

7. Add App Path Registry to improve end-user app launch experience. Go to Registries view → Create HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\App Paths\notepad++.exe key with default registry name value pointing to notepad++.exe primary file key and for Path registry name value pointing to the Directory name where the notepad++.exe is installed.

8. Apply MSI reliability properties. Pro tip - you can automate applying these properties with one click using Master Packager templates functionality.

If you need to have specific plugins preinstalled, then:​

• Install Notepad++ on a test machine.
• Grab plugin files from: “C:\Program Files\Notepad++\plugins”
• In Master Packager Advanced View → Files view, drag and drop plugins into: “[ProgramFiles64Folder]Notepad++\plugins”
• Click Build Now. This will create a data.cab file that must stay next to the MSI and MST during installation.

If you previously repackaged Notepad++ into an MSI or used MSI from hass.de, then:​

• Reuse your previous MSI Upgrade Codes.
• In Master Packager → Advanced View → Upgrade section
• Press NEW
• Paste your previous MSI package Upgrade Code to Upgrade Code textbox
• Set Max Version to 8.8.8
• Set Action Property to WIX_UPGRADE_DETECTED
• Press ADD and then NEW again
• Paste your previous MSI package Upgrade Code to Upgrade Code textbox
• Select checkbox Detect only
• Set MinVersion to 8.8.8
• Set Action Property to WIX_DOWNGRADE_DETECTED

You’re good to deploy this as is. But if you want to take it to the next level, we strongly recommend wrapping it with PSAppDeployToolkit (PSADT).

Wrapping into PSADT​

You’ll get a great end‑user experience with PSADT pop‑ups to prevent forced closes and standardized package creation, plus easier removal of previous EXE installations using built‑in PSADT functions.

For that use Master Wrapper (Free or Pro) to easily wrap the MSI inside the PSADT.

1. Open Master Wrapper
2. Drag & Drop MST file to the application info view or select “Load data from installer”.

3. Add description. (If you will upload this package to Intune using Master Packager Toolbox, then this info will automatically be used for Intune Company Portal, saving you time)
4. Move to “Main actions” -> Install view
5. Add PSADT function Uninstall-ADTApplication in the first line to ensure Notepad++ EXE uninstallation before starting to install new MSI version.

6. You can see that Master Wrapper automatically loaded notepad++ exe as a process to be closed using the PSADT prompt if opened during install and uninstall, ensuring an amazing end-user experience.

7. That’s it. Save it and upload to your deployment system or use Master Packager Toolbox to upload to Intune faster.

You can download a ready package with the created MST and PSADT here.

How the Notepad++ installer should have looked from the start​

The main problem is that there are two installers, and neither of them works as well as they could.

Both need to be created, maintained, and communicated to end-users. How is a regular home user supposed to know which one to install? How would they know that the MSI option is meant only for enterprises, will be missing features, and might even try to install an EXE during an update, making their machine a mess? Sure, a text could be added next to each installer explaining what it’s for, but that’s just solving a problem, not eliminating it.

With open-source projects, we often hear that it is hard to find people who are willing to help maintain the project or contribute. But in this case, the MSI is created using WiX Toolset and ends up being 807 lines of code, while their EXE installer is built with NSIS and requires multiple files and folders, each containing hundreds of lines of code that someone would need to read and understand in order to help.

Building MSI or MSIX or both using Master Packager Dev​

After years of packaging thousands of third-party apps for organizations, we learned how hard it is to understand, build, and afford a great installer. That is why we created Master Packager Dev. It is a command-line tool that developers can integrate into their CI/CD pipelines to build excellent MSI and MSIX packages from a simple JSON project file. It is free for non-commercial organizations like Notepad++ team.

The project file for MSI​

We decided to go with JSON file as it easy to create and read.

Master Packager Dev will not only build the installer, but also sign all binaries and installer, add Windows 11 modern context menu or add auto-update component that can update package also for users without admin rights completely silently.

This is how the project file looks like to build MSI that works great for home users as well for enterprises.

Build is simple as running mpdev build path_to_json

The end result is an excellent MSI file for organizational deployment systems, as well as a simple installation experience for home users.

It is also possible to add MSIX option in the project file if you know your app will work under MSIX packaging type.

Download Master Packager Dev, try it yourself, check out the documentation or reach out to us for help or advice.

Final thoughts​

It is great that the Notepad++ developer is starting to listen to the community and is now offering an MSI installer. It is a much better option than the EXE created with NSIS (Nullsoft Scriptable Install System) or Inno Setup, which let developers build installers that organizations often need to redo afterward.

However, as this new MSI is clearly marked as an enterprise deployment-ready solution, it really isn’t due to the fact that auto-updates are left enabled without official instructions on how to disable them, there are missing features when compared to EXE installation, and IT admins still need to do packaging before they can deploy the installer.

The goal should be to create and support only one packaging type that is ideal for home users, and organizations do not need to spend extra time packaging it. An MSI is a perfect packaging type to achieve that, either using WiX Toolset, Master Packager Dev, or other solutions.

Having MSI for Notepad++ as an additional packaging type is a great first step forward, and we should be happy even if it is not perfect (yet). :)

———

If you as third-party app packager, IT admin or independent software vendor developing your own app are ready to build Windows application packages that end-users love, enterprises want, and the Windows OS needs we are here to help with our knowledge and solutions.

Our mission is to help finally end the endless cycle of re-doing where every organization is forced to waste time and money fixing vendor applications that should have been created correctly from the start.

Have an easy package, or hard, because you’re a Master Packager.

As with every October, the Master Packager team is back in Latvia from the amazing AppManagEvent. This year was special for three main reasons.

First, we had the chance to meet up with friends we hadn’t seen in a long time and others we had never met in person, all of whom we had known through application packaging.

Rory Monaghan, Dan Gough, and Dan Cunningham were among the first Master Packager advocates to spread the word about how good the Master Packager software is, completely unsponsored. I do not know if they realized how important that was, especially in the early days when no one knew about us and we were bootstrapping the company with no budget for marketing. Thanks to AppManagEvent, we got to meet them and say thank you in person.

We met so many people: partners, friends, customers, and speakers. The entire day was spent networking for a full 11 hours. We really enjoyed it.

Second, we had an opportunity to speak on the main stage about PSAppDeployToolkit and MSI. We support many organizations and users through different channels and have noticed that experienced packagers who know MSI technology are increasingly being succeeded by system administrators who rely solely on PowerShell. This inspired Dan and me to collaborate on a session comparing PSAppDeployToolkit and MSI in various packaging tasks, showing how choosing the right technology can save hours of work and improve internal app management quality in general.

Third, but not least, we announced and showed a sneak peek of our integration with the Patch My PC.

Patch My PC, a leading third-party patch management solution, offers a catalog of pre-packaged apps to keep your machines up to date with the latest versions. However, as it is for every third-party catalog - not every app organization may need is included or can be pre-packaged. For those missing apps, organizations use an application packaging solution like Master Packager to package them. In upcoming Master Packager releases, we’ll introduce direct upload of a custom app to the Patch My PC Cloud portal right from within Master Packager. This will save even more time and further streamline the packaging process.

Finally, thank you, Coert Bosker, Danny van Dal, and the entire Professional Development Systems BV team, for organizing AppManagEvent . It’s the best-organized IT event with the most application management–focused attendees we’ve ever attended. Looking forward to AppManagEvent 2026 on October 9, where we plan to showcase the best version of Master Packager yet.

Inspired and full of energy to execute our vision - making app management easy and affordable for companies of all sizes. 2026 will be our most exciting year yet, where we will bring the most value to those involved in application management.

Application packaging solution PACE Suite, developed by Infopulse, which is now part of Tietoevry Create, has suspended new product license sales from June 30, 2025.

In July, 2025, I can point organizations to only four professional app packaging solutions that you can buy licenses of and that will do great job solving main application packaging challenges. However, public release notes and industry feedback indicate that two of these solutions have a significant slowdown in development and innovation in recent years.

That means that only two vendors are left that continue to regularly improve the software, innovate with features that actually help with real problems (not only mandatory maintenance), show up in conferences, give sessions and write blog posts to help others.

One of these two packaging solutions who haven’t slow down in 2025 but only expands, of course, is Master Packager. And initial business instinct would tell: “Great, fewer competitors mean more customers will find out about Master Packager!“. While somewhere that’s true, it hides more complex issues underneath the surface - the trend is that soon there will be even fewer app packaging solutions left.

Competition is good. For companies like Master Packager and consumers. It forces companies to push forward. To think. To execute. To innovate. To keep the price down. And that leads to better products and ultimately a better life for consumers. In Latvia, for example, we have access to unlimited lightning fast (average 300-1000 Mbps) internet and unlimited calls for less than €30 per month. All thanks to competition in the internet provider space.

Over the years, many app packaging tools have been discontinued, like Wise Package Studio by Symantec in 2013 and MSI Studio by Dell in 2013. Many have been just left for slow death, like the brilliant MSI editing tool InstEd It, which has inspired us a lot. Microsoft ORCA has remained untouched for almost two decades. Even the Microsoft MSIX Packaging Tool, hasn’t been updated for more than a year, although lacking a ton of features to be useful with modern packaging format MSIX adaption.

Demand for app repackaging has decreased due to better support for silent installations from software vendors and fewer OS compatibility issues compared to the migration times from XP and Windows 7. There are also more apps available in Microsoft Store, WinGet, and multiple third-party patching catalog providers help reduce the need for popular app packaging.

The new generation of IT admins who play the role of deployment specialists, but who have never seen what impact streamlined app packaging can bring to organizations’ efficiency, often choose an easier way to deploy apps and be done with it. That comes with a price tag in long run in terms of standardization, troubleshooting and more important - security.

All these reasons makes app packaging look less needed. But enterprise needs haven’t disappeared. No single third-party catalog can update and configure all applications in a medium to large environment. People are rotating and IT pros new to app management do not have experience how to handle low quality application installers. Standardization, predictability, security, and efficiency are key cornerstones for a mature, efficient, and stable organization. That’s where tools like Master Packager provide value, giving organizations full control to package any app to meet their requirements.

We started developing Master Packager in 2014, with public appearance in 2018. Entering an already mature market dominated by well-known tools was challenging. Yet, as professional packagers ourselves, we saw that multiple problems existed: tools stopped improving, were expensive, overly complex, and often lacked features we considered essential. We knew the market and we understood the customer and the tools. Knowing that made us strong to continue fulfill our vision - making app management affordable and easier.

We have been profitable from day one while offering professional application packaging solution for affordable price. We love building products, we love application packaging, and we love helping organization become more efficient and save money.

There is no doubt that app packaging is still needed and will be for many years. But not on the same scale as before. For vendors with large teams and complex packaging solutions full of features no longer needed in the Windows 11 era, it will be hard and we can already see that happening.

For us on other hand with our decade of app packaging knowledge, small team, focus on problem solving not maximizing profits and fully owning the solution ourselves we strive to be the number one choice for many organizations understanding how important application management is. For so many organizations we already are. But we know there are more organizations out there discovering us every day - and once they do, they never look back.

• If you are a PACE Suite existing customer and are now looking for a new professional app packaging software, consider choosing Master Packager.
• If you’re using a software packaging software with slow release cadence, do not see new features that bring value to you and cost a fortune - consider looking into Master Packager.
• If you are only using PSAppDeployToolkit (PSADT) to package apps, consider learning more about what a comprehensive app packaging solution like Master Packager can provide to you and your organization. To package any Win32 custom app with highest standards in reasonable time , then PSADT is not enough.
• If you do not have a packaging tool and you do not know why it is needed and where to start, consider reaching out to us and let us help you and your organization learn and get better.

Have an easy package, or hard, because you are a Master Packager!

We’re back in Latvia after attending Workplace Ninjas UK 2025, which took place in the beautiful city of Edinburgh.

This was our first time attending a Workplace Ninjas summit and our first time visiting the beautiful city of Edinburgh. We flew in on Sunday, checked into our hotel, and joined the pre-event party with the organizers, speakers, and attendees. It was a great icebreaker before the event. We talked, ate snacks, played games, threw darts, and even learned how to throw an axe.

The two-day conference kicked off the next day. It was exciting to meet our happy existing customers and hear their stories in person. As always, our “I am Master Packager” stickers and mouse mats were a hit.

For us, an excellent conference is one with many attendees looking for an application packaging solution or those who have not yet discovered the benefits of proper packaging practices. That’s where we come in with our sessions.

Our Sessions​

1. How to Become a Master Packager: Package Any Custom App for Intune with Confidence​

In this session, we reminded everyone why application packaging is needed for organizational efficiency. We shared our workflow for packaging teams and demonstrated how our software can help package any application for Intune.

⬇️ Download video slides: How to Become a Master Packager: Package Any Custom App for Intune with Confidence

2. The UI for PSAppDeployToolkit - Master PSADT V4​

Here we explained the importance of PSADT in application packaging. With PSADT V3 no longer supported, we showcased what’s new in V4.0.x and what’s coming in V4.1. We reminded why migrating to PSADT V4 in 2025 is needed to be up to the date and have a support from the open-source community. We also demonstrated how Master Wrapper, our application, simplifies the migration from V3 to V4 and how huge value it can bring packaging any apps into PSADT V4 using the Master Wrapper.

⬇️ Download slides: The UI for PSAppDeployToolkit - Master PSADT V4

Final Thoughts​

Workplace Ninjas UK was outstanding not just because of the amazing attendees but also thanks to the top of the class organization. Huge thanks to Dean and the team for setting this up.

We enjoyed this event and saw a great opportunity to help many new organizations adopt better application packaging practices that improve efficiency for their business, end-users, and IT teams.

Until the next one.

Toms and Edijs from the Master Packager Team

This week has been rich with 3 major announcements in the app management space:

1. Intune now supports importing Win32 apps from the Microsoft Store.
2. Administrator protection, a new Windows 11 platform security feature, will make app management more challenging.
3. Master Packager new release gets more attractive for MSPs.

1. Importing Win32 apps from the Microsoft Store into Intune​

• Announced at Microsoft Build.
• The feature is currently in preview.
• The search shows a “Win32” type, indicating that it is a Win32 app.
• Logo is not selected automatically. 🤦‍♂️
• No option to change the install command line.
• The Microsoft Store app (new) search now shows AI apps and age-restricted apps as well.

Read more here: https://blogs.windows.com/windowsdeveloper/2025/05/19/microsoft-store-expands-opportunities-for-windows-app-developers/

2. Administrator protection: a new Windows 11 platform security feature​

Announced at Microsoft Build. It’s important for IT Pros to understand how this feature will work and the impact it will have on desktop applications and the way they are packaged. This could potentially create issues for organizations that deploy per-user installers via Configuration Manager or Intune.

However, this needs to be tested before I can say for sure. There may be many applications that won’t work correctly due to the way files will be saved when an app is launched using admin privileges while the Administrator protection feature is enabled.

Read more here:

https://blogs.windows.com/windowsdeveloper/2025/05/19/enhance-your-application-security-with-administrator-protection/

3. Master Packager 25.4.9272 release highlights​

This week we launched a new version of the Master Packager software to help package applications better and faster.

• Added multi-tenant support for Intune upload. MSPs and larger organizations will love this.

• Added group assignment support for Intune upload. If you test your packages in Intune via a specific user or device group, you will love this.

• Script builder for PSADT – A new tool that will help build your scripts better than AI and faster than doing it yourself.

  The first script builder actions are for registries and Windows Firewall rules. We have a couple more actions in mind. Let us know what actions you want us to build next.

• We fixed all reported bugs including the one reported 2 days before the release.

• The new Master Packager update mechanism that we introduced in the previous version is in action now:

  • No need for admin rights.

  • No need to go to the website and download the installer.

  • There is a way to enable updates automatically, silently, in the background.

    UI for that will be enabled later, but you can configure it from the settings file in the installdir.

    

Read more here:

https://www.masterpackager.com/master-packager-release-notes/25.xxx/25.4.9272

Have a great weekend.

Toms Knostenbergs

Master Packager

What?​

In October 2023, Microsoft announced that VBScript will be deprecated. In future releases of Windows, VBScript will be available as a Feature On Demand before its removal from the operating system.

*VBScript (“Microsoft Visual Basic Scripting Edition”) is a

scripting language developed by Microsoft.*

*Feature On Demand (FODs) are Windows features that allow you to enable

and disable additional functionality for your devices at any time. On

Windows 11, you can access these features by navigating to Settings ->

Apps -> Optional features.*

WHY?​

The reason why Microsoft is deprecating VBScript is because it’s a legacy scripting engine component that Microsoft does not recommend using unless it’s absolutely necessary, as it may contain security vulnerabilities. There are more modern languages available that offer better functionality like JavaScript and PowerShell.

When?​

Microsoft shared their VBScript deprecation plan in their blog post. It will happen in three phases.

• Phase 1 VBScript will be pre-installed on all Windows 11, version 24h2 and on by default as FODs.
• Phase 2 that will happen around 2027 VBScript will no longer be enabled as default. With
• Phase 3 VBScript will be retired and eliminated from future versions of Windows. When this could happen is currently unknown.

What is the impact?​

VBScript is frequently used by organization in-house development teams for automating tasks and creating utility tools, as well as by Windows operating system administrators. While the industry standard for most tasks has shifted away from VBScript to languages like PowerShell and other scripting languages, there are still cases where VBScript remains widely used.

In application management, Microsoft Installer (MSI) capabilities often fall short of making the necessary changes when deploying application packages in an enterprise environment. Therefore, IT system administrators and application packagers utilize VBScript, either for MSI Custom Actions or as a separate file, to implement the required changes during package installation or uninstallation.

When installing MSI without VBScript feature the MSI will fail with the following error:

“The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2738.”

When reading the MSI log file you will find the following error message:

“Error 2738: Could not access VBScript runtime for custom action”

Another scenario where IT system administrators rely on VBScript is when they need to run PowerShell scripts in a user’s context without triggering any pop-ups. Running a PowerShell script in a user’s context can result in opening and closing PowerShell windows, which can be disruptive and annoying for end users. As a solution, enterprise administrators turn to VBScript to launch the PowerShell script.

How to Prepare to Work Without VBScript?​

Please note that at the time this blog post is written, it is still possible to use VBScript as an optional feature in the Windows OS. However, Microsoft’s official announcement of VBScript deprecation due to security reasons is a strong indicator that, in future Windows releases, VBScript may no longer be available. This could potentially disrupt organizations relying on this solution, causing issues and making things to not work as expected.

The exact timing of this change is currently unknown, as well as the specific files and libraries that will be removed from the Windows Operating System with VBScript feature removal. Therefore, it is a good idea to prepare your environment to not rely on deprecated Windows features.

Here are the steps we recommend organizations consider taking to prepare for a transition away from VBScript usage in their environment:

1. Identify in-house developed applications that use VBScript and find suitable replacements, such as PowerShell or another programming language.
2. Assess third-party applications in your environment that may rely on VBScript, starting with older applications that are no longer actively developed.
3. Determine which MSI packages have VBScript Custom Actions or contain .vbs files in it, and replace them with PowerShell scripts or contact the vendor to make necessary adjustments.

Tools that can help​

Here is a list of tools and descriptions that can assist you in transitioning away from using VBScript:

PowerShell​

Replace VBScript with PowerShell. Explore whether there might be an even better alternative to your current VBScript solution, such as Python.

For System Administrators, you may encounter situations where you need to run PowerShell .ps1 scripts silently without any pop-ups, a feature not currently supported by PowerShell. Ironically, some IT system administrators have used VBScript as a workaround to execute PowerShell scripts, but this is not a viable long-term solution due to the fact VBScript is being deprecated. For further discussion on this topic, you can refer to this thread on X where industry experts discuss different options on how to overcome this issue.

Master Packager – detect VBS in MSI/MST​

When working with MSI files use Master Packager to open, create, and edit MSI/MST files. Starting with version 23.6.8717 Master Packager will detect if the MSI has VBScript Custom Actions. This functionality is supported in the Free Community Version.

When opening an MSI with Master Packager you will see red warning icon at top indicating that there is an VBScript Custom Action in the MSI/MST file.

Same warning icon is visible in the Custom Action Advanced Editor view.

We believe that a feature like this is a crucial functionality to be proactive and prevent issues going forward. If you use ORCA or InstEd to edit MSI files, then you will love working with Master Packager even more.

Master Packager – Run PowerShell script with MSI​

With Master Packager Professional you can run a PowerShell script within an MSI or MST file and it takes just a few clicks.

• PowerShell is executed silently without any Window flickers.
• PowerShell error logging is handled in the MSI log file
• PowerShell script is working during Intune and SCCM system context deployments

We have made sure that adding and running PowerShell scripts with Master Packager in MSI or MST is easy as possible. Here is how to add PowerShell in an MSI with a 6 simple clicks:

1. In Master Packager Advanced Editor got to Custom Actions

2. Choose Predefined Actions

3. Press Add New Predefined Action

   

4. Select Run PowerShell Script

5. Press Add

   

6. Browse PowerShell .PS1 file or Edit it in the software

   

VBScript-Remediation by Dan Gough​

To understand which of your current MSI/MST files has VBScript Custom Actions or .vbs files in the file table you want to check out these VBScript-Remediation script created by awesome Dan Gough. This comes very handy to validate multiple MSI and MST files.

It is available for free under MIT license.

Suggestions from Microsoft​

Microsoft posted a blog post about VBScript deprecation detection strategies. In this blog posts Microsoft suggest to use Sysmon to monitor VBScript usage, review VBScript dependencies in Group Policy, Scan for .vbs files across the system and Scan custom MSI packages for embedded VBScript.

Conclusion​

VBScript is a feature that is being deprecated due to security reasons and starting with Windows 11 23H2 is available as Feature On Demand. It is unknown when it will be removed completely therefore it is smart to prepare organizations and the software that use this previously widely used solution and replace it with other tools. It comes in handy to know tools like Master Packager that can help organizations and software developers to understand where VBScript is currently used.

For the first time ever, the Master Packager Team joined the Modern Endpoint Management Summit 2025 (MEM Summit 2025) in Paris, France. This was an amazing event to meet our existing customers and partners, and to show others how we can help with application packaging and management.

The attendees were fantastic. We met people from all around the world with diverse expertise and a shared eagerness to learn more.

We participated as a Silver Sponsor, which gave us the opportunity to set up a booth and share our knowledge and tooling during one of the sessions.

In our session, we talked about why application packaging is so important, and how organizations can package any application like a Master Packager.

At our booth, we answered questions about our products and application packaging. As a goodie item, we brought our “I am Master Packager” mouse mat, which makes packaging a bit more comfortable and more beautiful.

The hotel where the event took place had an amazing sky bar with an incredible view of Paris.

You can meet us in person and grab your own “I am Master Packager” mouse mat at Workplace Ninjas UK 2025 on 16-17 June 2025, and at AppManagEvent 2025 on 10 October 2025.

We love talking about application packaging and helping you become a Master Packager.

We hope to see you in person at one of the upcoming events.

The Master Packager Team

Automatically updating software sounds like a standard functionality that software should have, right? But that is not the case in the overwhelming majority of Windows applications. Why is that, and how did we just fix that?

We’ve seen more than 10,000 applications with their flows and advantages when it comes to auto-update. This month, we implemented auto-update mechanism for our applications. That led us to the conclusion that the main reasons we don’t see solid auto-updating mechanisms boil down to three factors: lack of knowledge, complicated systems, and expensive solutions. Today, we make available our solution that will focus on solving all three of these problems for software vendors.

1. Lack of knowledge​

To create an installer that auto-updates, developers must understand key aspects of the Windows operating system. The solution must be secure and user-friendly. Home users will install software on their own. IT pros will use the installer to update thousands of endpoints in their organizations. You must understand not only the Windows OS but also consumer needs and requirements. Most software vendors mainly think about home users and often exclude organizations. Organizations may want to install their app for thousands of users at once via deployment solutions like Microsoft Intune, where IT Pros may want an easy way to disable the updates. Or leave it enabled if the auto-update functionality is very good. That would depend on the application type (business-critical or not), but we see many organizations leave auto-updates enabled for Google Chrome. That’s because the auto-update mechanism is so good. We want to make an alternative solution and make it available for everyone.

2. Complicated systems​

Even when you have the knowledge, it is still complicated to develop such functionality internally. The system needs to cover all security issues, be flawless for users, be integrated into the installer, check running processes, and so on. For most organizations and developers, that will be too time-consuming and expensive. It is just easier to say: “Go to our website and download a newer** version from there”.

3. Expensive solutions​

Learning, building, and maintaining such a system takes time, and time is money. With money, you can buy ready-made solutions, but from what we have learned, even paid solutions have one or all three of these problems, which translate into an expensive solution.

How we solve these problems?​

We used our over a decade of experience seeing how others have built their applications and created auto-update functionality for our own applications. We follow the principle: build for ourselves, and then once we have solved our own problems, we make the solution available for others. This is that day.

Auto-updates should happen seamlessly. The best experience is when you launch the application and it is already updated without you ever noticing anything. That is exactly how Master Packager Dev Auto-Update functionality can work - in the background.

I say can, because you can of course disable it. We know that there are types of applications, organizations and users who want to control what updates and when. That is why it is possible to disable auto-update functionality completely or leave only notifications about an available update so that the user can trigger the update manually.

Master Packager Dev auto-update is built using a Windows service that can update the per-machine MSI even for limited users, similarly to how Google Chrome updates work. You need admin rights just during the first app installation, and then you can forget about updating it ever again.

It takes only 18 lines of JSON to put auto-update functionality in place in your solution. All with the most basic information that every developer will know.

    "updater": {
      "serviceName": "MasterPackager.Updater",
      "serviceDisplayName": "Master Packager Updater",
      "latestVersionDescriptor": {
        "url": "https://www.masterpackager.com/api/latest-version/mp",
        "installerUrlMatcher": "(?<=\"URL\":\")[^\"]+",
        "versionMatcher": "(?<=\"Version\":\")[^\"]+",
        "checkSumMatcher": "(?<=\"SHA256\":\")[^\"]+"
      },
      "scheduling": {
        "enabled": false
      },
      "notifications": {
        "enabled": true,
        "triggers": [
	        "MasterPackager",
	        "MasterRepackager",
	        "MasterWrapper",
	        "MasterPackager.Toolbox" ]
      }
    }

• serviceName - Name of your update service.
• serviceDisplayName - Display name of your update service.
• latestVersionDescriptor - Describes retrieval and parsing of the latest available version metadata.
• url - URL for the GET API that returns a simple response (JSON, XML, plain text, etc.) indicating where to download and how to validate the latest version of the application. Must be an HTTPS URL.
• installerUrlMatcher - RegEx pattern to read the URL from which to download the latest installer file.
• versionMatcher - RegEx pattern to read the latest version that will be compared with the currently installed version.
• checkSumMatcher - RegEx pattern to read the SHA256 checksum that will be compared with the checksum of the downloaded file.
• scheduling - Enable or disable silent automatic updates that happen in the background while the app is not running.
• notifications - Enable or disable update notifications for the application which show up when specified processes are running.
• triggers - Application process names that trigger an update notification upon application launch.

Notification when launching the app and there is a newer version available.

Installation progress bar.

Close conflicting processes view.

Updates finished successfully.

We currently support auto-update only for MSI packages and you must use Master Packager Dev to implement auto-update functionality flawlessly. The updater and the newer version must be signed with the same code signing certificate. Microsoft Trusted Signing is the recommended solution for signing your files.

Master Packager Dev and the auto-update feature are FREE if you use the application as a non-commercial product.

299 EUR/yearly for small and medium organizations.

999 EUR/yearly for larger enterprises.

Per organization.

For unlimited users and machines.

It is the most affordable solution out there. No paid solution is even close to the features and prices we offer. But what about open-source solutions, they are free, aren’t they? No, they are not. To see if open-source is free or not, check the option for a consultancy package or the huge list of complicated documentation. However, we will help you build the best installer for free.

Our mission is to make application management easy and affordable. Auto-update is built to solve a large part of why application management is so complicated and expensive. If you want to make creating Windows application installations easier for you and the installing experience better for your users, consider choosing Master Packager Dev.

• Download Master Packagers:

  https://www.masterpackager.com/download/master-packager-dev

• Documentation:

  https://www.masterpackager.com/support-master-packager-dev/documentation

If you need help, let us know and we will help you build installers for your apps: info@masterpackager.com

Application packaging shouldn’t be hard and expensive.

The Master Packager Team

Build Windows application packages that end-users love, enterprises want, and the Windows OS needs. We’re here to help you become a Master Packager.

1. Master Wrapper now supports the latest version of PSADT - 4.0.4. Master Wrapper is the best way to wrap your packages in PSAppDeployToolkit. No need to read the documentation. No need for extensive training of your beginner teammates. No need to check for typos. If you want to significantly improve your packaging speed and quality, look at Master Wrapper.

   

2. Master Wrapper now shows recently opened projects. You can also open a project by right-clicking the main PSADT AppDeployToolkit PS1 file.

   

3. With Master Wrapper and PSADT V4 now you can also set to remove MSI using Product Name as an upgrade action. Before, we only supported it for PSADT V3.

   

   

4. Improved support for .MSP files. If you package app .MSP files into PSADT, you can now right-click the .MSP file to load general info and install command-line details automatically.

5. Now when saving a PSADT project from Master Wrapper, we’ll notify you if the destination folder is not empty. This is particularly useful for predefined locations, such as the user’s desktop or document folder, where saving PSADT with many files could cause issues.

6. We’ve made built-in snippets available from the script editor for Master Wrapper community license users.

   

   

7. Proper repackaging should be done on a clean Virtual Machine, but not everyone knows that. Now, users launching Master Repackager on a physical PC will be informed of this best practice.

   

8. Automated upgrade table updates. Packagers often copy a previous package MSI to use as a template for a newer version and then increase the MSI version. We now detect this and automatically update the upgrade table references. It’s a small change, but it saves a lot of time in the long run.

We’ve improved many other features in Master Packager and fixed all known bugs.

Many of these improvements were prioritized and added because our users told us what they were missing. Join the Master Packager community and become a Master Packager faster.

See the full release notes here

Download Master Packager here

Here is a new version of Master Packager 24.9.9112 so that you can build Windows application packages that end-users love, enterprises want, and the Windows OS needs. We’re here to help you become Master Packager faster.

What’s new?​

1. PSAppDeployToolkit (PSADT) V4 support​

Now you can create and edit PSADT V4 projects effortlessly without learning new function names and risking having typos. All handled by Master Wrapper – the UI for PSADT.

This support also includes:

• Saving templates as PSADT V4
• Having ability to convert PSADT V4 packages with right click context menu to .intunewin files
• Use Master Wrapper created PSADT V4 packages with Master Packager Toolbox for fast upload to Intune
• We left PSADT V3 support, but going forward all new improvements will be focused on PSADT V4.
• Option to select default template for PSADT- V3 or V4

Learn all about new PSAppDeplyToolkit V4 and watch Master Wrapper wrapping in it here.

2. Sign PSAppDeployToolkit wrappers with your digital signature​

It is important to sign your scripts with a digital signature as an extra layer of security. Organizations that have PowerShell execution policy set to all-signed means that PSADT packages must be signed.

Now, Master Wrapper can easily help sign all unsigned PSADT scripts.

We support following signing methods:

• Azure Trusted Signing
• Certificate thumbprint
• Certificate (.pfx;p12)

The nice part is that if you use code signing certificate with Master Packager or Master Repackager then the same code singing certificate will appear in Master Wrapper.

3. IntelliSense for editing PSADT projects in Master Wrapper Community version​

With this version we have enabled IntelliSense for the Master Wrapper free Community version. This is amazing feature that will:

• Reduce learning curve: It allows users to quickly find the new PSADT v4 functions and their new parameters without reading the documentation.
• Increase productivity: IntelliSense provides code suggestions and auto-completions, which can speed up the wrapping process.
• Cut down on errors: IntelliSense helps prevent typos and syntax mistakes.
• Remove the need for any third-part software: like Visual Studio Code and save time as you will need only one software to build PSADT wrappers.

4. Upload to Intune improvements​

We have designed the best packaging flow for Intune – Wrap your package in PSADT with Master Wrapper where it will collect all the details required for Intune. Then use Master Packager Toolbox to convert package into .intunewin file and with one click upload to Intune.

With this version we added following details you can specify during packaging phase for smoother packaging and deployment process:

• Added information URL option and automatically fill it when loading data from MSI packages in Master Wrapper General page.
• Added option to specify device restart behavior option for Intune when uploading from Master Packager Toolbox.

5. New feature: Auto-Upgrade Configuration for MSIs​

One of the top questions we hear from IT Pros is how to properly set up MSI upgrade functionality. You must know that new MSI needs to have a different Product and Package codes, but the same at Upgrade code as previous MSI.

Now with the Master Packager Auto-Upgrade Configurator creating upgrades for previous versions is as easy as browsing previous MSI file, pressing the Fix All and Add & Update buttons. That’s it. You also get to learn what exactly is needed for MSI to upgrade previous versions.

6. Fixed all reported and found issues​

As always, we fixed every single reported bug. If you see any issues or have idea for improvements, we want to hear it: www.masterpackager.com/feedback

🗒️Read full release notes here:

https://www.masterpackager.com/support/release-notes

⬇️ Download Master Packager here:

https://www.masterpackager.com/download

Master Packager 24.8.9063 is out 🎉

We’re releasing a new version of Master Packager so that You can build Windows application packages that end-users love, enterprises want, and the Windows OS needs.

What’s new?​

1. Added support for modern code signing​

Master Packager and Master Repackager now support Trusted Signing and HSM signing.

2. Improved packaging for Intune​

Now when wrapping packages into PSAppDeployToolkit (PSADT) with the Master Wrapper and uploading them to Intune using the Master Packager Toolbox Intune feature we support following properties:

• Notes
• Developer
• Category
• Detection script

3. Fixed all reported bugs​

As always, we fix all reported and found bugs. You shouldn’t have anything stopping you from becoming a Master Packager.

Try out Master Packager and become a Master Packager that saves time and money.

Full release notes

Download Master Packager

The Master Packager Team

Two weeks ago, we were at AppManagEvent 2024, and it was filled with positive energy and technical insights.

It was so rewarding to meet face-to-face with Master Packager customers who have been relying on our software for years, as well as with those new to Master Packager. Showing them how we can help fuels us and keeps us motivated to build more and better solutions.

I really enjoyed sharing the lessons I took away from so many great discussions with application packagers. These conversations help us work on behalf of the people we serve and drive our mission—making application management easy and affordable.

Watch full session on YouTube.

Embedded content

A huge thank you to Coert Bosker and the team for organizing such a fantastic event where we can geek out on all things app management, with the shared goal of helping each other improve.

We’ll be back at AppManagEvent 2025, and we hope to see you all there too!

Master Packager 24.7.9021 is out 🎉

We’re releasing a new version of Master Packager so that You can build Windows application packages that end-users love, enterprises want, and the Windows OS needs.

What’s new?​

1. Master Wrapper PSADT templates​

Now you can create templates in Master Wrapper with your standard PSAppDeployToolkit configuration.

• Add, create, save, and update PSADT wrappers as templates.
• Enables service providers packaging for multiple third parties to choose and apply PSADT templates quickly.

2. Right-click → Wrap with Master Wrapper​

Previously you had to open the Master Wrapper app to start wrapping in PSADT. Now you can right-click on MSI/MST or EXE to start the wrapping process more conveniently.

Currently only supported from the legacy/classic context menu.

3. Load data from EXE installers​

When loading EXE to general information Master Wrapper will now read metadata from the EXE to fill out the main information for you - logo, name, version, publisher, and architecture. This will save some seconds and remove the boring part.

4. Create upgrade for previous applications with PSADT without reading the documentation​

It’s helpful when your package can upgrade previous applications making sure there will be no conflicts during deployment. To standardize the upgrade process and enable beginner packagers to become Master Packager faster we’re introducing the Master Packager Upgrade feature.

• Remove previous version of MSI and EXE with PSADT without reading the documentation.
• Load previous version MSI to fill out upgrade data
• Lower typo and issues rate when creating upgrade
• Standardize your package upgrade functionality
• Simply be more efficient when handling previous app removal so users can upgrade to the latest app version

5. Fixed all reported bugs​

As always, we fix all reported bugs as well we try to prioritize your suggestions.

Read all release notes here:

https://www.masterpackager.com/support/release-notes

Download Master Packager here:

https://masterpackager.com/download

Have an easy package. Or hard, because you are Master Packager. :)

The Master Packager Team 🧙‍♂️

In this blog post we will show following:

• How to find drivers
• What you will need to install drivers:
  • Driver files
  • DPInst.exe to install drivers (It usually can be found in Windows ADK or next to driver files)
  • Certificates – In cases where a window is shown with the option to always trust the publisher you will need to add a certificate. The easiest way to find them is using regedit, but there are other options too.
    • Path to Trusted Publisher certificates: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SystemCertificates\TrustedPublisher\Certificates
• How to create Custom Actions for Installing Drivers using Master Packager
• How to create Template for future use

How to find DPInst.exe and drivers​

To locate DPInst.exe:​

1. Open Process Monitor. Stop the capture and clear data.

2. Run installation

3. When DPInst.exe install windows appears, start the capturing process and when it finishes stop the process

4. Add a filter – Set the Category to write. Add it and click apply

5. Search for a process with a name like DPInst*.exe, right click and select “Jump to”

   

Note that the name of the executable can be slightly different. E.g.

DPINST.EXE, dpinst.x64.exe, dpinst-amd64.exe, dpinst-x86.exe,

DPInst32.exe etc.

Copy DPInst.exe to a new folder.

To locate driver files and registries:​

1. On clean VM open Master Repackager

2. Create first snapshot

   

3. Run DPInst.exe

4. After installation create second snapshot

   

   

5. In the files section under DriverStore locate driver files and copy them to the same folder where you copied DPInst.exe

   

6. Locate Trusted Publisher certificates in the registries section

   

7. Open them in RegEdit

   

8. Export the registries

Add drivers to MSI​

1. Open MSI with Master Packager
2. In General Information add application name, version, vendor, ect.
3. Go to the Files section. Create a new folder under [ProgramFilesFolder]\vendors_folder and place the drivers in it
4. Drag and drop located files and DPInst.exe exe into the folder and build a Cab file

Add Trusted Publishers certificates​

In Advanced Editor locate Registries section – drag and drop previously exported registries.

Create Custom Actions​

Go to Custom Actions.

Installation Custom Action:​

1. Create a new Custom action called CA_Install_Drivers.

2. Choose type Exe in File table

3. As Execution Options select Deferred System

4. Return Processing – Synchronous, ignore exit code – this will indicate that at installation process it would ignore exit code

5. Scheduling Options set for Always

6. Select DPInst.exe file

7. In command line section add this line: /Q /F /LM /SA

   

Uninstall Custom Action:​

1. Create a new Custom Action called CA_Uninstall_Driver

2. Choose type Exe in File table

3. As Execution Options select Deferred System

4. Return Processing – Synchronous, ignore exit code

5. Scheduling Options set for Always

6. Select DPInst.exe.exe file

7. In the command line section add this line: /u [#driverkey.inf] /d - replace file key for each driver file that you need to uninstall later. File keys can be found under File table. The file key is the first column of the file table called File.

   

Pro tip!

To create Uninstall Custom Actions faster for each driver, open Table editor:

1. Copy CA_Uninstall_Driver row and paste (Ctrl+Shift+C and Ctrl+Shift+C to copy whole row) new Custom actions as many as drivers we have
2. For each driver that needs uninstall, change the command line’s driver key
3. To find driver file keys go to File table and click on sequence in descending order to see last added files

Add created Custom Actions in InstallExecuteSequence​

In advanced editor locate InstallExecuteSequence.

Add CA_Install_Drivers:​

1. Select Action Type - Custom Actions

2. Select Action Name – CA_Install_Drivers

3. Add Condition – During Installation

4. Set Sequence number – 6500. It must be somewhere between WriteRegistries and InstallFinalize actions

5. Add Custom Action to the Install Execute Sequence list.

   

Add each CA_Uninstall_Driver:​

1. Select Action Type - Custom Actions

2. Select Action Name – CA_Uninstall_Driver

3. Add Condition – During Uninstallation

4. Set Sequence number – 3450. It must be somewhere before RemoveFiles and InstallFinalize actions

5. Add it to the Install Execute Sequence list

6. Repeat it to for each uninstall custom action

   

How to Create a Template for Future Use in Master Packager​

1. Open MSI and go to the Custom Actions table
2. Select CA_Install_Drivers and CA_Uninstall_Driver rows
3. Right-click on one of the selected rows and press the “Add to Template” button
4. Create a new template name and press the arrow button in the left textbox

Add pre-existing template to your Master Packager​

To add a pre-existing template, locate the Master Packager folder in your User Profile’s %appdata% directory.

You can find your templates in there.

Note! The Template folder will only appear after you create a template in Master Packager.

Summary​

Manually installing drivers for each user is time-consuming and inefficient. To install drivers silently, you should use DPInst.exe, Custom Actions and you might need a certificate for some drivers. Using templates in Master Packager allows you to speed up the process of adding custom actions to multiple MSI packages and reduce errors while creating them.

Template for Custom Action to Install Drivers

We will explain what the recommended properties are, how to apply them using Master Packager, and how to create a template for future use.

What are MSI Properties?​

Properties control how the MSI behaves during installation, modification, and uninstallation. These properties can define things like the product name, manufacturer, and installation behavior.

Types of Properties:

• Public Properties:
  • Must be in capital letters
  • Can be modified from the command line during installation
• Private Properties:
  • Typically, lowercase or mixed case
  • Cannot be changed from the command line

What Are the recommended properties?​

These properties should be set in every package to ensure a more successful deployment.

Here are the recommended properties:

ALLUSERS=1

Installs the application for all users on the system. Typically, deployments happen from the SYSTEM account and not setting ALLUSERS to 1 can install the MSI only to the SYSTEM account. The user will not see the shortcuts for the application as they will be in the SYSTEM user profile.

ARPNOMODIFY=1

Removes the “Change” option in the Add/Remove Programs list. This ensures that the user cannot go to Add/Remove programs and modify the installation configuration with the “Change” button.

ROOTDRIVE=C:\

Ensures the application installs on the C: drive. If not set the installer sets ROOTDRIVE to the local drive that can be written to and having the most free space.

LIMITUI=1

Does not display any windows installer dialogs during installation, uninstallation and repair. This ensures that even if an MSI is installed with a double click, then the installation will require no interaction with the user.

REBOOT=ReallySuppress

Prevents forced reboots after installation. If this property is not set, the installer can force a reboot. PSADT can be used to inform the user if a reboot is necessary.

MSIRESTARTMANAGERCONTROL=Disable

Disables interaction with Restart Manager to avoid interruptions during installation. This property will mean that processes with files in use will not be shut down. For example, shell extension DLL files can be used by explorer.exe and windows installer will kill explorer.exe if this property is not set.

When creating new MSI in Master Packager, Best Practice Properties are set by default.

More information about MSI properties: https://learn.microsoft.com/en-us/windows/win32/msi/property-reference

How to apply Best Practice Properties using Master Packager​

Applying these properties in Master Packager is simple. Here’s how you do it:

1. Open the MSI/MST file in Master Packager
2. Go to the Table Editor and open the Property table
3. Add missing Properties:

   • Right-click the Property table and select Add Row

   • Enter the property name and value

     

4. Edit an existing Property:
   • Find the property, double-click it, and update its value
5. Save the MSI/MST

Once you’ve made the necessary changes, save the MSI/MST file to apply the changes.

How to create a Template for future use in Master Packager​

1. Open MSI and go to the Property table
2. Select all Best Practice Property table rows – press ctrl and select properties
3. Right-click on one of the selected rows and press the “Add to Template” button
4. Create a new template name and press the arrow button in the left textbox
5. Press Add to add selected properties to the newly created template

How to apply Template​

1. Open MSI/MST you want to apply template to
2. In Advanced Editor go to Templates section
3. Select template and press “Apply Template”

Add pre-existing template to your Master Packager​

To add a pre-existing template, locate the Master Packager folder in your User Profile’s %appdata% directory.

You can find your templates in there.

Note! The Template folder will only appear after you create a template in Master Packager.

Summary​

Setting up best practice properties ensures MSI packages are successfully deployed. Using Master Packager’s templates allows you to apply these settings quickly across multiple packages, saving time and reducing the risk of errors.

Template for Recommended Properties

It has come to our attention that many packagers have experienced issues with packaging Arduino IDE 2 so it can be deployed in an enterprise environment. To help the application packaging community learn how we package these complex (read: poorly packaged by vendor) applications we documented a step-by-step guide.

We’re working on new self-paced courses and to test how good they are we gave to test it to our new intern Signe. She knew nothing about app packaging. All she had was course recordings, Master Packager Pro, our guidance and app to package. A hard one. Perhaps too hard. However, this is all you need. This is what we want to show. The next guide is created by Signe and proofread/checked by Toms and Edijs. Enjoy and become a Master Packager faster.

Application name: Arduino IDE 2.3.2

Link to Arduino IDE MSI installer: https://www.arduino.cc/en/software

Tools needed: Master Packager Pro (or any other repackaging software)

We are following our designed Master Packager Framework that helps to package any application in a fast and high-quality way.

What we will show in this guide:​

1. Evaluation process - Installing vendor MSI and monitoring installation process.
2. Summarizing problems - issues wrong with this application and its installer.
3. Packaging process - how to resolve these problems using Master Packager software.
4. Wrapping - how to create a PSAppDeployToolkit (PSADT) wrappers using Master Wrapper.
5. Testing - testing package using system account.

Evaluation​

1. Open a clean virtual machine
2. Open Master Packager Toolbox
3. Install the Arduino IDE MSI on the virtual machine
4. After installation, check what apps were installed and the location of the installed files by using Master Packager Toolbox
5. Open the application to verify if there is any configuration that should be included in our package

To see where the application is installed refresh Master Packager Toolbox by Right-Click -> Refresh or pressing F5. Everything that was installed will be marked green. Everything that will be uninstalled will be marked red. This is excellent when doing app evaluation and testing.

Click on the Arduino IDE app row to see more details about it.

Problems​

After evaluation of the installation, there are few problems that we encountered:

1. MSI creates desktop shortcut by default. The desktop is a user’s private space and in an enterprise deployment scenario desktop shortcuts should be removed.

2. MSI installs files in a per user location. Enterprises want per-machine apps. Main reasons are better security and ease of deployment when apps are per-machine.

3. Windows Defender Firewall displays two Windows Security Alerts when a user runs the application:

   • Arduino IDE
   • Mdns-discovery

4. App requires the installation of several drivers, which also needs admin rights.

   

5. During first launch the application downloads libraries.

In an enterprise environment users do not have admin rights. At least they shouldn’t.

As you saw from firewall exception and driver installation popups they point to a per-user location – application checks if the library files are present in “%localappdata%\arduino15” location.

Although the software is free to download it costs money. It costs time and money for every company in world to package it or better -> re-doing the installer with hacks and tricks as you will see next.

It’s clear that this application was created without considering enterprise requirements.

Packaging​

Now let’s resolve these problems one by one.

Removing Desktop shortcut​

Open the MSI using Master Packager and create a new Transform (MST) file. It is recommended to create MST file for every vendor MSI you want to package (modify) and deploy.

Under the shortcuts section, select desktop shortcut, right click on it and remove it.

Set MSI to install from per-user to per-machine location​

On the left upper corner click on table icon to open Table Editor and locate Property table.

Then change ALLUSERS = 2 to 1 and MSIINSTALLPERUSER = 1 to 0. This will configure that installation will happen under [ProgramFiles] folder for all users.

Improve MSI reliability​

Add a decade proven MSI properties that will improve MSI installation reliability.

Read about MSI reliability properties and how to apply them automatically for every package here: Improve MSI reliability with these MSI properties

Install drivers and include the libraries​

To install drivers, it is usually required to have:

• Imported driver certificates
• Dpinst.exe that will be used to silently install drivers
• INF driver files

Locate drivers and registries for importing driver certificates​

1. Install Arduino original MSI on a clean virtual machine but do not open the Arduino app itself.

2. Open Master Repackager and create first snapshot.

   

3. Now open Arduino application.

4. Install drivers and tick the checkbox to always trust publisher.

   

5. After all drivers are installed, in Master Repackager check the “I am done making system changes” and create a second snapshot.

   

   

6. In package cleanup phase click on “Manage Registries” and find registries under Trusted publishers.

   

   • Open them in RegEdit by right-click on the key name
   • Export all 4 registry key names under TrustedPublisher\Certificates.

7. Locate dpinst-amd64.exe file and right click on it and go to file location. Make a copy of the file as it will be required later. Tip: You can use filter search on top right corner to find any file or registry faster.

   

8. To find the installed drivers you will need to check the "C:\Windows\System32\DriverStore\FileRepository” folder.

   

9. Sort the folder by date modified and you should see 8 subfolders with inf in the name. Create a new folder called Drivers. Then go into each of the driver subfolders and copy its contents to the newly created Drivers folder. Copy dpinst-amd64.exe also in the Drivers folder. Your folder should look like this:

10. Create a new folder called Configuration and copy the Drivers folder inside it.

    

Include downloaded libraries​

11. The libraries must be present or Arduino will try to install the drivers again even if they are already installed. In the captured files of Master Repackager we can see that the application wrote to 4 per user locations:
    • “%AppData%\arduino-ide”
    • “%AppData%\Arduino IDE”
    • “%LocalAppData%\arduino15”
    • “%UserProfile%.arduinoIDE”

How can we know which files should be included in the package?

An easy way to do is to use elimination method. Rename one of the folders by adding “_backup” at the end of the folder name, then launch the app and check if the libraries are not downloaded again. Repeat this until the libraries start to install again when launching the app. This means that you have found which folder is required for the libraries to not install again. Using this method you can quickly find that only the “%LocalAppData%\arduino15” folder is required for the libraries to be installed.

12. The last step is to copy the “%LocalAppData%\arduino15” folder inside the Configuration folder that we created previously.

Install drivers with MSI/MST​

In the Master Packager Advanced Editor find Files section and right click the directory [ProgramFiles]\arduino-ide and select “Add Directory(s)” and browse for the Configuration folder and then press build now.

We will need to use predefined actions that will copy these files from the MSI to each user’s profile during system account installation that is used by most deployment systems.

To copy data to user profile we have created a predefined custom action called: “Copy to UserProfile”. It works amazingly. It copies files during system context installation to all user profiles. It also copies files to default profile so new user profiles can have the same configuration.

Under Custom Actions section, create a new Predefined action “Copy to UserProfile”. It will copy files to %localappdata% folder during the installation process.

Custom Actions → Edit → Predefined Actions → Add new Predefined Action → Copy to UserProfile

As source select arduino15 folder which was added under the configuration folder. As destination path set “AppData\Local”.

A custom action will also be added to remove these files from the default user profile during uninstallation.

Adding certificate registries​

For drivers to be installed silently we need to have the certificates imported to the Trusted Publishers store before driver installation.

In Advanced Editor locate Registries section → drag and drop previously exported registries.

Creating Custom action to install drivers​

1. Under Custom Actions → Edit → Custom actions Create new Custom action create new custom action called CA_Install_Drivers.
2. Choose type Exe in File table
3. As Execution Options select Deferred System
4. Return Processing – Synchronous, ignore exit code – this will indicate that at installation process it would ignore exit code
5. Scheduling Options set for Always
6. Select dpinst-amd64.exe that we added previously – dpinstamd64.exe
7. In command line section add this line: /Q /F /LM /SA

Custom Action should look like this:

After we need to add uninstall Custom Actions for each driver:

1. Create a new Custom Action called CA_Uninstall_Driver
2. Choose type Exe in File table
3. As Execution Options select Deferred System
4. Return Processing – Synchronous, ignore exit code
5. Scheduling Options set for Always
6. Select dpinst-amd64.exe file in the Drivers folder
7. In command line section add this line: /u “[#AdafruitCircutPlayground.inf]” /d /q

To create Uninstall Custom Actions faster for each driver, open Table editor.

Copy CA_Uninstall_Driver row and paste (Ctrl+Shift+C and Ctrl+Shift+C to copy whole row) new Custom actions as many as drivers we have and change the file key in the Target column for each corresponding INF file key.

To find file keys go to File table and click on sequence in descending order to see last added files. Or you can use filter in the top corner and type “.inf” to filter out all INF files.

Add created Driver Custom Actions in InstallExecuteSequence​

To run each created Custom Action in correct timing we need to add them in InstallExecuteSeqeuence table.

In advanced editor locate InstallExecuteSequence → Edit

First add CA_Install_Drivers:

1. Select Action Type - Custom Actions
2. Select Action Name – CA_Install_Drivers
3. Add Condition – During Installation
4. Set Sequence number – 6500
5. Add it to the Install Execute Sequence list

Then add each CA_Uninstall_Driver:

6. Select Action Type - Custom Actions
7. Select Action Name – CA_Uninstall_Driver
8. Add Condition – During Installation
9. Set Sequence number – 3450 (+1 for each uninstall custom action. The sequence number should not be the same for any other action)
10. Add it to the Install Execute Sequence list
11. Repeat it to for each uninstall custom action

Note! It’s important where each type of Custom Action is placed in the Install Execute Sequence list - CA_Install_Drivers should be place after WriteRegistries (otherwise the drivers will try to install before the certificates are installed) and CA_Uninstall_Driver before RemoveFiles action. Also, they should be placed before InstallFinalize Action.

Pro tip! This was a lot of work to install drivers. We don’t like a lot of work like that. After some time, it is hard to remember how to do it again or can introduce typo mistakes. Therefore you can create a template for driver installation using Master Packager Templates feature. Read more about how to do it here.

Firewall exceptions​

To create a firewall exception, add a new Predefined Action.

1. Open Control Panel → System and Security → Windows Defender Firewall and locate Advanced Settings

   

2. Under Inbound Rules is shown information about both needed Firewall Exceptions –for arduino ide.exe and mdns – discovery.exe

   

Arduino ide.exe firewall exception​

Under Custom Actions add new Predefined Action:

1. Select “Add Firewall Exception”

3. Set Exception name exact the same as it was by default - arduino ide.exe

4. Under Path select the exe file

5. Leave Bound, Profiles and Protocol with their default values

   

6. Set the same Exception Name also to Remove firewall exception.

   

Mdns-discovery firewall exception​

Create a second firewall exception for mdns-discovery using Predefined Actions.

1. Select “Add Firewall Exception”

2. Set Exception name exact the same as it was by default - mdns-discovery.exe

3. Under Path set location same as default to LocalAppData Folder:

   • [LocalAppDataFolder]arduino15\packages\builtin\tools\mdns-discovery\1.0.9\mdns-discovery.exe

4. Leave Bound, Profiles and Protocol with their default values.

   

5. Set the same Exception Name also to Remove firewall exception (1).

For this firewall exception to work, we need to set up few more things:

• Change install execute sequence condition to during repair for AddFirewallException and SetFirewallException

• Ensure that the MSI has an advertised shortcut, to trigger self-repair mechanism

  -Check for DISABLEADVERTISESHORTCUTS entry in property table. If it exists, remove it to enable advertised shortcuts.

• To activate the self-repair mechanism, create a new registry entry under HKEY_CURRENT_USER\Software

Change custom action condition to only be executed during repair for MP_AddFirewallException1 and MP_SetAddFirewallException1​

Because Mdns-discovery exe is in user data and system account installation cannot see that location for all users, we need apply this exception during repair.

1. In Advanced Editor go to Install Execute Sequence → Edit

2. Locate MP_AddFirewallException1 that we created for mdns-discovery

3. Change Condition to During repair

4. Do the same for MP_SetAddFirewallException1

   

Remove DISABLEADVERTISESHORTCUTS entry from property table​

1. In table editor locate property table
2. Select DISABLEADVERTISESHORTCUTS entry
3. Right click on it and delete it

Create a new registry entry under HKEY_CURRENT_USER\Software​

1. Under Register section in Advanced editor in HKEY_CURRENT_USER create a new HKCU registry Software[ProductName]. It will automatically create a corresponding component.

   

2. Open newly added registry in Table editor

3. Locate the corresponding component in Relationships → and double click on it

   

4. Set keypath to newly created registry key (in this case Reg_7 – Software[ProductName]) and set the Component Attributes to Registry KeyPath. This will enable Advertised Shortcut to activate MSI self-heal and register Firewall via Custom Action as in this situation Custom Action will be able to see user data path.

Wrapping​

After all the changes in the MST are done, it’s time to wrap this package into PSADT. Master Wrapper is the fastest and safest way to create a PSAppDeployToolkit (PSADT) wrappers.

1. Open Master Wrapper and create a new Project

2. Change General information about application by loading data from the MST or just dragging and dropping the MST file into the Master Wrapper.

3. In the Main actions, Master Wrapper auto-generates Install, Uninstall and Repair command lines

4. In Pre-actions section set all the information you want to show at installation. If you use MSI/MST then it also finds and sets all the processes to be closed for upgrade. In our case if Arduino IDE is open on user end it will ask to close the application using PSADT functionality.

5. At post-installation you can set request to restart if needed, set force restart after a certain period or you can show custom message that you want show to the user.

6. Next step – at the script editor we need to add two lines:

   • Copy-ContentToCache function:
     • Copy-ContentToCache
   • Remove-File function:

     • Remove-File -Path “$configToolkitCachePath$installName” -Recurse -ContinueOnError $true

       

Copy-ContentToCache function copies the toolkit files to a local cache folder. It’s necessary for the repair to work because Intune deletes the installation folder after the installation is complete.

Remove-File function will ensure that the cached folder is removed during uninstallation.

7. Save the package
8. After saving, Master wrapper will suggest opening the Files folder in newly created package. Drag and Drop created MSI, MST and cab file into it.

Testing installation​

To test if the application is packaged and wrapped correctly you need to do installation through system account. To do this, you need to use PsExec.

1. Open CMD as administrator
2. Add the command line and run the installation:

   • <path to PsExec>” /si “<path to Deploy-Application.exe>

     

Conclusion​

Arduino IDE 2.3.2 is not suitable for deployment in enterprise environments. This means that you need special skills to package it. Fortunately, we’re here to help you become a Master Packager. For Master Packager Pro customers this is not a problem as:

• They have Master Packager Pro software to handle any app
• Discord community to ask for help

Get Master Packager Pro

Self-paced courses are coming soon so you can package with confidence on your own. Subscribe to our newsletter to learn when they are available.

Have an easy package!

The Master Packager Team

For this release, our main goal was to enable you to become a Master Packager when writing custom PSAppDeployToolkit (#PSADT) scripts.

This version will help you:​

• Avoid the frustration of searching for scripts in old packages/notes
• Save time applying custom scripts
• Improve onboarding of new packagers
• Standardize your packaging process across the organization

We wanted to stop:​

• Spending time installing and opening third-party tools like Visual Studio Code to edit PSADT scripts.
• Searching for PSADT functions and examples in the documentation.
• Saving and copy/paste pre-made custom scripts from Sticky Notes.

This is how we made that happen:​

1. We integrated IntelliSense into the Master Wrapper Script Editor. A powerful tool that is available in Visual Studio Code.

2. Then we loaded AppDeployToolkitMain.ps1 and AppDeployToolkitExtensions.ps1 files.

3. After that, we created the Master Wrapper Script Explorer.

   Currently, it supports our built-in and custom snippets. It allows you to save parts of code and then easily access them from the script editor. This is a game changer for making application packaging efficient—everything is in one application.

Here is an example of how you can add your custom scripts to snippets and then load them from the Script editor.

IntelliSense and Script Explorer features are available to Pro license users. Help us help you become a Master Packager by purchasing the Pro license.

Next​

We’re working to solve one of the biggest packaging challenges: upgrading previous application versions. You’ll be able to create an upgrade with just a few clicks—no scripting, no Intune Supersedence. Everything will be standardized across your packaging team and organization.

Full release notes are here:

https://www.masterpackager.com/support/release-notes

Download Master Packager Community or purchase Master Packager Pro here:

https://www.masterpackager.com/download