fbpx
This site uses cookies to offer you a better browsing experience. Find out more on how we use cookies and how you can opt out. Accept
PACE Suite - Application Packaging & Virtualization Software
Request a trial Get a quote Become a partner
Request a demo of PACE Suite now We will get in touch with you right away to schedule a convenient time for your 1-on-1 demo with one of our experts.
I have read and agree to the Privacy Policy
Request a quote Please fill in this quick form and we will send you a free quote shortly.
License *
 Freelancer Enterprise Service Provider
I have read and agree to the Privacy Policy
Request a quote Please fill in this quick form and we will send you a free quote shortly.
License *
 Freelancer Enterprise Service Provider
I have read and agree to the Privacy Policy
Request a call Please fill in this quick form and we will call you back shortly.
I have read and agree to the Privacy Policy
Contact Support Please fill in this quick form to contact our support.
I have read and agree to the Privacy Policy
Subscribe to our Newsletter Be among the first to receive our updates! Fill in this quick form to join the list of subscribers.
Send an email to Tetiana Botanevych Please fill in this quick form to contact our expert directly.
I have read and agree to the Privacy Policy

Edit MSI packages (files, registry, shortcuts)

This time we demonstrate how to edit MSI packages but as the topic is broad we divided the guide into two parts. The first part deals with files, registry, and shortcuts.



If you edit MSI with PACE Suite, you can manage files, directories, permissions, registry entries & registry permissions, shortcuts, features/components structure, custom actions and other resources of your package. Also, you can create patches, package documentation, validate your package and publish it to SCCM.

Please note that if you’re editing a vendor MSI (produced by a software manufacturer), according to Windows Installer best practices, you should do it with a transform file. In case you’re editing your repackaged MSI or you are not afraid of losing vendor’s support, skip the step of creating a transform file.
Share this blog article: