Windows 11 blocking my trusted AutoIt scripts from running

Your AutoIt scripts are likely being intercepted by Smart App Control or Reputation-based protection, which act as higher-level security filters that often ignore standard antivirus exclusions. If you have Windows 11 Home which lacks the Group Policy Editor, you would need to manage these blocks through the Windows Security interface or specific file-level attributes.

The most common cause for a silent block on a fresh Windows 11 installation is Smart App Control. This feature blocks apps that are unsigned or have low reputation without always providing a clear notification. To check this, open Windows Security, navigate to App and browser control, and select Smart app control settings. If it is set to On, it will block most AutoIt scripts by default because they lack a digital signature from a known CA. Note that if you turn this feature Off to test your scripts, you cannot turn it back on without a full factory reset of Windows.

If Smart App Control is already off or in Evaluation mode, the next culprit is Reputation-based protection. Within the same App and browser control menu, click on Reputation-based protection settings and look for the Check apps and files toggle. This uses Microsoft Defender SmartScreen to prevent unrecognized apps from starting. Try toggling this off temporarily to see if your scripts execute. If they do, you should avoid leaving this protection off globally; instead, ensure you are running the scripts from a directory that is not synced to a cloud service like OneDrive, which can sometimes re-apply security flags to files.

At the individual file level, Windows 11 Home frequently applies the Mark of the Web to scripts, especially those edited or moved between folders. Right-click your .au3 or compiled .exe file, select Properties, and look for an Unblock checkbox at the very bottom of the General tab. If you have many scripts, you can unblock an entire folder at once using PowerShell as an administrator. Open PowerShell and run the following command to strip the block attribute from all files in a specific directory:

gci "C:\Your\Scripts\Path" | Unblock-File

Finally, if you are running compiled AutoIt scripts, the compilation process itself often triggers heuristic detections. If you have already added the folder to the Exclusion list in Virus and threat protection but the block persists, ensure you have also excluded the specific process. In the Exclusions menu, click Add an exclusion, select Process, and type the exact name of your compiled executable. This tells Defender to stop monitoring the behavior of that specific running program, which is often more effective than a simple folder exclusion for AutoIt's automation-style activities.

If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

hth

Marcin