Convert EXE to DEB

Debian and Ubuntu administrators may need a .deb file to deploy software through APT, a local repository, or standard package-management tools. A Windows .exe cannot become a native Linux application by changing its package format; it must run through Wine or be replaced with a Linux build.

EXE and DEB formats

An EXE is usually a Windows Portable Executable (PE) program used by Windows software vendors and users. It can be an application binary, a self-extracting archive, or an installer made with Inno Setup, NSIS, InstallShield, WiX, Electron Builder, or similar tools.

A DEB is a Debian software package used by Debian, Ubuntu, Linux Mint, Pop!_OS, and related systems. It contains package metadata, files installed at defined paths, dependency declarations, and optional maintainer scripts; apt and dpkg can install, upgrade, verify, and remove it.

A DEB containing a Windows program is only a Wine wrapper package. The program remains Windows code and still needs a compatible Wine installation.

Use a native package when available

First check the publisher's site, the distribution repository, Flatpak, Snap, or the software project's release page for a Linux build. An official .deb, AppImage, Flatpak, or source build provides better desktop integration and avoids Wine-specific failures.

Do not use tools such as alien to convert a Windows installer: they do not translate Windows binaries into Linux binaries. No reputable online service can safely convert an arbitrary EXE into a meaningful native DEB, and uploading executable files to conversion sites creates security and privacy risks.

Package a Wine-compatible application

Only package an EXE after testing it manually with Wine. Install Wine from the target distribution, then run the program from a terminal:

sudo apt update && sudo apt install wine
wine /path/to/MyApp.exe

Package portable applications or files extracted from an installer, not the installer itself. For example, innoextract can unpack many Inno Setup installers, while 7z x setup.exe can inspect some self-extracting archives. Extraction is not guaranteed to reproduce an installer's registry changes, runtime installation, services, or drivers.

1. Create the package directories. Use a lowercase package name and a path without spaces.
   mkdir -p myapp-deb/DEBIAN myapp-deb/opt/myapp myapp-deb/usr/share/applications
2. Copy the tested EXE, DLLs, and required data files into the application directory.
   cp -a MyApp.exe data myapp-deb/opt/myapp/
3. Create myapp-deb/DEBIAN/control. Set the architecture to the Windows program's target architecture: use amd64 for a 64-bit x86 EXE and i386 for a 32-bit x86 EXE. Do not use Architecture: all merely because the package contains no Linux executable.
   Package: myapp
Version: 1.0
Section: utils
Priority: optional
Architecture: amd64
Depends: wine
Maintainer: Your Name <you@example.com>
Description: MyApp Windows application for Wine
4. Create myapp-deb/usr/share/applications/myapp.desktop for the application menu. This example assumes the EXE name and path contain no spaces.
   [Desktop Entry]
Name=MyApp
Exec=/usr/bin/wine /opt/myapp/MyApp.exe
Type=Application
Categories=Utility;
Terminal=false
5. Build and install the package.
   dpkg-deb --build --root-owner-group myapp-deb myapp_1.0_amd64.deb
sudo apt install ./myapp_1.0_amd64.deb

dpkg-deb is sufficient for a small local package. For repeatable distribution builds, Debian packaging tools such as debhelper or fpm can generate packages from a staged directory, but they do not solve Windows compatibility.

Dependency and compatibility limits

Confirm the Wine dependency name on the intended distribution with apt-cache show wine. Some releases or third-party Wine repositories use different package names, such as wine64, wine32, or WineHQ packages; declare dependencies for the distribution you actually support.

A 32-bit EXE on a 64-bit system may require 32-bit Wine support and the i386 foreign architecture. A 64-bit Wine prefix cannot run every 32-bit application, and a package built for i386 may require multiarch configuration before installation.

Wine cannot reliably support every Windows dependency. Programs that require kernel drivers, Windows services, hardware dongles, anti-cheat systems, device-specific software, unsupported .NET runtimes, DirectX features, or tightly controlled registry settings may fail even when installed in a DEB.

Do not run untrusted EXEs during package installation and do not create Wine prefixes in maintainer scripts. Wine prefixes are per-user configuration directories, so let each user initialize and configure the application at first launch.