Differences

This shows you the differences between two versions of the page.

--- assistance:Accessibility_Permission_Problem [2018/07/31 01:21] – Mojave (Developer Betas 1-4 / Public Betas 1-3) peternlewis
+++ assistance:Accessibility_Permission_Problem [2025/06/30 06:45] (current) – peternlewis
@@ Line 3: / Line 3: @@
 Accessibility access to control your computer is required to use many features including selecting menu items, manipulating windows, pressing buttons, typed string triggers and the window switcher.
-You will need to enable Accessibility permissions for both Keyboard Maestro and Keyboard Maestro Engine.
+You will need to enable Accessibility permissions for both Keyboard Maestro and Keyboard Maestro Engine. This is not something Keyboard Maestro can work around - it is a security feature of macOS.
-On modern macOS, you enable Accessibility permissions by opening System Preferences, going to the Security & Privacy preferences, and in the Privacy pane select Accessibility and ensure that both Keyboard Maestro and Keyboard Maestro Engine are ticked.
+On modern macOS, you enable Accessibility permissions by opening System Settings, going to the Privacy  & Security preferences, and in the Accessibility and ensure that both Keyboard Maestro and Keyboard Maestro Engine are ticked. On some systems, you may get results by unticking and reticking these permissions.
-(!) Note that for Mojave (Developer Beta 5 / Public Beta 4) you may need to relaunch the Keyboard Maestro Engine or make any change to your macros after enabling accessibility.
+In Big Sur and later, as well as the Accessibility permissions, you will need to check the Input Monitoring permissions. If Keyboard Maestro or Keyboard Maestro Engine is listed there, you must ensure it is enabled. Input Monitoring permissions can override accessibility permissions.
-(!) Note that OS X Yosemite (10.10 GM1 through 10.10.2) has a serious problem adding applications to the accessibility pane properly. This bug was largely resolved in Yosemite 10.10.3. So if you are having problems with accessibility under Yosemite, upgrade to 10.10.3 or later, and then launch Keyboard Maestro.
+If you cannot enable the Accessibility permissions you can try removing Keyboard Maestro Engine from the Accessibility permissions, and then quit and relaunch the Keyboard Maestro Engine (in Keyboard Maestro, File ➤ Quit Engine, File ➤ Launch Engine) to re-add it, and then you should be able to enable it.
-If you continue to have problems with enabling Accessibility permissions, ensure you only have one copy of Keyboard Maestro on your Mac and restart and try again.
+If Keyboard Maestro or Keyboard Maestro Engine are not listed in the Accessibility list, try restarting each of them. In Keyboard Maestro, choose File ➤ Quit Engine, File ➤ Launch Engine to restart the Keyboard Maestro Engine. Then quit and relaunch Keyboard Maestro. If that does not work, try Restarting and repeat the process. Failing that, you can drag the Keyboard Maestro.app in to the list, or control-click on the Keyboard Maestro.app, and select Show Package Contents, Contents, MacOS and then drag the Keyboard Maestro Engine.app in to the list.
-If you continue to have problems, [[https://support.keyboardmaestro.com/|contact support]].
+If you continue to have problems with enabling Accessibility permissions, ensure you only have one copy of Keyboard Maestro on your Mac, that it is in the /Applications folder, that you moved it there **using the Finder** and restart and try again.
-** Historic Mojave Beta information which will be removed when Mojave is released **
+If you continue to have problems, you can use the `tccutil reset Accessibility` command to reset the Accessibility permissions.
-Note that OS X Mojave (Developer Betas 1-4 / Public Betas 1-3) has a serious problem adding accessibly for Keyboard Maestro Engine.  Specifically after it is added, you can click the checkbox but it wont necessarily turn on.  Resolve this by deleting the Keyboard Maestro Engine entry from the Accessibility list and relaunching Keyboard Maestro Engine (Keyboard Maestro File ➤ Quit Engine, File ➤ Launch Engine), and then you can check the checkbox to enable accessibility permissions.
+Failing all that, and having Restarted your Mac and tried the processes again, you can try reinstalling the Keyboard Maestro.app, which may poke the security system enough to make it work. Ensure you only have one copy of Keyboard Maestro on your Mac, that it is in the /Applications folder, then reinstall Keyboard Maestro by:
-Note that OS X Mojave (Developer Betas 1-4 / Public Betas 1-3) has a further serious issue in that even after it claims to have enabled accessibility permissions, the system may still be refusing to allow access to the event queue (symptoms include not being able to set hot keys and typed keystrokes not working (including Command-V for paste)).  Restarting your Mac seems to resolve this.
+* Quit Keyboard Maestro and Keyboard Maestro Engine
+* Download a fresh copy from [[https://download.keyboardmaestro.com/|our web site]].
-Note that OS X Mojave Beta 4 (Developer Betas 4 / Public Betas 3) will not grant Keyboard Maestro Engine.app accessibility permissions while it is within the Keyboard Maestro.app bundle, so the only way to run the Keyboard Maestro Engine.app with accessibility permissions in beta 4 is to copy the Keyboard Maestro Engine.app out of the bundle and launch it manually.  Note that Keyboard Maestro (editor) will relaunch the “correct” version of Keyboard Maestro Engine every time it is launched, so you will have to relaunch the Keyboard Maestro Engine.app each time you launch Keyboard Maestro.app.
+* If the file is still a .zip file, unzip it.
+* **Use the Finder** to move the resulting Keyboard Maestro.app application to the Applications folder (replacing the old version).
+* Launch the Keyboard Maestro app from the Applications folder.
+If you continue to have problems, [[https://support.keyboardmaestro.com/|contact support]].