How to Lock Desktop EXE Apps on Windows 11
This guide is for traditional Windows desktop programs that launch from an .exe file. It shows how to find the real executable, require password approval or block launch, and verify that shortcuts and updates do not bypass the rule.
How do I lock a desktop program on Windows 11?
In GiliSoft EXE Lock, open Desktop Apps (EXE), add the program's real executable, then choose Password Verification to approve launches or Direct Block to stop them. Test the Start menu, shortcut, and direct EXE path. For Microsoft Store apps or Windows 11 Home policy choices, use the Windows 11 Home app-locker guide.
Check the app type before adding a lock
| What you need to control | Use this route | Check first |
|---|---|---|
| Traditional desktop EXE | EXE Lock Desktop Apps (EXE) | Find the installed executable, not just its shortcut |
| Microsoft Store or packaged app | Store Apps (UWP) guide | Confirm that the specific app is supported |
| Rules for different Windows users | Separate accounts or managed policy | Decide whether access should follow the person rather than one app |
| Private files opened by an app | File permissions or encryption | Blocking one program does not protect its documents |
For a broader comparison of Windows 11 Home options, see App Locker for Windows 11 Home.
Before locking a desktop application
- Set and verify the EXE Lock administrator password and recovery email.
- Test a nonessential program before applying the rule broadly.
- Identify the real EXE path and any secondary launcher or updater.
- Do not block Windows shell, sign-in, security, update, or recovery components.
- Decide whether authorized users should see a password prompt.
Lock a desktop EXE on Windows 11
- Prepare recovery.
Open EXE Lock, set its administrator password and recovery email, and test with a nonessential program first.
- Find the installed program.
If you start from a shortcut, use its file location or target to identify the real .exe. In Desktop Apps (EXE), select Add and choose that executable.
- Choose the launch policy.
In Lock Policy, use Password Verification when an authorized person may approve launch, or Direct Block when the program must not start.
- Test every route.
Try the Start menu, taskbar, desktop shortcut, file association, and direct EXE path. Check related launchers if the app uses more than one executable.
- Retest after updates.
Review blocked-attempt logs and check the rule again if an update changes the executable name, path, or launcher.
App-locking limits to understand
Locking an executable controls launching that program on the protected PC. It does not encrypt the program's documents, remove cloud access, or prevent an untrusted administrator from changing the computer. Use file protection and account security for the underlying data.
Frequently asked questions
Can I lock a Windows 11 app without uninstalling it?
Yes. Account controls, policy, or EXE Lock can restrict launching while leaving the application installed.
Can I put a password on a desktop app?
A dedicated EXE lock can show a password prompt for selected traditional desktop applications. Test the actual executable and every launch path.
Does locking a shortcut also lock the desktop program?
No. A shortcut only points to an app. Add the underlying executable in the Desktop Apps (EXE) list, then test the Start menu, shortcut, and direct EXE path.
What is the difference between Password Verification and Direct Block?
Password Verification permits authorized launch after a password. Direct Block prevents launch in that configured workflow.
Will the rule survive an application update?
It may require retesting if the executable name, path, launcher, or installation changes.