IntuneWinAppUtil Package Win32 Apps Easily
IntuneWinAppUtil is the official Microsoft tool for preparing Windows application installation files for deployment through Microsoft Intune. Convert your EXE, MSI, or script files into the required .intunewin format.
What is IntuneWinAppUtil?
Learn about the tool that simplifies Windows application packaging for Microsoft Intune deployment
Streamline Application Deployment
IntuneWinAppUtil is a command-line tool provided by Microsoft that converts Windows application installation files into the .intunewin format required for deployment through Microsoft Intune.
This tool packages your application installer along with any necessary resources and creates a single file that can be uploaded to Intune for distribution to managed Windows devices.
Whether you’re deploying traditional desktop applications, modern UWP apps, or custom scripts, IntuneWinAppUtil ensures they’re properly formatted for Intune’s application management system.
key Features of IntuneWinAppUtil
Win32 App Packaging
IntuneWinAppUtil efficiently converts traditional installer formats like EXE or MSI into the .intunewin format, making them ready for deployment via Microsoft Intune to managed Windows devices seamlessly.
Compression & Encryption
The tool automatically compresses and encrypts your application files, ensuring faster upload speeds and enhanced security during transfer and storage, protecting sensitive data from unauthorized access or tampering.
CLI-Based Utility
This command-line tool is lightweight, scriptable, and fast. It requires no graphical interface, making it ideal for automation, batch packaging, and integration with custom deployment workflows.
Detection Rules
Detection rules help confirm whether an app is already installed or functioning correctly by checking files, registry keys, or scripts, enabling smarter deployment decisions and avoiding redundant installations.
Seamless Integration
IntuneWinAppUtil works perfectly within the Microsoft Intune ecosystem, allowing IT administrators to easily package, upload, and distribute applications to managed devices with consistent and reliable performance.
Dependency Management
You can set dependencies between applications, ensuring prerequisite software or frameworks are installed before the main app, preventing compatibility issues and improving successful installation rates across all devices.
How to Use IntuneWinAppUtil
Step-by-step instructions for packaging your Windows applications
Basic Command Structure
The tool uses a simple command-line interface with these primary parameters:
IntuneWinAppUtil.exe -c <source_folder> -s <setup_file> -o <output_folder> [-q]
Step-by-Step Process
- Prepare your application installer and any dependencies in a source folder
- Run IntuneWinAppUtil with the appropriate parameters
- Upload the generated .intunewin file to Microsoft Intune
- Configure application properties, requirements, and detection rules in Intune
- Assign the application to user groups or devices for deployment
Advanced Options
Explore advanced parameters and configurations for complex packaging scenarios
Command-Line Parameters
IntuneWinAppUtil supports several command-line parameters for customized packaging:
console.log( c <source_folder> # Source folder containing the application files
-s <setup_file> # Main setup file (e.g., setup.exe, install.msi)
-o <output_folder> # Output folder for the .intunewin file
-q # Quiet mode (suppresses output)
-a <arguments> # Additional arguments for the setup file );
Custom Detection Rules
Create custom detection rules to accurately determine if your application is already installed:
console.log( # Registry-based detection
HKLM\Software\Vendor\AppName
# File-based detection
C:\Program Files\Vendor\AppName\app.exe );
Troubleshooting
Solutions for frequently encountered problems when using IntuneWinAppUtil
Failed to load the source folder
Cause: The source path specified is incorrect or inaccessible.
Fix:
Double-check the folder path in the command line.
Ensure the directory is not protected or restricted.
Use quotation marks (
" ") around paths containing spaces.
Example:
The setup file cannot be found
Cause: The setup file path or filename is incorrect.
Fix:
Verify that the
.exeor.msifile exists in the source directory.Ensure correct spelling and file extension.
Tool not generating .intunewin file
Cause: Missing admin privileges or invalid output path.
Fix:
Run the tool as Administrator.
Confirm that the output folder exists and you have write permissions.
Recheck input parameters for typos.
Error parsing command line arguments
Cause: Syntax or spacing errors in your command.
Fix:
Always use the correct format:
Avoid extra spaces or missing flags.
Packaging works but app fails to install via Intune
Cause: Incorrect install or uninstall command in Intune configuration.
Fix:
Use silent install commands compatible with your setup file.
For
.msi:msiexec /i appname.msi /qnFor
.exe:setup.exe /silentor vendor-specific parameters.
Verify detection rules in Intune.
Permission Denied or Access Denied Errors
Cause: User account lacks permissions or files are locked.
Fix:
Run the tool in an elevated command prompt.
Close any program accessing the source folder.
Best Practices
Follow these guidelines for optimal application packaging with IntuneWinAppUtil
Packaging Guidelines
- Always test your packaged application in a non-production environment first
- Include all dependencies in the source folder to ensure offline installation
- Use descriptive names for your .intunewin files to easily identify them later
- Document any special installation parameters or requirements
- Keep your source files organized in version-specific folders
Deployment Strategies
Consider these strategies when deploying applications through Intune:
- Use phased rollouts to minimize impact on your user base
- Configure appropriate dependency relationships between applications
- Set up proper detection rules to avoid reinstalling already present applications
- Monitor deployment status and failure reports in the Intune console
FAQ's
What is IntuneWinAppUtil?
IntuneWinAppUtil (Intune Win32 Content Prep Tool) is a Microsoft utility that packages Win32 applications into the .intunewin format for deployment through Microsoft Intune.
What is the purpose of using IntuneWinAppUtil?
The tool prepares application installers so they can be securely uploaded and distributed via Intune’s Win32 app management system.
Where can I download IntuneWinAppUtil?
You can download it directly from the official intunewinapputil.com
What file types does IntuneWinAppUtil support?
It supports .exe, .msi, and .bat setup files for packaging into .intunewin format.
How do I run IntuneWinAppUtil?
Open Command Prompt, navigate to the tool’s folder, and use this command:
IntuneWinAppUtil.exe -c <source_folder> -s <setup_file> -o <output_folder>
What does the .intunewin file contain?
It contains compressed application files, metadata, and encryption details used by Intune for deployment.
Do I need administrative privileges to use IntuneWinAppUtil?
Yes, running the tool as Administrator ensures it has permission to access and package all required files.
Can I package multiple apps at once?
No, IntuneWinAppUtil packages one application per command. You can use PowerShell scripts for automation.
Why is my .intunewin file not generating?
The source or output path may be invalid, or the command syntax could be incorrect. Always verify folder permissions and paths.
What is the output of IntuneWinAppUtil used for?
The generated .intunewin file is uploaded to the Microsoft Intune portal for deployment to user or device groups.
Can I edit an existing .intunewin file?
No, .intunewin files are encrypted and cannot be modified. You must recreate the package if changes are needed.
What happens if the setup file is outside the source folder?
The tool will show an error: “Setup file path must be inside source folder.” Move the setup file into the specified source directory.
How do I silently install an app packaged with IntuneWinAppUtil?
Use silent install switches like /quiet or /qn in your Intune configuration during deployment.
Where are Intune installation logs stored?
You can find them in:
C:\ProgramData\Microsoft\IntuneManagementExtension\Logs
Does IntuneWinAppUtil compress files?
Yes, it compresses all source files into an encrypted .intunewin package to optimize upload and security.
Is IntuneWinAppUtil compatible with macOS or Linux?
No, it’s a Windows-only utility designed to package Windows-based applications.
Can I use IntuneWinAppUtil for MSI-based apps?
Yes, it fully supports .msi installers and allows silent installation through standard MSI parameters.
How do I troubleshoot deployment failures?
Check the Intune logs, review detection rules, and verify install/uninstall commands in your Intune configuration.
Is IntuneWinAppUtil open source?
Yes, Microsoft provides it as an open-source tool on GitHub, allowing community access and transparency.
What are the best practices for using IntuneWinAppUtil?
Use short file paths and simple names.
Always run as Administrator.
Keep installers and dependencies in one source folder.
Validate commands before packaging.