Processing Ajax...

Title

Message

Confirm

Confirm

Confirm

Confirm

Are you sure you want to delete this item?

Confirm

Are you sure you want to delete this item?

Confirm

Are you sure?

User Image
quintus
2 discussion posts
On both Windows 10 and Windows 11, most keybindings involving the extra hidden function keys (F13-F24) work. However, some random ones fail to be bound due to conflict.

Not sure what conflict there would be, as neither Windows nor any programs use F13-F24 keys in shortcuts.
Jun 1, 2022  • #1
Keith Lammers (BFS)'s profile on WallpaperFusion.com
What's the error message that you get when you try to bind them?
Jun 2, 2022  • #2
User Image
Vasco Moura Esteves
3 discussion posts
On my Windows 10, I verified that when a window with elevated privileges is active the key F13 doesn't work.:o
Nov 13, 2022  • #3
User Image
Vasco Moura Esteves
3 discussion posts
I will try to better explain my case:
I use F13 as a hotkey in an AutohotKey script to execute some instructions. On Windows 7 it works flawless everytime.
On Windows 10 it works well if the active window is not elevated. If the active windows is elevated my AutohotKey script doesn't catch the F13 key because the script is not elevated.
Nov 16, 2022  • #4
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Ah yep, that makes sense. If they're at different integrity levels, Windows doesn't allow certain interactions.
Nov 18, 2022  • #5
Subscribe to this discussion topic using RSS
Was this helpful?  Login to Vote(-)  Login to Vote(-)