As the person responsible for reporting the unwanted behaviour with Special Keys last year, I'm happy to take responsibility for the change that led to your current issue.

The fix done by the team solved a long-standing issue with unwanted behaviour affecting many developers / users when the use of special keys was disabled.

Specifically, problems can occur if special keys are disabled during development work. For example, unticking Allow special keys prevents the use of Ctrl+Break to stop code. This is intentional.

However it has the unintended side effect of preventing breakpoints and the use of Stop from pausing execution.

This means you cannot debug code for problems with the special keys option unticked. For full context to this issue, please see my article: https://isladogs.co.uk/breakpoint-special-keys/

By comparison, your usage seems very marginal / unusual

I'm confident wha\t you are seeing has nothing to do with Windows 11. That observation may be coincidental with the fix being applied in Access version 2305 (released on 1 June 2023)