Need the exact folder where an application is installed? This guide shows every reliable way to locate a program's executable file, copy its full path, and avoid confusing shortcuts with real EXE files.
Most Windows applications are started by an executable file with the .exe extension. Finding this file is useful when you need to create a firewall rule, add a program to antivirus exclusions, repair a shortcut, run the app as administrator, check whether a file is legitimate, or manually copy a program path.
There is no single universal location for all EXE files. Traditional desktop applications are usually installed in C:\Program Files or C:\Program Files (x86), portable programs can run from almost any folder, and Microsoft Store apps use protected system directories. The fastest method depends on whether the program is running, pinned to Start, available as a shortcut, or installed as a Store app.
.lnk extension and only points to the real EXE file. To find the real executable, open the shortcut properties and check the Target field.
If the program has a desktop shortcut, you can find the executable path from its properties. This is one of the most reliable methods for traditional Win32 applications.
A typical target path looks like this:
If the path contains extra text after the closing quotation mark, that text is usually a command-line argument. For example, a browser shortcut may include startup parameters. The EXE path is the part inside the quotation marks.
If the application is currently running, Task Manager is often the best tool because it can show the executable behind an active process.
Windows will open File Explorer in the folder that contains the executable file used by that running process.
Some programs use several processes. To see the exact executable name, right-click the column header in Task Manager, enable Process name or Command line, and check which .exe file is being launched.
C:\Windows, C:\Program Files, or application folders just because you found them in Task Manager. Deleting executable files manually can break programs or Windows components.
If you know the program name but cannot find it from Start or Task Manager, use File Explorer search. This method is helpful for portable apps, old software, or programs installed outside the default folders.
Useful search examples:
For faster results, search first in common installation folders:
C:\Program FilesC:\Program Files (x86)C:\Users\YourName\AppData\LocalC:\Users\YourName\AppData\RoamingAppData folder is hidden by default. To open it quickly, press Win + R, type %localappdata% or %appdata%, and press Enter.
Windows Settings can help identify the app, its publisher, and sometimes provide advanced options. However, Settings does not always show the direct EXE path for every program.
This method is more useful for Microsoft Store apps and modern apps than for classic desktop programs. For a direct EXE path, the Start menu, shortcut properties, or Task Manager usually works better.
Command-line tools are useful when you need the exact path for scripts, troubleshooting, or administration. They work best when the program is included in the system PATH environment variable.
cmd, and press Enter.where chromeYou can also include the extension:
where chrome.exeIf Windows can find the executable through the PATH variable, it will show a full path such as:
Get-Command notepad.exeTo show only the executable path, run:
(Get-Command notepad.exe).SourceFor software that is not in PATH, PowerShell may not return a result. In that case, use Start menu search, Task Manager, or File Explorer search instead.
Microsoft Store apps are different from traditional desktop programs. Many of them are installed in the protected WindowsApps folder:
This folder is hidden and access is restricted even for administrator accounts. Changing permissions manually is not recommended because it can break Store apps, updates, or Windows app registration.
If you need to launch or reference a Store app, it is usually better to use its Start menu entry, app execution alias, URI protocol, or package name rather than manually editing files inside WindowsApps.
Some Store apps and developer tools create command aliases. To check them:
This usually happens with Microsoft Store apps, system components, web shortcuts, or special app entries that do not point to a normal desktop executable. Try Task Manager if the app is running, or check the app's settings and installation type.
You may be looking at the Start Menu shortcut folder. Right-click the shortcut inside that folder and select Open file location again, or open Properties and check the Target field.
Portable programs do not always register in Windows. They can be located in Downloads, Documents, Desktop, another drive, or a custom folder. Use File Explorer search for *.exe or search by the program name.
Some apps install per user under AppData\Local or AppData\Roaming. Examples include auto-updating apps, messengers, launchers, and utilities. Use %localappdata% and %appdata% in the Run dialog to check these folders quickly.
If you found an unknown EXE in a temporary folder, Downloads folder, or an unusual path, do not run it. Check its digital signature, scan it with Windows Security, and verify whether it belongs to a known application before allowing it through a firewall or antivirus exclusion list.
C:\Program Files\....C:\Program Files or C:\Program Files (x86). Some per-user applications install under C:\Users\YourName\AppData\Local or C:\Users\YourName\AppData\Roaming.
C:\Program Files\WindowsApps. This folder is protected because it contains Microsoft Store app packages and system-managed app files.
Finding the location of a program's EXE file in Windows is straightforward once you choose the right method. For a running app, Task Manager is the fastest option. For an installed desktop program, the Start menu or shortcut properties usually gives you the exact path. For portable or hard-to-find tools, File Explorer search, Command Prompt, and PowerShell can help.
Always distinguish between a shortcut and the real executable file, keep full paths in quotation marks when using them in commands, and avoid modifying protected folders unless it is absolutely necessary.