Over the last twenty years, Advanced Installer has always kept up with the latest technology updates, evolving into a user-friendly and powerful authoring tool for Windows. We are proud to serve #ITProfessionals and #Developers from all over the world.
On our YouTube channel, you will find helpful tutorials, how-to’s, and guides about application packaging and deployment including #MSIX, MSI, App-V Packaging, #Repackaging - VM integration, App Virtualization, #VisualStudio Extension.
Subscribe to our newsletter and get unmatched support for #MSI and MSIX technology documentation, practical #guides, how-to's, and tips about the application packaging industry.
➡️www.advancedinstaller.com/newsletter-subscribe.htm…
✨New from Advanced Installer✨
MSI Packaging Training and Certification - the first free training and certification program in the application packaging industry.
Get trained and certified for FREE: www.advancedinstaller.com/hub/msi-packaging-academ…
Advanced Installer & PacKit
Adopting MSIX doesn't mean forcing every legacy application into a container it wasn't built for.
The secret to a successful migration isn't speed, it's triage.
Knowing upfront which apps will package cleanly, which need Package Support Framework (PSF) fixups, and which belong in a legacy pool saves months of wasted repackaging effort.
#MSIX #ApplicationPackaging #ITOps #SysAdmin #PackagingStrategy
5 hours ago | [YT] | 0
View 0 replies
Advanced Installer & PacKit
Your update configuration files and installer packages now have a home that is not your own web server.
Before Updater Cloud, publishing an application update meant hosting the configuration file and the installer package yourself, generating URLs manually, and keeping everything in sync.
We published a video walking through the full flow: creating the Updates Configuration project, uploading the config file and MSI or EXE in one click, connecting the hosted file to your MSI project, and enabling auto update. The installer download URL is filled in automatically after upload.
One tip from the video worth keeping: maintain two configuration files from the start, one for testing and one for production.
Watch it here:
1 day ago | [YT] | 0
View 0 replies
Advanced Installer & PacKit
Advanced Installer 24.0 introduces Updater Cloud, and you no longer need your own server to publish application updates.
Before 24.0, the update workflow required hosting both the updates configuration file and the installer package on your own infrastructure. Updater Cloud removes that entirely.
You create an Updates Configuration project in Advanced Installer, add a new update entry, configure the version and detection settings, then upload.
Advanced Installer handles both the configuration file and the MSI or EXE, fills in the installer download URL automatically, and your end users get the update pulled directly from Advanced Installer Cloud.
No server to configure. No hosting to maintain.
Full walkthrough by Renato Ivanescu: www.advancedinstaller.com/publish-app-updates-with…
#AdvancedInstaller #SoftwareUpdates #ApplicationPackaging
3 days ago | [YT] | 2
View 0 replies
Advanced Installer & PacKit
PowerShell 7.7 deprecating the MSI installer surprised many enterprise teams.
The packaging teams that navigate these changes smoothly won't be the ones doing a last-minute rip-and-replace. They're the ones adopting dual-build workflows now.
#ApplicationPackaging #SysAdmin #ITInfrastructure #MSIX
1 week ago | [YT] | 3
View 0 replies
Advanced Installer & PacKit
Advanced Installer 24.0 adds WinGet prerequisites support, available from the Enterprise Edition.
The built-in prerequisites library covers runtimes, frameworks, and Microsoft products well. But when your application depends on something outside that scope, another application rather than just a runtime, you were handling that on your own.
From 24.0, you search the WinGet repository directly from the Prerequisites page, pick what you need, and the install command lines are pulled automatically. No local file download needed. During installation, the wizard calls the WinGet repository and runs the install command directly. An internet connection is required at install time.
Full walkthrough by Radu Popescu: www.advancedinstaller.com/winget-prerequisites-in-…
#AdvancedInstaller #WinGet #ApplicationPackaging
1 week ago | [YT] | 0
View 0 replies
Advanced Installer & PacKit
Advanced Installer 24.0 lets you pull prerequisites directly from the WinGet catalog, and we just published a short video showing exactly how it works.
The built-in prerequisites library handles runtimes and frameworks well. But when your application depends on something like 7-Zip, Git, Node.js, Python, or VLC, you had to source those installers separately, keep them updated, and bundle them with your setup.
From 24.0, you search the WinGet catalog from inside Advanced Installer, add the package in a couple of clicks, and the install commands are populated automatically. No local file to ship. The wizard calls WinGet at install time and runs the command directly.
Watch it here:
1 week ago | [YT] | 0
View 0 replies
Advanced Installer & PacKit
If your MSIX package installs cleanly but crashes on launch, chances are it's an unhandled file write.
You don't need to rewrite legacy apps to fix it, you just need to see what they're trying to do.
#MSIX #PSF #ApplicationPackaging #SysAdmin
2 weeks ago | [YT] | 3
View 0 replies
Advanced Installer & PacKit
We published a video on the Open Package Manifest, now integrated in Advanced Installer 24.0.
When packaging and deployment are handled by different teams, deployment information ends up scattered across documents, emails, and spreadsheets. Install commands, detection rules, requirements, assignments - all manually compiled with no standard format.
OPM is a free, open-format XML file that keeps all of that in one place, inside the .packit folder right next to the installer.
From Advanced Installer 24.0, you launch PacKit directly from the tool, fill in your deployment settings through the GUI, and the manifest is generated automatically. Works with Intune, SCCM, and MECM.
2 weeks ago | [YT] | 1
View 0 replies
Advanced Installer & PacKit
Starting with Advanced Installer 24.0, PacKit is now integrated directly in the tool as your deployment hub.
In enterprise environments, packaging and deployment are usually handled by separate teams. The packager finishes the installer and then has to manually pull together install commands, detection rules, requirements, and assignments into a file to hand off. No standard format, no guaranteed consistency.
OPM (Open Package Manifest) is a free, open-format XML file that standardizes that handoff and lives in the .packit folder right next to your installer.
From Advanced Installer 24.0, you launch PacKit directly from Package Definition / Deployment, fill everything in through the GUI, and the OPM file is generated automatically.
Supports Intune, SCCM/MECM, PSADT, and WinGet.
Full walkthrough by Radu Popescu: www.advancedinstaller.com/open-package-manifest-in…
#AdvancedInstaller #EnterprisePackaging #Intune
2 weeks ago | [YT] | 0
View 0 replies
Advanced Installer & PacKit
What's new in Advanced Installer 24.0?
If you manage application packages and deployment pipelines, this update adds several tooling enhancements to streamline day-to-day packaging workflows:
🔹 AI Assistant integration to assist with troubleshooting and project configuration updates directly in-app
🔹 Native Open Package Manifest generation
🔹 WinGet integration to pull installer prerequisites directly
🔹 Cloud hosting for your updater configurations and installer binaries
🔹 GitHub and Microsoft account SSO sign-in options
We've also added a dedicated signing audit log to track signature operations (useful for monitoring costs on Trusted Signing or DigiCert), automatic project backups before overwriting .aip files, PowerShell custom action updates, and updated runtimes for .NET 8, 9, and 10.
What's new in Advanced Installer 24.0: www.advancedinstaller.com/what-is-new-version-24.0…
#SysAdmin #AppDeploy #MSIX
2 weeks ago | [YT] | 0
View 0 replies
Load more