Distributing classic Windows applications via Microsoft Intune is often more complex than it seems at first glance — especially when EXE installers, custom scripts, or proprietary setups are involved. Microsoft has developed a specialized tool for exactly these cases, which may not immediately catch everyone's eye, but offers enormous potential. In this article, we take a close look at a tool that has long since established itself as a standard for many IT administrators — and show you how to use it optimally.
The most important things in brief
- IntuneWinAppUtil is the official Microsoft toolto prepare classic Win32 applications for deployment via Intune (.intunewin format).
- The tool can be automated, is scriptable and can be integrated into CI/CD processes — ideal for larger IT environments.
- LOB apps may be easier to deploy, but offer significantly less flexibility than Win32 packages with detection rules, user-defined commands, and update functionality.
- Graphical interfaces and wrapper tools Like Win32ContentPrepToolGUI, it's easy to get started, but use the same logic as the official tool in the background.
1 What is IntuneWinAppUtil?
The IntuneWinAppUtil, officially “Microsoft Win32 Content Prep Tool”, is a command line tool from Microsoft, with which classic Win32 applications for use in Microsoft Intune can be prepared. The tool packages installation files (such as MSI, EXE, or batch files) in a specially encrypted .intunewin format. This file can then be uploaded to the Intune console and distributed.
Originally developed to close gaps in app deployment via Intune, IntuneWinAppUtil offers a way to provide even complex legacy apps or company-specific applications — regardless of whether they are installed via a classic installer or via a script.
Since its introduction, the tool has established itself as an indispensable tool for IT administrators using Windows applications in modern Endpoint Management Want to roll out centrally.
2 What is a.intunewin file?
An .intunewin file is a specially packaged format that Microsoft Intune uses to distribute classic Windows (Win32) applications. The Microsoft Win32 Content Prep Tool (IntuneWinAppUtil.exe) compresses and encrypts all installation files and metadata — such as recognition rules — in exactly this format. The resulting file contains everything necessary for Intune to reliably install and monitor the application.
An .intunewin file ensures that even complex installation packages — including multiple files and user-defined installation parameters — can be rolled out cleanly and reproducibly via Intune.
Why is that important? The alternative would be to provide an application as a so-called line-of-business app (LOB app) — a fast but also limited approach. LOB apps only support simple MSI installations without dependencies, user-defined commands or update logic. As soon as more control, flexibility or automation is required, Win32 packaging with .intunewin is the much more robust path.
3 Requirements for use
Before you can use IntuneWinAppUtil, a few basic requirements should be met — both on the technical side and in terms of the deployment strategy.
Technical requirements
- Operating system: Windows 10 or higher (it is recommended to use it on an admin PC)
- .NET Framework: .NET Framework 4.7.2 or newer must be installed
- File access: Full access to the source folder with the installation file
- Target directory: An empty folder to store the created.intunewin file
Further requirements
- Admin rights: Many installation packages and deployment via Intune require elevated rights.
- Microsoft Intune access: A valid Microsoft Intune subscription and admin rights in Azure Active Directory
Tip: Make sure that the source folder and files do not contain spaces or umlauts in the path — otherwise this often leads to conversion errors. These prerequisites lay the foundation for successfully integrating Win32 applications into Intune.
4 Installation and download
The IntuneWinAppUtil.exe tool is officially provided by Microsoft via GitHub and is not part of the standard Windows or Intune installation. It is a lightweight, portable tool that can be run directly without any setup.
download source
The latest version can be found at official GitHub repository from Microsoft.
After downloading the ZIP file, it is sufficient to unzip it. The application can then be used directly from the command prompt or powershell be launched.
GUI alternatives
If you don't want to use the tool via the command line, you can use alternative graphical interfaces, such as:
- Win32ContentPrepToolGUI
- IntuneWinAppUtil GUI wrapper
- Tools such as scConfigMgr or Advanced Installer
These GUIs offer a more user-friendly interface, especially for beginners, and help to avoid common input errors. Make sure to always use the latest version — older releases may cause compatibility issues with Intune.
5 Preparing the Win32 app: step-by-step instructions
Packaging an application with IntuneWinAppUtil is relatively simple, but requires detailed information about the installation file and its paths. Here are the typical steps:
1. Start tool
Navigate to the directory where IntuneWinAppUtil.exe is located using the command prompt (cmd.exe) or PowerShell. Start the tool with: IntuneWinAppUtil.exe
2. Answer the query
The tool queries the following parameters in order:
- Source folder: Directory in which the setup files are located
- Setup file: The name of the main installation file (for example, install.exe or setup.msi)
- Output folder: destination folder for the created .intunewin file
- Catalog folder: Optional — usually left empty
3. Sample call
Alternatively, you can call the entire command directly with parameters:
IntuneWinAppUtil.exe -c "C:\Install\7Zip" -s "7zSetup.exe" -o "C:\Output”
4. Check the result
After a successful run, you will receive a.intunewin file, which can now be uploaded to Intune.
Use a PowerShell script with dynamic path variables for repeated package creation — this saves a lot of time.
6 parameters and options at a glance
The IntuneWinAppUtil provides several command line parameters that make the packaging process more efficient and automatable. Here are the most important ones:
Example of automated packaging:
IntuneWinAppUtil.exe -c "C:\Installers\Notepad ++” -s "npp.exe" -o "C:\IntunePackages" -q
This command builds the Intune package in the background, without manual prompts. For extensive package deployments, it is worthwhile to use it in CI/CD environments with PowerShell and GitHub Actions.
7 Uploading and Assigning to Intune
Once the.intunewin file is created, you can upload it to the Intune admin console and assign it to devices or users.
Step-by-step upload to Intune
- Open Intune: Microsoft Intune Admin Center → Apps > All apps > Add
- Select app type: Select “Windows app (Win32)” as the type
- Upload app package: Upload the.intunewin file
- Enter app information: title, description, publisher, etc.
- Define installation commands: For example, install.exe /quiet, also optional uninstall or reset commands
- Make an assignment: Assigns the app to specific devices, groups, or users
- Set detection rules: Defines rules that Intune uses to recognize whether the app is already installed (possible options: file path, MSI recognition, registry value, script)
- Monitoring: Monitor installation status and potential errors in the Intune dashboard
For reusable installations, it is recommended to define user-defined requirements (e.g. registry keys or file paths) in the “Requirements” tab.
8 best practices and pitfalls
Even though IntuneWinAppUtil is fairly easy to use, there are some common sources of error and best practices that you should know:
Best Practices
- Use short file paths: Long or nested paths can result in packaging errors
- Test the installation command: Run locally on a test device beforehand to avoid errors
- Consistent folder structure: collect all setup files in a dedicated directory
- Package versioning: Clearly name package names and output paths (e.g. “appname_v1.0.intunewin”)
Common pitfalls
- Spaces and special characters in the file path → often leads to “File not found” errors
- Wrong path to the setup file → the tool does not recognize the file or aborts
- Missing admin rights when running → may result in incomplete packages
- Outdated tool version → incompatible with current Intune features
- Package size not suitable: max. 30 GB per Win32 app
Uses a dedicated packaging script with logging functionality to reproducibly build packages and log errors.
9 Conclusion and recommendations
The IntuneWinAppUtil is the way officially provided by Microsoft to prepare classic Win32 applications for deployment via Microsoft Intune. It converts installation packages into the required.intunewin format and thus forms the technical basis for deploying complex applications as part of modern endpoint management.
Thanks to its command line structure, the tool can be efficiently integrated into automation processes — for example via PowerShell, GitHub Actions or Azure DevOps. For more convenient operation, there are supplementary graphical front ends and commercial tools that work towards the same target format, but usually also use the packaging process defined by Microsoft internally.
Anyone who uses IntuneWinAppUtil strategically benefits from reproducible packaging, clearly structured deployments and a high level of flexibility — especially for complex or company-specific setups. In short, the tool is part of the basic equipment for any Intune owner who wants to manage more than just simple standard packages.
Since 2011, Thore has focused exclusively on endpoint management and endpoint security topics. Initially focused on software packaging and software distribution with Microsoft MECM/SCCM and Ivanti DSM, he is now a sought-after interlocutor when it comes to unified endpoint management, system hardening, patch management and endpoint protection. The focus is in particular on the Microsoft technologies Intune, Configuration Manager, Entra and Defender. Thore is co-founder of the “Endpoint Management” expert group at IAMCP e.V.
Jahre Erfarung
Verwaltete Endgeräte
