Convert LNK to EXE

A deployment system, kiosk application, or third-party launcher may accept only .exe files while the available command is stored as a Windows shortcut. The practical result is a small EXE launcher that starts the shortcut’s target with the same arguments and working directory.

What LNK files contain

LNK is the Windows Shell Link format used by shortcuts on the desktop, Start menu, and other Windows locations. Explorer creates these files through New → Shortcut or Send to → Desktop (create shortcut).

An LNK can store a target path or shell item, command-line arguments, a working directory, icon location, window state, and volume or network information. It does not contain the linked application’s program code, so renaming Program.lnk to Program.exe cannot create a working executable.

Before recreating a shortcut, right-click it and open Properties → Shortcut. Record Target, Start in, any arguments shown in the target command, and the icon source. Treat unknown shortcuts as untrusted: they can start command interpreters, scripts, remote locations, or programs with hidden arguments.

What an EXE launcher is

An EXE is normally a Windows Portable Executable (PE) file containing native code or managed .NET code that Windows can load. A launcher EXE can start another program with fixed arguments, select a working directory, show an error when the target is missing, and carry an icon.

A launcher is useful where shortcuts are rejected or where the launch command should not be editable through the normal shortcut-properties interface. It does not include the original application unless that application is separately packaged, installed, or developed as part of the launcher.

Create a launcher with AutoHotkey

AutoHotkey v2 and Ahk2Exe are suitable for a simple Windows-only launcher. Install AutoHotkey v2 from its official site, create a script such as Example-launcher.ahk, and replace the paths and arguments with values from the shortcut.

#Requires AutoHotkey v2.0

target := "C:\Program Files\Example\Example.exe"
arguments := "--open project1"
workingDir := "C:\Program Files\Example"

Run '"' target '" ' arguments, workingDir

If the shortcut has no arguments, use Run '"' target '"', workingDir. Preserve quotation marks required by paths containing spaces; do not alter arguments unless you understand what the target program accepts.

Run the script first to verify its behavior. Then open Ahk2Exe.exe, select the .ahk file as the source, choose an output such as Example-launcher.exe, optionally select an .ico file, and compile it. Test the EXE by double-clicking it and from the distribution location, not only from the development folder.

Create a maintainable launcher with .NET

For launchers requiring logging, configuration, error messages, application detection, or enterprise signing, create a C# project in Visual Studio. Set ProcessStartInfo.FileName, Arguments, and WorkingDirectory, then build or publish the project through Build → Publish.

A normal .NET build may require the matching .NET runtime on the destination computer. Use a self-contained publish profile when that dependency is unacceptable, but expect a substantially larger output. Publishing a single file does not turn an unrelated LNK or target application into one self-contained executable.

Compatibility and security limits

The launcher works only if its target exists and can run on the destination system. Hard-coded paths often fail when the application is installed in a different location, under another user profile, or in a different 32-bit or 64-bit layout.

When distributing a launcher beside its target, use a fixed folder layout and resolve paths relative to the launcher. For installed software, prefer an installer, a configuration file, or application detection instead of embedding a machine-specific path.

A launcher cannot preserve the target EXE’s digital signature, bypass UAC, or grant permissions the target lacks. If the target requires elevation, Windows may still display a UAC prompt; do not design a launcher to bypass that protection.

New unsigned EXE files, including compiled script launchers, can receive Microsoft Defender or SmartScreen warnings. Sign production files with an organization’s code-signing certificate and distribute them through a managed or otherwise trusted channel.

Do not use online “LNK to EXE converters.” No web service can recover an application from a shortcut because the application is not stored in the LNK file. Uploading a shortcut can also disclose local paths, server names, arguments, and other embedded metadata; desktop tools are the appropriate option for this task.