Autohotkey windows 10 не работает

Fix for AutoHotkey Not Working in Windows 10

UAC rules have changed with Windows 10.

AutoHotkey scripts that worked fine in Windows 7 no longer work in Windows 10.

1) Find your AutoHotkey executable, typically here: C:\Program Files\AutoHotkey\AutoHotkey.exe

2) Right-click on AutoHotkey.exe

3) Select the Compatibility tab

4) Enable Run this program as Administrator

Note you have to do this even though you are running as an Administrator.

This caused me to go back to Windows 7 until I could figure it out. Gamer, I need my scripts! Very frustrating. Hope this helps others.

Re: Fix for AutoHotkey Not Working in Windows 10

No, the UAC rules changed with Windows 8. In Windows 8.1 and 10 the rules remain the same as in Windows 8.

If UAC is enabled in any version of Windows, most programs do not run as administrator by default, even if you are an administrator. That is basically the purpose of UAC. Your instructions would apply to any system with UAC enabled. The difference between Vista/7 and 8/8.1/10 is that in the latter, the «Never notify me» setting in Control Panel doesn’t actually disable UAC, just the Yes/No prompts.

I would generally not recommend running every script (or program) as administrator. Any programs that the script launches will also run as administrator. If you just need to automate windows of programs running as admin, you can use EnableUIAccess instead.

Re: Fix for AutoHotkey Not Working in Windows 10

This is incorrect. Even with UAC off you need to run AutoHotkey as an administrator.

If there’s another method, let’s hear it.

Re: Fix for AutoHotkey Not Working in Windows 10

Right back at you. You are incorrect. If you have any facts to back up your claims, let’s hear them.

1. AutoHotkey does not need to be run as administrator. I frequently run it as a limited user. By default it can only automate windows which are not running as administrator (due to security restrictions), but if you use EnableUIAccess as I said, it can automate any window even while running as a limited user. Specific scripts might still need to be run as administrator, such as if they write to the Program Files directory; but the majority of scripts do not.
2. If UAC is disabled and the current user is an administrator, every program run by that user gets administrative privileges.

On Windows Vista at least, you can’t even turn on the option if UAC is disabled. If you temporarily disable UAC, turn on the option and re-enable UAC, there will be a tick in the box but the box itself will be disabled and the setting will have no effect. Even «Run as administrator» from the context menu just runs the script normally — without admin if the user isn’t an admin.

If you are using Windows 8 or later, it is very unlikely that you have UAC disabled. On Windows 8 and later, UAC can only be disabled by modifying the registry, and doing so breaks apps. As I said, «turning off» UAC in Control Panel on Windows 8 and later just suppresses the Yes/No prompts; programs are still run with limited privileges by default.

Supposedly turning off «admin approval mode» has a similar effect to disabling UAC, but I haven’t tried it and wouldn’t recommend it either.

AutoHotkey в Windows 10 — горячие клавиши не работают в некоторых приложениях

Простой скрипт, как

раньше работал нормально под Windows 7. Теперь, когда я обновился до Windows 10, он не работает, когда некоторые окна активны. Специально LButton -Hotkeys может все испортить, приводя к ситуации, когда вам действительно нужен диспетчер задач.

Вот небольшой список приложений, в которых горячие клавиши больше не распознаются: (вместо вышеприведенного скрипта отправляется простой a )

Где это работает: (примеры)

• редактор
• Skype
• Приложения для Windows в целом
• Ахк помогите
• Открытый офис
• (большинство программ)

Может кто-нибудь воспроизвести это?

Что не так с AutoHotkey в Win10?

Как это можно исправить?

(Версия AHKscript 1.1.22.3, 64-разрядная версия Unicode)

4 ответа

В связи с тем, что Windows 10 была только что выпущена, это очень актуальный вопрос, и я уверен, что многие пользователи оценят помощь в правильной работе своих скриптов на этой новой ОС. Возможно, кто-то подумал, что этот вопрос носит широкий характер или может быть неправильно классифицирован, так как это проблема Windows, а не конкретная проблема AutoHotkey?

Насколько я понимаю, проблема заключается в новых настройках UAC. Простое решение — запустить ваш скрипт от имени администратора. Для этого щелкните правой кнопкой мыши файл -> выберите «Запуск от имени администратора».

У меня нет прямого ответа на вопрос о запуске приложения или файла в качестве администратора (в Windows 10), но я обнаружил, что это руководство охватывает все возможные способы сделать это в Windows 10.

Другой альтернативой является проверка скрипта, работает ли он от имени администратора, а если нет, то от перезагрузки от имени администратора. Код был извлечен из файла справки:

AutoHotkey in Windows 10 — Hotkeys not working in some applications

A simple script like

used to work fine under Windows 7. Now that I upgraded to Windows 10, it isn’t working when certain windows are active. Specially LButton -Hotkeys can mess up everything, leading to the situation where you actually need Task Manager.

Here is a small list of applications in which hotkeys are not recognized anymore: (instead, as of the above script, a simple a is sent)

Where it does work: (examples)

• Editor
• Skype
• Windows Apps in general
• Ahk help
• Open Office
• (most programs)

Can someone reproduce this?

What’s wrong with AutoHotkey in Win10?

How can this be fixed?

(AHKscript vers. 1.1.22.3 Unicode 64-bit)

5 Answers 5

Being that Windows 10 was just released, this is very relevant question and I’m sure that many users will appreciate help in getting their scripts to run properly on this new OS. It’s possible someone thought that this question was to broad in scope or maybe improperly classified, as it’s a Windows issue rather than a specific AutoHotkey problem?

From my understanding the issue lies in new UAC settings. A simple solution is to run your script as an Administrator. To do this right click on the file -> select «Run as Administrator»

I don’t have a direct answer to give regarding running an application or file always as an Admin (in Windows 10), but this guide I found seems to cover every way possible to do so in Windows 10.

Another alternative is to have the script check if it is running as Admin, if not reload as Admin. Code was pulled from the Help File: