Hyper Key cannot be set for internal (built-in) MacBook keyboard on MacOS 26.4 Beta 1

[callisco]

This may be a bug with MacOS 26.4 Beta 1 which was released yesterday, but the reason I’m opening a topic is that it maybe due to some intended change Apple made that BetterTouchTool may need to address.

On an internal keyboard, pressing a Hyper bound-key, in my case Caps Lock, does not register. So if you were to press Caps Lock + a, only the letter a would register.

On an external keyboard, it works as expected.

I’ve also tried Raycast and it has the exact same issue:

• Type of Mac: MacBook Pro M4 Max
• macOS version: 26.4 Beta 1
• BetterTouchTool version: 6.198 (2026021703)

[Andreas_Hegenberg]

I will install the beta on some machine soon.

Could you try to remap caps lock to "No Action" in System Settings => Keyboard => Keyboard Shortcuts => Modifier Keys

And then check whether the key still produces events in BTT's key sequences recorder?

It's possible Apple is further restricting access for third party apps

[Andreas_Hegenberg]

An good alternative to a hyper key you could use for now:

Remap Caps Lock to e.g. right control in BTT's Automations, Named & Other Triggers section:

Then use the "Differentiate Left / Right Modifier Keys" Option in BTT:

[callisco]

Caps Lock set to No Action:

Pressing Caps Lock on an internal keyboard does not register at all.

In fact, nothing is registered even when the Caps Lock is set to the default Caps Lock function.

May be of interest to you - when I set No Action for an external keyboard, Key Sequence still gets captured correctly.

[Andreas_Hegenberg]

Ok, then I at least know what they changed. Not great, but I think I'll be able to create a workaround. It might also just be a bug (actually sounds a bit like that)

[Andreas_Hegenberg]

//edit February 23: this is not necessary anymore, update to the latest BetterTouchTool alpha to make the default hyperkey work again.

---

I guess you could also remap the caps lock key to some right modifier key like mentioned above and then create a custom hyper key like this:

[callisco]

@Andreas_Hegenberg

Thanks for the suggestion, it worked!

I remapped Caps to Right Control.

And then made two sequences.

[wynstaxxx]

Yeah this is an ISSUE facing all keyboard changing apps i.e. Karbiner Elements or Hyperkey app etc. But I use KE for hyperkey and some other keyboard changes because its able to get closer to metal aka deeper integration by way of using kexts etc and even with that it is broken on 26.4 beta update just for the system keyboard. Interestingly external keyboards work fine apparently so something must have dramatically changed. Hope.a fix is figured out ASAP because I rely on some off those keyboard quality of life enhancements and right now most are not working-a few i was able to recreate similar to above for hyperkey but others probably not possible. Ironically when Karabiner failed I was thought “bummer” but ill just use BTT hyperkey integration till fix, unfortunately BTT is plagued by same problem

this is what is posted on KE’s website right now

Caution regarding the latest macOS beta (26.4)

In macOS 26.4 Beta, we have confirmed an issue where key presses on the MacBook's built-in keyboard are not remapped and are entered as-is. (External keyboards remap key events correctly.)
We're currently working on a fix.

[Andreas_Hegenberg]

sounds like Apple is actively blocking this. We should all send feedback to Apple about it. They did similar stuff for the trackpad a few versions ago.

For BTT the only affected function should be the hyperkey, but that can be worked around. For Karabiner Element this change is really bad.
Key remapping in BTT (even low level) should still work.

[Andreas_Hegenberg]

Here is the issue being discussed at karabiner elements: Karabiner Elements stops working on internal keyboard on MacOS 26.4 beta 1 · Issue #4402 · pqrs-org/Karabiner-Elements · GitHub also with some examples on how to report it to Apple. The more people send feedback about this, the more likely Apple is to undo the restriction.

[garrattg]

@Andreas_Hegenberg

discussed at karabiner elements

As a heads up, this worked for me too but the caps lock stuck, so i had to run this:

hidutil property --set '{"CapsLockDelayOverride":0}'

[garrattg]

And I created a launch agent so its stays on restart.

[Andreas_Hegenberg]

@garrattg what worked for you?

[iandol]

@garrattg

this worked for me too

I also didn’t really see a solution, apart from hidutil fixes that only apply to single key swaps (i.e. how can we get hyperkey back with hidutil?) For everyone affected, please use Feedback Assistant or your developer acounts to report this inconvenience.

Karabiner Elements stops working on internal keyboard on MacOS 26.4 beta 1

Root cause: macOS 26.4 beta introduced com.apple.iohid.protectedDeviceAccess, which completely blocks IOHIDDeviceOpen (even with kIOHIDOptionsTypeNone) for the Apple Internal Keyboard connected via SPI transport (AppleHIDTransportHIDDevice). External keyboards (USB, BLE) are unaffected.

Workaround — CGEventTap fallback:

It seems there is a workaround with more limited flexibility…

[Andreas_Hegenberg]

I have a workaround that will be fine for Hyperkey, I'll implement a first version today. BTT's low level key remap also still works fine and BTT is already using the CGEventTap fallback that is being discussed in the Karabiner Elements issue.

So for BTT the issue is not critical right now but it paints a dark future for macOS system tools in general.

[Andreas_Hegenberg]

I have added support for 26.4 beta 1 hyper key in BetterTouchTool 6.205 alpha. However I wasn't able to verify it yet because I broke my beta machine

Would be great if any hyperkey users on 26.4 beta 1 could test it.

[Illyrian]

The latest alpha update fixed the hyper key for me on MacOS 26,4 beta 1.

[iandol]

Also working for me, awesome support as always Andreas!!!

Let’s hope Apple are not over-tightening restrictions on macOS going forward…

[ShailAntani]

Not sure why its not working for me in the latest update (6.206) as well.
Here’s the screenshot of what I have:

I tried pressing “Caps Lock” + “M” But that didn’t increase the brightness.
Could that be because of the above issue?

[Andreas_Hegenberg]

only if you are on macOS 26.4 beta 1. Does the brightness up action work in general for your display?