InstallScout

InstallScout – user guide

InstallScout takes a Windows installer all the way to Intune. You give it an EXE, MSI, COM or MSIX. It does not run the installer — it analyzes the file, lets you edit the silent command, builds a local .intunewin and uploads the Win32 app with install, uninstall, detection and app logo.

Silent switches are one step. The destination is the package in Intune.

Version 1.9.2. Quick start: quickstart-en.html. Find the silent switches. Technical reference: reference-en.html. PDF: InstallScout-guide.pdf. Danish: vejledning.html.

Expected hit rate for the package and detection is further down in this guide.

FileEngineTypical result
Git-2.51.0-64-bit.exeInno SetupLocal and online agree on /VERYSILENT … · System · not unpacked
jre-8u491-windows-x64.exeInstallShieldLocal /s /v"/qn" · online Java 8 /S · System
AcroRdrDC….exeSelf ExtractorOuter /sAll /rs /rps /msi /quiet · online Acrobat Reader · System
SlackSetup.exeSquirrelPer-user · User

1. Start and window

Double-click InstallScoutPortable.exe or run Start.bat. No installation is required. The UI defaults to English; switch to Dansk in the top-right corner. About… next to the language field shows the version, developer, and links to GitHub. It also says that startup sends one anonymous call to Aptabase in the EU (eu.aptabase.com) with the version and language. File names and paths are not sent. INSTALLSCOUT_USAGE=0 turns the call off.

The download is not code-signed. Windows or company security may warn or block it. Choose Keep / Run anyway, ask IT to allow the file, or try it in a VM or Windows Sandbox without those policies.

Empty InstallScout window. Steps 1 Files, 2 Check and 3 Package are grouped, Clear sits left of More, and Try in Sandbox is under the silent command
Empty InstallScout window. Steps 1 Files, 2 Check and 3 Package are grouped, Clear sits left of More, and Try in Sandbox is under the silent command

Drop an installer on the window, or use Add files / Add folder. The empty start shows Drop an installer here in the file list and a short introduction on the Commands tab. Try in Sandbox sits under the silent command when Windows Sandbox is installed. EXE, MSI, COM and a whole folder can be dropped.

The steps sit in three groups: 1 Files, 2 Check and 3 Package. They share one row when the window is wide enough, and Package moves down when it is narrow. Only the next step is highlighted: Add files when the list is empty, Analyze when a file is not analyzed, Intune package when the selected file has no current package, and Upload to Intune when that package exists. Clear sits left of More. The language is changed at the top right. The default is English.

Left: file, engine, confidence and status. Confidence is green from 75 %, amber from 40 %, and red below that. The selected row keeps that color on a darker blue background. Status is Analyzed, Packaged, or Rebuild.
Right: the silent command wraps over three lines. Press Enter to save it. Above the tabs: engine, confidence, System or User, and the online result. Then Extra switches, and the tabs Commands, Online, Intune, Detection, PSADT, Found switches, Evidence and notes, and MSI / Version.

Status and progress sit on their own row under the buttons, so they stay visible when the window is not maximized.

ButtonAction
Add files… / Add folder…Choose EXE, MSI, COM, MSIX
AnalyzeRead the file locally
AnalyzeRead the file locally, then look up WinGet and Chocolatey (name/vendor only)
Try in SandboxOptional. Run the silent command and detection in Windows Sandbox. This PC is not changed, and you can continue while it runs. Shown only when Sandbox is installed
Silent Install HQOpens a name search in the browser — file is not uploaded, command is not overwritten
Copy commandSilent line to the clipboard
PSADT package…Folder with PSADT 4.1.8
Intune package…Local .intunewin + detection — required before upload. The dialog opens in the last folder you used
Package all…One .intunewin per analyzed file. Upload stays one app at a time
Upload to Intune…Sign in and create the Win32 app (logo, context, detection, supersedence)
Add / Save commandExtra switches, or save the edited line
Use online switchesShows the local and online command. The local line changes only after you confirm

2. Workflow

