FAQ | Intune Win32 Deployer

Short answer: most issues come down to execution policy, missing Chocolatey/winget prerequisites, or Intune Administrator permissions - see the specific fixes below.

In the FAQ of the “Intune Win32 Deployer” I answer general questions about handling and the functions.
Do you also have a question? Then tell me either in the comments, via a social media channel or via contact form.

Introducing the “Intune Win32 Deployer”

Which detection rule is used during upload?

• Winget: Detection rule via PowerShell Script. Template: check.ps1 (github.com)
• Chocolatey: Folder detection under “C:\ProgramData\chocolatey\lib” and the folder with the Chocolatey ID.

Do I have to be an administrator to run the app?

Basically not. Certainly not for execution.
During installation, however, it is checked whether Chocolatey and winget are available on your system. If not, you will be asked if you want to install it. .
But if you only want to distribute winget apps, you don’t need Chocolatey.

What permission do I need to upload the apps to Intune?

The Intune Administrator role is sufficient for this.

Nothing happens when I start the installation, why?

This is almost certainly related to the execution policy on your system.
You can bypass these by invoking the installer like this:
PowerShell.exe -ExecutionPolicy Bypass -File ”.\INSTALL_Intune-Win32-Deployer.ps1”

How does this work with winget and the system context?

Rudy Ooms has written a great article on this, which he keeps up to date: Install | Deploy | Use Winget | System context | Intune (call4cloud.nl)

The upload got stuck or failed halfway through - what now?

Check the “IntuneWinAppUtil” packaging step first: if the generated .intunewin file is missing or 0 KB in the tool’s working folder, the Win32 Content Prep Tool itself failed - usually because the source path contains a character it doesn’t handle well, or an antivirus/EDR product is locking temp files mid-packaging. Re-run from a path without spaces or special characters, and temporarily exclude the tool’s working directory from real-time scanning if that doesn’t help.

Can I re-run the tool to push an update to an app I already deployed?

Yes - re-running the deployer for an app that’s already in Intune creates a new app version rather than a duplicate app, as long as the app name and detection rule stay consistent between runs. If you changed the detection method (e.g. switched from Chocolatey to winget), treat it as a new app instead to avoid orphaned assignments on the old one.