What Bulk App Analyzer helps you do
Drop a folder of MSI and EXE installers into your browser and build a packaging inventory without uploading anything. Haivix extracts metadata, hashes, signature presence, Intune silent commands, packaging warnings, and version families — then hands off selected apps to the Detection Rule Generator.
This workflow is designed for browser-first processing, so you can complete the task quickly without sending files off to another dashboard or waiting for an account workflow.
How to use Bulk App Analyzer
- Drop MSI and EXE installers into the workbench, then run Analyze Packages and watch Ready / Warnings / Need Review summarize the batch.
- Open a row for Intune silent commands, detection recommendations, and packaging warnings; export CSV or Intune Inventory when needed.
- Select one or more apps and Generate Detection Rule to hand off into the Detection Rule Generator with prefilled inputs.
What you can do with Bulk App Analyzer
- Analyze many MSI and EXE packages locally with a concurrent job queue (files never leave the browser).
- Extract MSI ProductCode, UpgradeCode, version, manufacturer, language, architecture, and install-scope hints.
- Read EXE VERSIONINFO, architecture, installer engine heuristics, Authenticode directory presence, and SHA-256.
- Surface Ready / Warnings / Need Review filters plus duplicate, older-version, and ProductCode collision checks.
- Group related releases into version families by UpgradeCode or product identity.
- Export CSV, Excel, JSON, PowerShell, and an Intune Inventory CSV for packaging teams.
- Deep-link one or many packages into the Intune Detection Rule Generator with prefilled detection inputs.
Example: inventory a packaging share
Drop MSI and EXE files together, review the MSI/EXE counts, then run Analyze Packages. Watch Ready / Warnings / Need Review summarize the batch.
Open a row for Intune silent commands and detection recommendations, export Intune Inventory CSV, then Generate Detection Rule for selected apps.
What to know before you start
- Authenticode presence is not Windows trust verification — Haivix does not call WinVerifyTrust in the browser.
- Missing EXE VERSIONINFO fields are shown as not provided, not as hard errors.
- Silent switches for unknown EXE engines are never invented.
- Very large batches stay local but may take time; files over 250 MB are skipped.
Frequently Asked Questions
No. Analysis runs entirely in your browser. Network upload is none — files never leave your device.
ProductName, ProductVersion, Manufacturer, ProductCode, UpgradeCode, PackageCode, language, architecture, and install-scope hints from the MSI Property table and Summary Information — without running the installer.
Haivix reads PE headers and VERSIONINFO when embedded, identifies common installer engines (Inno, NSIS, WiX Burn, InstallShield, Squirrel), reports Authenticode directory presence (not Windows trust), and recommends curated silent switches only when confidence is Confirmed or Likely.
Ready means parse succeeded with no packaging warnings. Warnings flag issues such as missing Authenticode, unknown EXE engines, older versions, or architecture outliers. Need Review covers parse failures, missing MSI ProductCode, duplicate ProductCodes across different hashes, and same-version/different-hash collisions.
An export tailored for packaging inventories: file name, product metadata, ProductCode/UpgradeCode, architecture, installer type, silent install/uninstall, recommended detection type/value, SHA-256, signature status, analysis status, and warnings.
Open Generate Detection Rule on a row to prefill the Detection Rule Generator, or select multiple packages and generate detection rules for the selection via a local handoff queue.
No. V1 reports whether an Authenticode certificate table is present in the PE. It does not call WinVerifyTrust or validate the certificate chain against Windows trust stores.