Application modernisation
IntuneWin
IntuneWin app package
An IntuneWin package is the `.intunewin` format produced by the Microsoft Win32 Content Prep Tool, wrapping a Win32 application's existing installer, whether an MSI, an EXE, or a script-driven setup.
Why IntuneWin matters in a Microsoft estate
IntuneWin matters during Windows 11, Intune, Azure Virtual Desktop, and Cloud PC programmes because application blockers can delay the whole rollout. The practical question is whether the term helps capture, package, sign, deploy, or troubleshoot an app with less rework.
How IntuneWin shows up in practice
This lets it be uploaded, assigned, and monitored as a managed Win32 app inside Microsoft Intune without requiring the application to be repackaged into MSIX first. Unlike MSIX, which gives an application a genuinely new, isolated package identity, IntuneWin is essentially a container wrapped around the application's original, unmodified installer. Intune unwraps it on the target device at install time and runs the original setup logic largely as-is. This is precisely why IntuneWin remains the practical choice for applications that are not good MSIX candidates, including those that install a driver or a system-level service, need genuinely unrestricted machine-wide write access, or depend on complex custom installer logic that MSIX's file and registry isolation model would break.
Because Intune runs the original installer rather than a re-architected package, IntuneWin deployments configure detection rules explicitly, telling Intune how to determine whether the application is already correctly installed on a device, commonly checking for a specific file version, a registry key, or an MSI product code. This detection logic is frequently the actual source of deployment failures in practice, more often than the underlying installer itself. An incorrect or overly narrow detection rule can report an application as failed when it installed correctly, or as successfully installed when an update silently failed.
Requirement rules similarly gate which devices are even eligible to receive the app, based on architecture, OS version, or available disk space, before Intune attempts the install at all. IntuneWin sits alongside MSIX and PSADT-driven Win32 packages as one of three common formats for deploying Win32 applications through Intune. The practical choice between them usually comes down to how well the application tolerates MSIX's isolation model: strong MSIX candidates should generally be packaged as MSIX for its cleaner install and uninstall behaviour. Everything else, particularly software needing genuine system-level access or complex pre- and post-install logic, is typically better served by IntuneWin or a PSADT-wrapped package instead.