Win32 app deployment in Intune has a reputation problem. Not because the deployment side is hard — it isn't. The pain lives upstream, in the packaging step. Hunt for the silent switch. Write a PowerShell wrapper. Spin up a sandbox VM. Run the Microsoft Win32 Content Prep Tool from the command line. Test. Fail. Debug. Repeat.
If that loop sounds familiar, this guide is for you. Here's the full workflow for converting any EXE installer into a deployment-ready .intunewin package in 2026 — no scripts, no VM, no packaging expertise required.
Why Win32 App Packaging Is Still a Manual Grind
Intune handles modern app deployment well when you're working with MSIs or MSIX packages. The moment a legacy EXE enters the picture, the process gets messy fast.
The core problem: Intune's Win32 app deployment requires a .intunewin file, a silent install command, an uninstall string, and a detection rule. None of those come with the EXE. You have to find or build every piece yourself.
The Microsoft Win32 Content Prep Tool wraps your files into a .intunewin package, but that's all it does. It doesn't detect the installer framework. It doesn't extract silent arguments. It doesn't generate detection GUIDs. You still have to figure out whether you're dealing with an Inno Setup, NSIS, or InstallShield installer — and then find the right flags for each.
For a single app, that's maybe 30–45 minutes of work. Multiply that across 20 or 40 apps during a migration and you've lost days.
What You Actually Need to Deploy a Win32 App in Intune
Before you can add a Win32 app in Intune, you need four things:
- A
.intunewinfile — the packaged app, wrapped using the Content Prep format - A silent install command — the command string that runs the installer without any UI prompts
- An uninstall string — so Intune can remove the app cleanly
- A detection rule — typically a registry key, file path, or MSI product code that tells Intune the app is installed
Getting all four from a raw EXE used to mean manual research, trial-and-error testing, and at least one failed deployment before you got it right.
The Zero-Script Approach: Upload, Convert, Deploy
InstallMage automates the entire packaging workflow in a single cloud pipeline. No local tools, no VM, no command line. Here's how the process works from start to finish.
Step 1: Upload Your EXE
Go to InstallMage and upload your raw EXE installer. The free tier supports files up to 250 MB and gives you 3 conversions per month — enough to test the workflow before committing to anything.
Your file runs in an isolated, stateless Linux container. It never touches persistent storage. The moment your package is ready, the EXE is permanently deleted. Nothing is retained.
Step 2: AI Scans and Identifies the Installer Framework
This is where the manual work disappears. InstallMage's AI engine inspects the EXE and identifies the installer framework automatically — Inno Setup, NSIS, InstallShield, and others. It then extracts the correct silent install arguments for that specific framework with zero configuration on your end.
No more cross-referencing documentation. No more /S vs /silent vs /SILENT guesswork. The AI handles it.
Step 3: Conversion and Testing
The engine compiles a WiX-based MSI wrapper and generates the .intunewin package. This step runs entirely in the cloud — no sandbox VM required on your end.
Pro-tier accounts can also supply a .pfx certificate for automatic code signing (BYOC), which matters if your environment enforces signed packages before deployment. Learn more in our code-signing guide.
Step 4: Download Your Deployment-Ready Package
You get back more than just a .intunewin file. InstallMage outputs:
- The
.intunewinpackage, ready to upload to Intune - A ready-to-paste install command string
- An uninstall string
- A detection rule GUID
That last part is the piece most tools skip. The gap between "here's your packaged file" and "here's everything you need to paste into Intune" is exactly where packaging workflows stall. InstallMage closes it.
The full pipeline — upload to download — completes in under 3 minutes.
How This Compares to the Manual Workflow
| Task | Manual approach | With InstallMage |
|---|---|---|
| Identify installer framework | Manual research or trial-and-error | AI detects automatically |
| Extract silent install switches | Search docs, test flags | Auto-extracted |
Create .intunewin package | Run Win32 Content Prep Tool locally | Generated in the cloud |
| Generate detection rule GUID | Create manually in Intune | Auto-generated and included |
| Write uninstall string | Research or reverse-engineer | Included in output |
| Total time per app | 30–90 minutes | Under 3 minutes |
The Microsoft Win32 Content Prep Tool is free and officially supported, but it only handles one step of the five listed above. If you're packaging more than a handful of apps, the time cost adds up fast.
What About the Microsoft Win32 Content Prep Tool?
The Content Prep Tool is the right answer if you already know your silent switches, already have your detection rule, and just need to wrap files into the .intunewin format. It's a CLI utility — functional, but narrow in scope.
If you're starting from a raw EXE with no packaging documentation, the Content Prep Tool leaves most of the work on your plate. InstallMage handles the steps the Content Prep Tool doesn't: framework detection, silent argument extraction, detection rule generation, and uninstall string output.
They solve different problems. If you only need a wrapper, the Content Prep Tool works. If you need the full Win32 app deployment package, you need more than a wrapper.
MSP and High-Volume Packaging
If you're an MSP managing 10 or more client environments, the per-app time cost compounds quickly. A new client onboarding with 30 legacy apps can mean 15–30 hours of packaging work at manual rates.
The MSP/Teams tier at $99/month includes priority VIP queueing, a 3 GB file size limit, and everything in the Pro tier. For shops billing hourly, the math on time saved versus subscription cost is straightforward. See the full pricing breakdown for details.
Security: What Happens to Your EXE?
This question comes up often, and reasonably so. You're uploading production software to a cloud service.
InstallMage processes every file in an isolated, stateless container. There's no shared infrastructure between jobs. The EXE is permanently deleted the moment your package is ready — no archiving, no logging of file contents, no retention of any kind. The pipeline is ephemeral by design.
Getting Started
The free tier at InstallMage gives you 3 conversions per month at no cost, no credit card required. It's enough to run your first EXE through the pipeline and see what comes out the other side.
Pro is $39/month for unlimited standard conversions, native .intunewin output, BYOC code signing, and the Intune Deployment Cheat Sheets. Annual billing takes 2 months off the price.
If you're mid-migration and staring down a backlog of legacy EXE installers, start with the free tier. Run one app through. The output speaks for itself.
FAQs
What installer frameworks does InstallMage support?
InstallMage's AI engine currently detects and handles Inno Setup, NSIS, and InstallShield, along with other common installer frameworks. The detection is automatic — you don't need to identify the framework yourself before uploading.
Do I need to install anything locally to use InstallMage?
No. The entire conversion pipeline runs in the cloud. You upload your EXE through the web app and download the finished package. No local tools, no VM, no command line required.
Is my EXE stored after conversion?
No. Each file is processed in an isolated, stateless container and permanently deleted immediately after your package is ready. There is no storage, archiving, or retention of any kind.
What does InstallMage output beyond the .intunewin file?
Along with the .intunewin package, you get a ready-to-paste install command, an uninstall string, and a detection rule GUID. Everything you need to configure the Win32 app in Intune is included in the output.
How is InstallMage different from the Microsoft Win32 Content Prep Tool?
The Microsoft Win32 Content Prep Tool wraps files into the .intunewin format but does not detect installer frameworks, extract silent switches, generate detection rules, or produce uninstall strings. InstallMage handles all of those steps automatically.
Can I use InstallMage for code-signed MSI packages?
Yes. Pro-tier accounts support BYOC (Bring Your Own Certificate) code signing. You upload a .pfx certificate and InstallMage automatically signs every generated MSI wrapper.
What does the MSP/Teams tier include that Pro doesn't?
The MSP/Teams tier ($99/month) adds priority VIP queueing for faster processing, a 3 GB file size limit (versus 1 GB on Pro), and is designed for high-volume environments managing multiple client deployments simultaneously.