Intune App Wrapping Tool Issues: Common Problems and Solutions
Users are reporting issues with the Microsoft App Wrapping Tool (IntuneWinAppUtil.exe) crashing during the wrapping process, especially when working with MSI installers. Here’s what’s happening and how to fix it.
The Problem
The IntuneWinAppUtil.exe tool has been closing unexpectedly during the wrapping process for about a week, particularly affecting MSI file packaging. Users report:
- Tool crashes at around 16-26% progress
- No error messages displayed before closure
- Issue affects the latest version of the tool
- Interactive prompts seem more prone to failure than command-line use
The Workaround That Works
Based on user reports, writing the command directly instead of using the interactive prompts resolves the issue. Here’s how:
Instead of double-clicking the executable and using prompts:
Open Command Prompt or PowerShell as administrator and run:
text.\IntuneWinAppUtil.exe -c "C:\path\to\source\folder" -s "installer.msi" -o "C:\path\to\output" -q
Where:
-c= source folder containing your installer-s= setup file name (your MSI)-o= output directory-q= quiet mode
Additional Troubleshooting Steps
1. Run from Command Line
Always use CMD or PowerShell instead of the GUI prompts. This prevents the tool from closing immediately if errors occur.
2. Check Permissions
- Run as administrator
- Ensure write access to output folder
- Exclude antivirus scanning on working directories
3. Path Considerations
- Use quotes around paths with spaces
- Try shorter folder names
- Avoid special characters in file paths
4. File Size Issues
The tool can struggle with packages over 8GB. Consider splitting large applications if possible.
5. Alternative Output Locations
If C: drive fails, try:
- USB drive as output location
- User profile folders (C:\Users\Public\Documents)
- Network drives with proper permissions
Known Issues and Limitations
- Windows 11 24H2 compatibility: Some users report extraction failures on specific 24H2 builds
- Terminal crashes: The tool has been crashing in Windows Terminal since late 2024
- File corruption: Occasionally the .intunewin file gets corrupted during creation
Best Practices
- Always test your .intunewin package before deployment
- Keep the source installer in a dedicated folder with no extra files
- Use simple, descriptive folder and file names
- Run packaging on a clean system when possible
- Exclude packaging directories from antivirus real-time protection
The command-line approach consistently works where the interactive method fails. While Microsoft hasn’t acknowledged this specific issue, the community workaround is reliable and should keep your packaging process running smoothly.
