Windows 10: what to do if i want to make F13 as a modifier key

Hi,-I am making one keyboard for a large scale production, and i am adding one extra key which act as modifier like shift, ctrl, alt. Means in combination of that key i want to print some more characters example like shift+a=A, shift+ctrl+alt+a=Ā like this.-So instead of OEM key i have used F13 key, now i want to make F13 key as a modifier key, but i don't know how to do it, like do i need to make filter driver for this or can i make F13 as psudo-modifier from layout side?-I am trying to avoid making driver, because i know it is a challenging task, so please help me get out of this problem.-I

:)

 

Using F13-F24 Keys for Keyboard Shortcuts

I recently got a 12-key macro keypad where the keys are programmed to be F13 - F24. These keys are recognized by Windows 10 and I can use them with Autohotkey or with other programs that let you set shortcuts such as OBS. However, I can't set them as keyboard shortcuts when I'm in the properties menu of a shortcut icon. When I hit the F13 key, for example, it doesn't show anything in the shortcut field. Is there a workaround for this or a way to edit the shortcut icons so you can assign keyboard shortcuts to them that the menu doesn't allow?

 

How can I block Windows system functions, triggered by pressing, 'Windows Key' + F13-F24?

I'm using a Corsair Scimitar RGB Elite mouse with its accompanying Corsair iCUE software v.4.33.138. Thumb grid buttons 1-12 are assigned to F13-F24 using iCUE.

Within Windows 10 1809, certain mouse key combinations trigger unwanted actions:

• Windows key + F16 = slide to shutdown
  
• Windows key + F17 = some wacky minimization thing
  
• Windows key + F20 = mini screen clipper
  
• Windows key + F21 = opens the settings
  
• Windows key + F22 = projector menu
  

I want to block these from happening.

I've tried:

• AHK (AutoHotkey) v. 1.1.33.02
  
  
  • This code does NOT block 'Windows Key + F16' from triggering the system function listed above.
    
  • Using SC (scan codes) to target the key yields no use either. This example shows SC067, which represents F16.
    
  • To see the KeyHistory of the script directly above, after pressing 'Windows key + F16', see here.
    
• Disabling Corsair iCUE
  
  • Only if you use hardware assignments to the mouse using iCUE, will the thumb grid buttons continue to work when the software isn't running. The problem here is, F13-F24 aren't assignable to the hardware, they require the software, in order to be mapped to the mouse.
    
  • It's possible to remap 1-+, F1-12, or Numpad 1-Numpad+ to F13-F24, but this defeats the purpose of using F13-F24, as the purpose what to have a decoupled set of 12 keys that could be bound to the mouse. Remapping the other sets, either ruins their original functionality or adds complexity by requiring a state toggle using AHK.
    
• SharpKeys
  
• Key Remapper
  
• Key Manager
  
• KeyTweak
  
• Simple Disable Key
  
• X-Mouse Button Control
  
• Editing the DisabledKeys registry value to include F16. This is a Google Bard hallucination.
  

Microsoft PowerToys is a no-go. It requires Windows 10 v2004 (19041) or newer, a prerequisite I cannot meet. Installation attempts fail because of this reason.

Any solutions for blocking these unwanted functions? I'm trying to preserve F13-F24, but not trigger the unwanted functions when these keys are paired with the Windows key.

 

Are there any shortcuts using F13~F24?

I have never heard of any functionality linked to F13 - F24, since no keyboard actually has those keys, it may be some sort of anomaly you have found.