The process ends with upload. The silent command is a middle step.

  1. Add the file and click Analyze.
  2. Read the green silent command. Edit it, or add extra switches, then click Save command / Add.
  3. Try in Sandbox is optional. Click it to run the command and the detection script in Windows Sandbox. This PC is not changed. You can build the package and upload while the test runs.
  4. Read the Online tab when it fills in. A confident local engine is kept if the catalog disagrees. A weak local guess is replaced when WinGet or Chocolatey has a matching product. On none, use Silent Install HQ (name search only).
  5. Open Intune and check Install context (System/User).
  6. Build an Intune package (local .intunewin). Test with Invoke-AppDeployToolkit.exe.
  7. Upload to Intune — the dialog opens tall enough to show the name, command, logo, supersedence and sign-in. One Edge profile is shown; open the field to pick another. Sign in to Intune, Cancel and Upload share that row.

Try in Windows Sandbox

Try in Sandbox is optional. It shows whether the silent command actually installs, without leaving the app on this PC. The button sits under the silent command, and only when Windows Sandbox is installed. Do not start Windows Sandbox manually, or the button stays grey. You can build the Intune package and upload while the test runs. The result comes back in this window when the test finishes. The start window says the same thing in the short introduction.

Git analyzed as Inno Setup. Try in Sandbox is under the silent command
Git analyzed as Inno Setup. Try in Sandbox is under the silent command

The sandbox runs the silent command, then the same Detection.ps1 that Intune will use. A message in the sandbox shows the install exit code and whether detection matched. InstallScout reports that result in this window. Close the sandbox when you are done. If you close it before a result comes back, Try in Sandbox turns back on so you can change the command and run it again. Its disk is discarded.

Only one Windows Sandbox can run. Close an open one before you try again. The command must still name this installer. A package folder — the setup plus MSI, CAB, or a subfolder the installer needs — is shared read-only, so the sandbox can read those files and cannot write back to this PC. A file directly in Downloads, Desktop, Documents, the OneDrive root, Temp, or the user profile is copied in on its own, even when that folder has been redirected. A subfolder there, for example Downloads\PSADT - CutePDF, still counts as a package folder. The sandbox has a network connection, because some installers download their payload. On a PC with free RAM it gets up to 8 GB of memory. The default ceiling is 4 GB.

An MSIX or AppX command such as Add-AppxPackage runs through PowerShell in the sandbox. If the install fails, the error text appears in the result. InstallScout also reads the frameworks an MSIX or MSIX bundle depends on, for example Microsoft.WindowsAppRuntime.2, and lists them in the notes. A fresh Sandbox and an Intune device without those frameworks fail with 0x80073CF3, so package the frameworks with the app or install them first.

Analysis still does not run the installer. Sandbox is a separate test, and you start it yourself.


3. Local switch check

Local analysis looks inside the binary — markers, PE sections, VersionInfo, MSI properties and text switches in the file. It picks an engine (Inno, NSIS, InstallShield, MSI, Self Extractor, …) and builds the command from that engine’s known silent flags.

Inner setup (unpack) happens locally and without running the installer. The goal is the silent line (and the file copied into Files\) from the payload that actually installs the product.

SituationWhat InstallScout does
Wrapper: 7-Zip SFX, WinRAR SFX, IExpress, WiX Burn, InstallShield, Advanced Installer, Self ExtractorLooks for ZIP, embedded MSI, CAB, and 7z (bundled 7za)
Unknown engine or very low confidenceSame cheap unpack (ZIP / MSI / CAB / 7z)
Clean engines: Inno, NSIS, Squirrel, DDPM, Wacom, Chrome, Python, …Does not unpack — the outer EXE already has the right dialect
Self Extractor with outer silent flags (/sAll, --silent, /silent)Keeps the outer command (typical Adobe-style /sAll /rs /rps /msi /quiet)
Self Extractor without those flagsAdopts the inner setup when it is found (often an MSI)

The installer is never executed to unpack. Large vendor SFX files are therefore not extracted just to confirm a /sAll that is already in the file.

What to look at

Expected hit rate

These figures are estimates for a typical Intune queue: MSI, Inno, NSIS, InstallShield, WiX Burn, and known vendor EXE files. They describe the first result, before the command is edited. InstallScout does not measure whether the package or the detection succeeded.

