Turn an .exe into a Windows installer (exe to Setup.exe)

"Convert exe to installer" is one of the most searched phrases around Windows packaging, and it hides a common confusion: an .exe and a Setup.exe are both executables, but they do different jobs. Your .exe is the app. The installer is a second program that puts the app in the right place, with the shortcuts and the uninstall entry Windows users expect. Here is how to make one from what you already have.

When you need an installer, and when you don't

A single portable .exe that runs from anywhere needs no installer. Users download it and double-click it. That's fine for small tools.

You want an installer when:

• the app needs more than one file (DLLs, assets, a data folder) and you don't want users digging through a zip;
• it should appear in the Start Menu and in Settings → Apps, with a clean uninstall;
• it should live in Program Files, or install per user on machines without admin rights;
• customers, IT departments or app stores expect "a proper setup".

What you need before you start

1. The app folder. Build or publish your app so that one folder contains everything it needs at run time. Test it by copying that folder to another PC and running the .exe from there. If it starts, the folder is complete.
2. The main executable. The file users should launch. With one .exe, that's it; with several (a launcher plus helpers), know which one is the entry point.
3. An icon. A .ico file for the installer and the shortcuts. Many apps already have one; otherwise an online converter turns a PNG into an ICO.
4. Version and publisher name. Shown in the wizard and in Windows Settings.

Convert the .exe to an installer with ExeTup

1. Zip the app folder, or upload the single .exe directly.
2. Pick the main executable from the list ExeTup shows.
3. Enter the name, version, publisher and optional licence.
4. Choose where it installs (all users or current user), the architecture, shortcuts and launch options.
5. Build, then download Setup.exe.

The result is a standard NSIS installer. Users run it, click through the wizard, and the app lands in Program Files with a Start Menu shortcut and an uninstaller. Nothing inside your .exe changes.

Doing it by hand instead

If you prefer a local tool, both are free:

• NSIS: write a .nsi script that lists the files, the shortcuts and the registry entries, then compile it with makensis. ExeTup generates exactly this kind of script for you; see NSIS installer online.
• Inno Setup: write an .iss script and compile it on Windows. See Inno Setup alternative for a comparison.

Both are solid choices when you are happy to maintain a script with every release.

Files that go next to the .exe

Some apps need files the build didn't produce: a sample config, a readme, fonts, a licence file. ExeTup's "Other files" step adds them alongside the main program, so they are installed and uninstalled with everything else.

FAQ

Does the installer modify or repack my .exe?

No. The installer compresses your files inside itself for transport and writes them back unchanged. Your .exe keeps its signature, if it has one, and its icon.

Can I wrap a single .exe with no other files?

Yes. Upload the .exe on its own. The installer still gives you shortcuts, an uninstaller and a Settings entry, which is the point of wrapping it.

Will the installer work on 32-bit Windows?

If you choose 32-bit. A 64-bit installer refuses to run on a 32-bit system and says so, which is what you want for a 64-bit app.

How do I make the app start with Windows?

Turn on "launch at start-up" in the options. The installer registers the app in the user's Run key, and the uninstaller removes it.