<- Back to Intune

Intune

Build Win32 App Packages

Step-by-step notes for preparing source files, converting them into `.intunewin` packages, uploading them into Microsoft Intune, and validating deployments before rolling them out broadly.

Before You Start

  • Confirm you have the installer files and any required support files.
  • Know whether the app uses an `.exe`, `.msi`, `.bat`, or PowerShell installer.
  • Document the silent install and uninstall commands before packaging.
  • Verify what detection rule will prove the app installed successfully.

Step 1: Prepare the Source Folder

Create a clean working folder for the application package. Place the installer and any supporting files in that folder, such as transforms, scripts, configuration files, or helper executables. Keeping the folder clean helps avoid packaging the wrong files and makes troubleshooting easier later.

Step 2: Use the Win32 Content Prep Tool

Run the Microsoft Win32 Content Prep Tool against the source folder. Point the tool to the folder containing the installer, select the setup file, and choose an output location. The tool will generate an `.intunewin` file that Intune can ingest.

Keep the output package in a predictable location, especially if you plan to revise the app later. Consistent naming helps when you build replacement packages or compare older versions.

Step 3: Add the App to Intune

In the Intune admin center, go to Apps, then Windows, and choose to add a new app. Select Windows app (Win32), then upload the `.intunewin` package you created.

Step 4: Configure Program Information

Enter the install and uninstall commands exactly as they should run on the endpoint. This is one of the most important parts of the package because even a valid upload will fail if the command line is incorrect or missing required switches.

Good items to document here:

  • The exact silent install command used.
  • The uninstall command and whether it is vendor supported.
  • Whether the app installs in system context or user context.
  • Any restart behavior that the app may trigger.

Step 5: Build Detection Rules

Detection rules tell Intune how to confirm the application is installed. Use a method that is reliable in your environment, such as an MSI product code, registry value, file path, or executable version. Weak detection logic can make successful installs appear failed or cause repeated reinstall attempts.

Step 6: Assign and Test

Assign the app to a small pilot group first. Confirm that the app installs successfully, appears correctly in Company Portal if applicable, and reports the expected status in Intune. This is the best time to catch issues with packaging, detection, or command syntax before expanding deployment.

Step 7: Review Troubleshooting Clues

If the deployment fails, review the install command, detection rule, and whether the installer works manually in the same context. Also check Intune Management Extension logs on the client and verify the package did not miss supporting files during the prep step.