If Sliprail runs with standard permissions while the active app runs as an administrator, Windows may prevent Sliprail's global shortcut from working.
Sliprail includes a built-in Run as Administrator option under Advanced Settings. If you need Sliprail to work reliably while elevated windows are active, start with this setting.
Windows isolates apps by privilege level. Development tools, terminals, Registry Editor, and other system utilities may run with administrator privileges. A standard-permission app cannot always interact with those elevated windows or receive global keyboard input while they are active.
Typical symptoms include:
Windows determines an app's privilege level when it starts. Open at Login does not elevate Sliprail by itself. If Sliprail starts normally, it may not receive the keyboard shortcut while an administrator-level window is active.
After Run as Administrator is enabled, Sliprail requests administrator privileges on future launches, including startup after sign-in.
This is the most direct solution and works well for temporary situations.
Steps:
Yes when the UAC prompt appearsAdvantages:
Disadvantages:
If you are already using a version that includes this option, this is the recommended solution to try first.
Steps:
SettingsAdvanced SettingsAfter you enable it, Sliprail requests administrator privileges on future launches, which usually resolves shortcut problems while elevated windows are active.
Advantages:
Important Notes:
A simple rule of thumb:
Running any application with administrator privileges increases security risk. Make sure that you:
When Sliprail cannot respond while an elevated window is active, the usual cause is a privilege mismatch. Enable Run as Administrator for a long-term fix, or launch Sliprail as an administrator manually when you need a temporary solution.
Choose the approach that best matches your workflow, and Sliprail's keyboard shortcuts should work normally again on Windows.