Direct Block
The selected app does not start. The user is not shown a password-release prompt.
- Block games on a shared or classroom PC
- Stop unapproved browsers or remote-access tools
- Keep administration and system utilities unavailable
GiliSoft EXE Lock User Guide
How to Lock Apps and EXE Files on Windows 11/10
Use GiliSoft EXE Lock to control desktop programs and supported Microsoft Store apps on a shared, family, classroom, or work PC.
- Lock traditional desktop EXE and supported Store/UWP apps
- Block app launches directly or require password verification
- Temporarily unlock apps and review blocked attempts
EXE Lock quick start
Start with one nonessential test app, confirm the result from the same Windows account that will use the PC, and only then add the remaining targets.
Set passwords and recovery email
Review the App Whitelist
Add desktop or Store apps
Choose the launch policy
Test the app and review logs
Choose what happens when a protected app is opened
The selected policy applies to the protected targets. Choose the launch result users should actually experience.
Password Verification
The app opens only after the correct release password is entered.
- Require approval before finance or business software opens
- Allow supervised access to selected applications
- Keep maintenance tools available to an authorized administrator
1. Configure passwords, recovery email, and the App Whitelist
Protect administration before adding lock rules
- Open Settings.
- Change the startup and release password from the default or trial configuration.
- Set an email address for password recovery.
- Review the App Whitelist and System Protected Items.
- Add approved desktop or Store apps that should never be placed on the lock list.
Do this first: confirm the password and recovery email before sharing the PC or enabling a large set of app rules.
Startup passwordControls access to EXE Lock management.
Release passwordApproves launches under Password Verification.
WhitelistKeeps trusted and system-sensitive apps away from lock rules.
Settings: passwords, recovery email, user whitelist, and system-protected items2. Add traditional Windows desktop EXE applications
Desktop Apps: add traditional programs and verify the executable pathProtect the executable that actually launches the program
- Open Desktop Apps (EXE).
- Click Add, or use the supported drag-and-drop area.
- Select the program executable or shortcut target.
- Confirm the displayed application name and full path.
- Select the app and apply the intended launch policy.
Some applications use a launcher and a separate main executable. Test the normal shortcut after adding the target to confirm that the correct process is protected.
3. Add Microsoft Store and UWP applications
Use the dedicated Store Apps list
- Open Store Apps (UWP).
- Find the supported Store app target in the detected list.
- Select one or more apps intended for protection.
- Apply the same Direct Block or Password Verification policy.
- Test the app from its normal Start menu entry.
Store/UWP apps use package identities and protected Windows locations, so they should be managed from this dedicated section rather than added as ordinary desktop EXE files.
Store Apps: manage supported modern Windows app targets separately4. Apply Direct Block or Password Verification
Lock Policy: choose the launch behavior applied to protected targetsUse one clear rule for the selected targets
- Open Lock Policy.
- Choose Direct Block when no launch should be permitted.
- Choose Password Verification when authorized users may release an app.
- Save the policy and return to the app list.
- Launch one protected app to verify the expected behavior.
Test with the Windows account that will use the PC. A successful administrator test does not replace testing the ordinary user experience.
5. Verify protection, use Temporary Unlock, and review logs
Confirm results from the Dashboard
- Check that Protection Status is Running.
- Review the number of protected Desktop Apps and Store Apps.
- Test a protected application and check Blocked Attempts.
- Use Temporary Unlock for maintenance or approved short-term access without deleting the target rules.
- Review Recent Intercept Logs and the full Logs area for process, action, time, and result.
Logs help distinguish a working block rule from an incorrect target path and provide evidence when a trusted application needs an exception.
Dashboard: protection status, target counts, Temporary Unlock, and recent eventsApply app rules without locking the wrong program
Add targets gradually. This makes launcher paths, Store app identities, password behavior, and whitelist exceptions easier to verify.
Protect management with a password
Add the recovery email
Confirm trusted whitelist entries
Add one nonessential test app
Verify the launch result and logs
More Windows app locking guides
Choose the guide that matches the type of app, Windows edition, or access rule you need to configure.
Lock desktop and Store apps
Password protect an EXE file on WindowsLock desktop apps on Windows 11Lock Microsoft Store appsLock apps with a password on a Windows PCBlock programs for other users
Block programs from running on WindowsPrevent users from opening programsBlock games on a Windows PCWindows 11 and AppLocker options
App locker for Windows 11 HomeAn easier AppLocker alternative for WindowsProduct and purchase information
GiliSoft EXE Lock features and screenshotsCompare EXE Lock license optionsEXE Lock troubleshooting and FAQ
Why can a protected desktop app still open?
Confirm the exact executable path. The shortcut may start a launcher while the main application runs from another EXE file.
Why can I not find a Microsoft Store app?
Refresh the Store Apps list and confirm the application is installed for the Windows account. Only supported detected Store/UWP targets appear there.
What if an app update changes its path?
Review the displayed target after major updates. Remove an outdated entry and add the current executable or package target if needed.
How do I release apps temporarily?
Use Temporary Unlock from the Dashboard for maintenance or approved access, then restore normal protection without rebuilding the app list.
What if a trusted application is blocked?
Use the event details to identify the process, remove it from the protected target list where appropriate, or add it to the App Whitelist.
What if the release password is forgotten?
Use the configured recovery email path. Set and verify that email before relying on Password Verification on a shared PC.
Lock selected apps without changing Windows accounts
Manage desktop EXE and supported Store/UWP targets with direct blocking, password release, temporary unlock, whitelisting, and activity records.