ClassSilent installDetection after a successful install
MSI and WiX MSIabout 95%about 95%
Inno, Advanced Installer, WiX Burnabout 85%about 75%
NSIS and Self Extractor with known flagsabout 75%about 70%
InstallShieldabout 60%about 70%
Squirrel, ClickOnce, Qt, unknown EXEabout 35%about 40% in Sandbox, lower in Intune

MSI carries the package rate. msiexec /qn is stable, and detection uses the product code. InstallScript without a recorded setup.iss, custom dialogs, and an EXE whose Apps & features name differs from the file pull the rate down.

Detection is the narrower step for an EXE. It requires the name, the publisher, and the version together. The file version is often more precise than DisplayVersion, so the script can report the app as missing after a successful install. A per-user install can pass in Windows Sandbox and still fail in Intune, because detection runs as SYSTEM and reads that account’s HKCU.

Below about 40% confidence, treat the package as a draft. The hit rate there is closer to one in three.

Example: Git (Inno Setup)

Git analyzed as Inno Setup. Try in Sandbox is under the silent command
Git analyzed as Inno Setup. Try in Sandbox is under the silent command

Local conclusion:

Engine: Inno Setup · confidence 95 %
"C:\pkg\Git-2.51.0-64-bit.exe" /VERYSILENT /NORESTART /SUPPRESSMSGBOXES /SP-

Inno does not use /S. That is in the notes. The Commands tab also shows the PowerShell form.

Example: Java 8 (InstallShield + embedded MSI)

Java Platform SE 8 is detected as InstallShield. The silent line becomes:

jre-8u491-windows-x64.exe /s /v"/qn"

/s is InstallShield; /v"/qn" is passed to the embedded MSI. That is the local, file-based truth — even if WinGet names the product differently.

In the PSADT package, an InstallShield line that contains quotes is started through cmd /d /s /c, so /v"/qn" is preserved. The package elevates itself when it is not already running as administrator. Intune as SYSTEM is already administrator and skips that.

Example: vendor Self Extractor (Adobe and others)

FileDescription / ProductName Self Extractor is a vendor wrapper class, not a product. Adobe, Lenovo and others use the same label.

Other typical local defaults

EngineSilent
MSI / WiXmsiexec /i file.msi /qn
NSIS/S (capital S)
Advanced Installer/exenoui /qn
WiX Burn/quiet
7-Zip SFX / Wacom/s
Self Extractor/sAll … (uninstall /uninst) or harvested --silent / /silent
DDPM/Silent (not InstallShield /s /v"/qn")

/install is not added. It is already the default action for WiX Burn. /norestart is not added either. Inno Setup still uses its own /NORESTART. Type /norestart under Extra switches when a quiet install must not reboot the PC.

Manual switches

The green line is editable. Under it are Extra switches, Add and Save command.

Extra switches field, Add and Save command under the silent line
Extra switches field, Add and Save command under the silent line
Suggested switches. Tick a box to add that switch to the command. Here /analytics no is selected
Suggested switches. Tick a box to add that switch to the command. Here /analytics no is selected

4. Online switch check

Analyze looks the product up in WinGet and Chocolatey after the local result is shown:

Silent Install HQ opens a browser search for the product name on silentinstallhq.com. The installer file is not uploaded, and the silent command is not overwritten. Use it when WinGet/Chocolatey conflict or return nothing — vendor-specific CLIs often live there.

Only the product name and vendor are sent — not the installer file.

Search uses both the long product name and catalog names. Wrapper labels are stripped so WinGet is not queried for Adobe Self Extractor. Compact file names are expanded to names the catalogs actually index:

In the fileOnline search
Java Platform SE 8 U491Java 8 (Oracle.JavaRuntimeEnvironment)
Adobe Self Extractor + AcroRdrDC….exeAcrobat Reader
GoogleChromeStandaloneEnterprise64.exeGoogle Chrome
npp.8.6.Installer.x64.exeNotepad++

The Online tab shows a result:

ResultMeaning
matchSame installer family (Inno, MSI, NSIS, …)
partialSome flags overlap
conflictDifferent family — read the sources, test in a VM
noneNo hits (e.g. an internal/unnamed package)
errorNetwork or source failure

Example: Git — local and online agree

Online tab: match for Git from winget.exe and Chocolatey
Online tab: match for Git from winget.exe and Chocolatey
Search: Git
Result: match
Online silent switches match (inno): /VERYSILENT /NORESTART /SUPPRESSMSGBOXES /SP-

