Turn any installer into a package you can deploy.
BE Repackager inspects your vendor setup, recommends wrapping or repackaging, and builds the .msi and .intunewin you hand straight to Intune or SCCM — all on your own machine.
Windows 10 / 11 · 64-bit · free, no account needed
From setup.exe to finished package.
Four steps, one straight line. Each step makes the next decision easier — no dead ends, no second-guessing.
Inspect the installer
Signature, reputation and silent-install support are checked up front — so the first decision is informed, not a guess.
Wrap or repackage
BE Repackager weighs silent support against risk, then recommends the route you can actually defend in a change review.
Review the changes
Snapshot and diff show exactly which files, registry keys and drivers landed — keep what belongs, drop the rest.
Build MSI & Intune
One build produces a clean, versioned .msi — and an .intunewin beside it — ready to hand to your deployment tool.
Made for the way packagers actually work.
Two methods, one decision.
Wrap clean silent setups, repackage the ones with drivers or risk. BE Repackager branches only where the installer forces it — never for the sake of it.
- Detect silent parameters automatically
- Snapshot & diff for a lean, robust MSI
- Intune .intunewin in the same run
Every action with a reason.
The live console, diff review and build log all read the same — so the operator and the auditor see one story, not a stack trace.
- Live console with timestamps
- File and registry diff
- Traceable build output
Deployable, ready for rollout.
You finish with artifacts you can ship today: a versioned .msi, optionally an .intunewin — no extra cleanup, no surprises at deploy time.
- MSI & .intunewin output
- Versioned builds
- Runs locally on Windows, nothing leaves the machine
Run it on your toughest installer.
Download it, point it at a real setup, and watch the decision, the diff and the finished package come together — on your own machine, in minutes.
Common questions.
When the installer brings drivers, services, deep registry changes or a flaky silent switch, a repackaged MSI is usually easier to validate, deploy and uninstall cleanly.
Yes. Every build can produce an .intunewin for Microsoft Intune right next to the .msi — no separate tool, no extra step.
No, and on purpose. Everything runs locally on Windows, so your installers, registry and drivers never leave the machine.
None by default. Update checks and crash reports are opt-in, and you see exactly what would be sent before anything leaves.
Write us at support@bath-electronics.de — ideally with some screenshots of the error, that makes the problem much faster to track down.