Skip to content
Create win32 intunewin
Home » Create Win32 App / .intunewin

Create Win32 App / .intunewin

Creating a Win32 app or ".intunewin" file for is very easy.
The hardest part of any package is the installation logic itself. You can handle this in a PowerShell script or CMD file, for example. I personally prefer the way via PowerShell and call the installation file "install.ps1".
You can find an explanation of the structure here: my take on win32 apps - Intune

Once you have created your routine, proceed as follows:

  1. Load the current one Microsoft Win32 Content Prep Tool down
  2. Open the downloaded "IntuneWinAppUtil.exe"
  3. Provide the path to your package
  4. Enter the installation file, for me in each case: install.ps1
  5. Enter the path to the storage of the .intunewin file
  6. If there is already a file with the corresponding name, you can delete / overwrite it
  7. For the Catalog Folder question, we choose No (N)
  8. Done, that was creating the Win32 App / "intunewin".
Win32 Content Prep Tool

Once the package has been created, you can use it in Endpoint Manager / Intune under «Apps > Windows apps" Add.
The parameters within the apps are then different depending on the application.
As install and uninstall command you can use in most cases use the following:

install command%SystemRoot%\sysnative\WindowsPowerShell\v1.0\powershell.exe -windowstyle hidden -executionpolicy bypass -command .\install.ps1
uninstall command%SystemRoot%\sysnative\WindowsPowerShell\v1.0\powershell.exe -windowstyle hidden -executionpolicy bypass -command .\uninstall.ps1

10 thoughts on “Win32 App / .intunewin erstellen”

  1. Pingback: Excel standard template with Intune | scloud

  2. Pingback: "Proactive Remediation for Business" | scloud

  3. Pingback: Install Worksheet Crafter with Intune | scloud

  4. Pingback: chocolatey - basic installation with Intune | scloud

  5. Pingback: My take on Intune Win32 apps | scloud

  6. Pingback: How to: winget & Intune | scloud

  7. Your install and uninstall commands include %SystemRoot%\sysnative in the path to powershell. I've never seen a folder 'sysnative' before?

Leave a Reply

Your email address will not be published. Required fields are marked *

de_CH DE
de_CH DE
en_US EN
Exit mobile version