Local switches: /VERYSILENT /NORESTART /SUPPRESSMSGBOXES /SP-

winget.exe: Git.Git
Chocolatey: git

Here you can keep the local command.

Example: Java — the catalog is coarser than the file

Online finds Java 8 with /S. Locally it is InstallShield /s /v"/qn". Both may be “quiet enough”, but the local line is more precise for this Oracle wrapper.

Catalogs can be wrong (wrong edition, OpenJDK instead of Oracle). Always test in a VM.


5. User vs system context

Intune Win32 must run as system or user. The wrong choice shows “installed” for the wrong account, missing Program Files files, or detection that never matches.

InstallScout infers context automatically and shows it on the Intune tab, in Intune.txt and in the Upload to Intune dialog. You can override it at upload.

An installer path under %LOCALAPPDATA%\Temp does not count as user context — only the arguments after the file path.

Default: System (machine install)

Most business Win32 packages should run as system: MSI with ALLUSERS=1, InstallShield, Advanced Installer, Inno/NSIS without a per-user flag.

Java/InstallShield on the Intune tab with Install context System
Java/InstallShield on the Intune tab with Install context System
Install context
System
InstallShield is typically a machine install and requires system context.

Minimum operating system     Windows 10 22H2
Installation time required   60
Device restart behavior      No specific action

The same default fields are used when uploading to Intune.

Exception: User (per-user)

Squirrel (Slack, many Electron apps), InstallAllUsers=0 / ALLUSERS=0, or an install that explicitly targets AppData.

Slack/Squirrel on the Intune tab with Install context User
Slack/Squirrel on the Intune tab with Install context User
Install context
User
Squirrel/per-user installers place files in AppData and must run in user context.

In Upload to Intune, System/User is preselected, but you can change it if you know the package better than the guess.

Why it matters

ContextTypical targetDetection
SystemC:\Program Files, HKLM UninstallMachine ARP / MSI ProductCode
User%LOCALAPPDATA%, HKCU UninstallThe user’s Uninstall key — fails if the app runs as system

6. Upload to Intune

Upload is a two-step run: first a local .intunewin, then Upload to Intune. The program uploads the package you already saved — it does not repackage on upload.

Analyze  →  Intune package… (local .intunewin)  →  Upload to Intune… (Graph upload)

What lands in Intune is a Win32 app with:

Step 1 — local Intune package

Intune package… opens in the folder you used last. It saves:

FileContents
*.intunewinEncrypted Win32 payload (same format as Microsoft Win32 Content Prep)
PSADT sourceInvoke-AppDeployToolkit.exe + script + Files\
Intune.txtFields for the portal
Detection.ps1Custom detection

Package all… writes one .intunewin for each analyzed file in the same folder. A file that has not been analyzed is left out. Upload is still one app at a time. After either save, the selected row says Packaged.

Detection

Intune treats the app as installed when Detection.ps1 exits 0 and writes a line to STDOUT. Empty output means not installed. The script does not throw. The same rules apply to every vendor.

What the installer hasWhat is matched
Product code (MSI, or a GUID in the uninstall command)That code in the uninstall registry, and the version
EXE without a product codeDisplay name, publisher and version
MSIXPackage name, and the version when it is known

Until a package exists for the selected file, Upload to Intune is grey. After the package is saved, the button becomes active:

Upload to Intune is active when a local .intunewin exists
Upload to Intune is active when a local .intunewin exists

Test the source before upload:

.\Invoke-AppDeployToolkit.exe -DeploymentType Install -DeployMode Silent

Step 2 — Upload to Intune

Click Upload to Intune…. The dialog sizes itself so the content is visible without scrolling. One Edge profile is shown at the bottom. Open the field to pick another. Sign in to Intune, Cancel and Upload share that row.

Upload to Intune with app logo, Choose file, Paste and Remove
Upload to Intune with app logo, Choose file, Paste and Remove

Logo

