Package and Deploy a Win32 App with Microsoft Intune

This walkthrough packages one approved Windows installer, adds it as an Intune Win32 app, and deploys it to a small device pilot. The installer must support a silent, unattended installation; interactive prompts are not supported by Intune’s Win32 app deployment.

Use an approved installer and a test device

Use software your organization is authorized to deploy. Test the vendor’s silent install and uninstall commands on a disposable or approved pilot device before uploading the package. Assign the app only to a pilot group until its detection and uninstall behavior are confirmed.

Prerequisites and app context

Devices must run a supported Windows edition, be enrolled in Intune, and have a supported Microsoft Entra join or registration state. Windows S mode is not supported by the Intune Management Extension. A Win32 app package is limited to 30 GB. Choose device/system or user context to match the installer’s design; a user-targeted install that needs administrator rights can fail for a standard user.

01

Prepare and Test the Installer

Preflight

Obtain the approved installer and its vendor documentation. Put only the app’s setup files and required dependencies in a dedicated source folder; keep the Microsoft Win32 Content Prep Tool and output folder elsewhere. On a test device, run and validate the vendor’s silent installation, uninstall, and detection method before packaging. Record the expected product code or installed file and version.

Source folder: C:\Intune\Source\ContosoApp
Installer file: ContosoApp.msi (example name)
Vendor silent install tested:
Vendor uninstall tested:
Detection method identified:
Pilot Windows device enrolled and checking in:

❯ Illustrative Output (Results Vary)

The installer completes without dialogs, and its installed state can be detected reliably.

---

02

Create the .intunewin Package

Packaging

Download the latest Microsoft Win32 Content Prep Tool from Microsoft’s linked GitHub repository and extract it outside the source folder. Run the tool with the source directory, setup file, and a separate output directory. The tool packages all files and subfolders in the source folder, so remove unrelated files before running it.

.\IntuneWinAppUtil.exe -c "C:\Intune\Source\ContosoApp" -s "ContosoApp.msi" -o "C:\Intune\Output"

❯ Illustrative Output (Results Vary)

C:\Intune\Output\ContosoApp.intunewin

Use the vendor’s exact installer switches

The command lines in the next step are common MSI examples. Replace them with the vendor-documented switches and product code for the actual app. Do not assume that an EXE installer uses MSI options.

---

03

Create the Windows Win32 App in Intune

App Setup

In the Microsoft Intune admin center, open Apps > All Apps > Create. Choose the Windows platform and Windows app (Win32), then select the generated .intunewin file. Add the app name, publisher, description, and other required metadata so administrators can identify the package and its owner.

App type: Windows app (Win32)
Package: C:\Intune\Output\ContosoApp.intunewin
Name and publisher: match the approved software record
Owner and support details: documented for the service desk

❯ Illustrative Output (Results Vary)

The Intune app wizard accepts the package and opens the app configuration steps.

---

04

Configure Program, Requirements, and Detection

Install Rules

On the Program page, enter the tested install and uninstall commands. For an MSI, common templates are msiexec.exe /i “ContosoApp.msi” /qn /norestart and msiexec.exe /x PRODUCT-CODE-GUID /qn /norestart; replace the example product code with the actual MSI product code and follow the vendor instructions. Select the installation behavior that matches the installer. On Requirements, set the supported architecture and minimum OS. On Detection rules, use the MSI product code or a reliable file, registry, or script rule so Intune can distinguish installed from missing.

Install command: tested vendor silent command
Uninstall command: tested vendor command and actual product identifier
Install behavior: System for machine-wide/admin install; User only when supported
Requirements: architecture and minimum OS verified
Detection: reliably matches the installed app and version

❯ Illustrative Output (Results Vary)

The app configuration describes a silent install, a working uninstall, and a testable detection state.

Do not target an admin-required install to a standard user’s context

Select System context for a machine-wide installer that needs elevated rights, then target a pilot device group. Use User context only when the vendor supports a per-user installation that succeeds without elevation.

---

05

Assign the App to a Small Device Pilot

Pilot Assignment

Finish the wizard, then assign the app as Required to an approved pilot device group. Review the included and excluded groups before saving. Avoid mixing Win32 and line-of-business MSI deployments during classic Windows Autopilot enrollment; Microsoft documents a possible Trusted Installer conflict in that scenario.

Assignment intent: Required for the approved pilot
Target: dedicated test-device group
Exclusions: production groups and unrelated devices
Autopilot enrollment: review app-type conflicts before deployment

❯ Illustrative Output (Results Vary)

Only the intended pilot devices receive the required app assignment.

---

06

Monitor Installation and Resolve Failures

Validation

Open Apps > All Apps, select the app, and review its device install status. Allow the device to check in; if needed, sync from Settings > Accounts > Access work or school > Info > Sync or Company Portal. For a failure, compare the Intune error with the installer result, detection rule, and logs under C:\ProgramData\Microsoft\IntuneManagementExtension\Logs, especially AppWorkload.log and IntuneManagementExtension.log.

Intune admin center > Apps > All Apps > select the app
Review: Device install status and per-device result
Client logs: AppWorkload.log and IntuneManagementExtension.log
Check: assignment, silent command, requirements, detection, and return code

❯ Illustrative Output (Results Vary)

Record install status and version on each pilot device before expanding the assignment.

Upstream references

See Microsoft’s Win32 app deployment guide, prepare Win32 app content, Intune Management Extension requirements and logs, and monitor app assignments.