In the dialog

  1. Edit Name in Intune if the detected name should not be the name in Company Portal. Version stays in Display version.
  2. Check the install, uninstall and detection summary.
  3. Confirm Install context (System/User). Change it only if you know the package better.
  4. Check the app logo (preview). Override with a file or paste if the automatic icon is wrong.
  5. Tenant and Client ID can stay empty: then organizations and Microsoft Graph PowerShell are used. InstallScout does not create an Entra app.
  6. Edge profile for sign-in shows the selected profile. The work profile is selected when it can be recognized. Open the list to pick another.
  7. Sign in to Intune — browser login (PKCE, localhost) in the selected Edge profile. Device code is not used, because Conditional Access often blocks it.
  8. After sign-in: optionally choose supersedence (see below). Nothing is selected automatically.
  9. Upload — creates the app, uploads .intunewin, sets detection, logo and optional supersedence. The status line shows progress.

Supersedence

In Upload to Intune the new Win32 app can replace older versions in the tenant — the same feature as Supersedence in the Intune portal.

Wait until the status is Signed in as …, not only that the Edge profile opened. Only then does InstallScout look up Win32 apps. The search uses the product name (startswith on displayName), not the entire Win32 catalogue. The list shows apps whose names look like the product — e.g. Git 2.50.0 when you send Git 2.51.0. The same vendor with a different product is typically omitted.

Upload to Intune: supersedence list with Git 2.50.0 selected and Update
Upload to Intune: supersedence list with Git 2.50.0 selected and Update
.\InstallScoutPortable.exe --cli .\setup.exe --intune C:\out\intune --publish-intune --supersede update
.\InstallScoutPortable.exe --cli .\setup.exe --intune C:\out\intune --publish-intune --supersede replace --supersede-id <app-guid>

--supersede update|replace matches on product name as in the GUI. Repeat --supersede-id if you already know the Intune app ID.

After success, a link to the app in the Intune portal opens.

What Graph writes on the app

FieldValue
App typeWin32 (win32LobApp)
Install command.\Invoke-AppDeployToolkit.exe -DeploymentType Install -DeployMode Silent
Uninstall command.\Invoke-AppDeployToolkit.exe -DeploymentType Uninstall -DeployMode Silent
DetectionPowerShell script, not 32-bit, no signature requirement
runAsAccountsystem or user
Minimum OSWindows 10 22H2
Max runtime60 minutes
RestartNo specific action (suppress)
LogolargeIcon (PNG/JPEG from EXE, MSI, file or clipboard)
SupersedenceOptional: Update or Replace against up to 10 older Win32 apps

Third-party updates (beta)

> Beta. Matching, download, packaging, and upload are tested, but the feature is new. Check the first packages yourself, assign them to a pilot group before a wider rollout, and confirm guessed matches with Set package ID…. The automatic supersedence chain is covered by tests, but has not been run against a live tenant yet.

Apps such as Git, 7-Zip, Notepad++, or Firefox need a new Win32 app every time the vendor ships a version. More › Update check (beta)… in the main window finds the ones that are behind and builds the update.

The More menu with Update check (beta) as the last entry
The More menu with Update check (beta) as the last entry
Third-party updates (beta): Git and Notepad++ are behind, ClickShare is behind but must be downloaded by hand, 7-Zip is up to date
Third-party updates (beta): Git and Notepad++ are behind, ClickShare is behind but must be downloaded by hand, 7-Zip is up to date
  1. Sign in to Intune — at the top of the window. It shows the signed-in account, or Not signed in. Pick the Edge profile for the Microsoft sign-in, and fill in a tenant if you do not use organizations. Check Intune signs in by itself when needed, with the same choices.
  2. Check Intune — signs in, reads your Win32 apps with their display version, and groups versions of the same product (Git 2.40.0 and Git 2.45.0 are one product). Each product is matched to a package, and the newest version is shown next to yours. WinGet comes first: the list of all WinGet packages is downloaded once a day and matched on this PC, so no search service is needed and winget.exe does not have to be installed. When WinGet has nothing, Chocolatey is asked, and only when the name is identical. Only product names are sent, and only to Chocolatey.
  3. The match is a guess from name and publisher, and the list says (guess). Set package ID… confirms it. Write a WinGet ID such as Git.Git, or choco:clickshare-desktop for Chocolatey. InstallScout remembers the choice. An empty ID forgets it. Products with No match are usually vendor or in-house software that neither catalogue has. Confirm one by hand when you know its package.
  4. Build update — downloads the installer from the manifest and checks its SHA256. A file that does not match is deleted, and nothing is built. The manifest also gives the silent switches, the exact Apps & features name and publisher, the version, and the MSI product code, so detection fits the product instead of a guess. The package is written to your Intune folder. The download sits in its _winget subfolder.
  5. Ask users to close these programs — optional. Enter names such as git, code. The install command then runs with -DeployMode Auto: a dialog when someone is signed in, silent when nobody is. Users can defer for up to three days, and they are asked again after four hours. After that the programs close after a ten minute countdown. The app also gets the return code 1602 as retry, so a deferral does not count as a failed install. Without names, the package is silent as before.
  6. Test upgrade in Sandbox — installs the version Intune has now (the previous WinGet version when that one is gone; when its download fails the SHA256 check, because the vendor replaced the file, the next older versions are tried, three at most), then the new one, and runs the new detection script before and after. Detection must say not installed first and installed last. The result names the problem: the old version did not install, detection is too lax (Intune would never update), the upgrade failed, or detection does not find the new version (Intune would keep reinstalling). The test also lists the programs the new version added. They go into the close-programs field when it is empty.
  7. Upload and supersede… — uploads the app and supersedes the earlier versions in the same product group as Update, at most 10.

Limits:

.\InstallScoutPortable.exe --cli --outdated
.\InstallScoutPortable.exe --cli --outdated --only git --map "Git=Git.Git"
.\InstallScoutPortable.exe --cli --winget Git.Git --intune C:\out\intune
.\InstallScoutPortable.exe --cli --winget Git.Git --intune C:\out\intune --close-apps git --upgrade-test --publish-intune

PSADT package without Intune

PSADT package… is the same source without .intunewin — useful for VM testing before you package for Intune.

Command-line upload

.\InstallScoutPortable.exe --cli .\setup.exe --intune C:\out\intune --publish-intune --icon .\logo.png

--publish-intune requires --intune (local package first), same as in the GUI. Without --icon, the logo is taken from the EXE or MSI when the package has one.

Sign-in and permissions

Sign-in opens in the browser with PKCE. Device code is not used.

Windows DPAPI encrypts the access token and the refresh token for the current Windows user, in %LOCALAPPDATA%\InstallScout\graph.json. The saved session is bound to the selected tenant and Client ID. A different pair does not reuse it. A plaintext token file from an older version is deleted and cannot be used. Sign-out deletes the file.


7. Command line

InstallScoutPortable.exe with no arguments opens the GUI. For scripts:

# Local analysis
.\InstallScoutPortable.exe --cli "C:\installers\Git-64-bit.exe"

# Local + online
.\InstallScoutPortable.exe --cli "C:\installers\jre-8u491-windows-x64.exe" --online

# Silent Install HQ (name search in the browser; does not upload the file)
.\InstallScoutPortable.exe --cli "C:\installers\DDPM-Setup.exe" --sihq

# JSON
.\InstallScoutPortable.exe --cli .\setup.exe --json --out .\analyse.json

# Extra switches
.\InstallScoutPortable.exe --cli .\setup.exe --switches "/LOG=C:\logs\app.log"

# Local Intune package
.\InstallScoutPortable.exe --cli .\setup.exe --intune C:\out\intune

# Package + upload + logo (requires --intune)
.\InstallScoutPortable.exe --cli .\setup.exe --intune C:\out\intune --publish-intune --icon .\logo.png

# Upload and supersede matching Win32 apps
.\InstallScoutPortable.exe --cli .\setup.exe --intune C:\out\intune --publish-intune --supersede update

From source: python -m installscout with the same flags. Use --lang da for Danish CLI text.


8. Supported engines

MSI, Inno Setup, NSIS, InstallShield, WiX Burn, Advanced Installer, InstallAware, BitRock, Squirrel, Wise, install4j, Qt Installer, 7-Zip SFX, Wacom, WinRAR SFX, IExpress, Self Extractor, DDPM, MSIX/AppX, ClickOnce.

Unknown engine: look at Found switches and Evidence. Analyze also asks WinGet and Chocolatey and uses that hit when the local guess is weak. Wrappers and unknown EXEs are unpacked locally first so an inner MSI can replace Unknown 15 %.


9. Limits