[Fix] AutoIt Error "Line 0: Error Opening the File" on Windows

The "AutoIt Error, Line 0, Error opening the file" box means a program built with AutoIt starts with Windows and looks for a script file that is no longer there. Nothing is wrong with Windows itself. Find the startup entry that still names that file with Microsoft's free Autoruns tool and delete it, then run a full malware scan.

Facts checked on 15 October 2026. Steps written for Windows 11 (25H2 and 26H2) and Windows 10 22H2.

What AutoIt Error "Line 0: Error opening the file" means

AutoIt is a free scripting language for automating Windows. A program written in it reads a script file and runs it line by line. The box you see is how one such program reports that it could not open its script at all. In a report on Microsoft Q&A the full text reads:

AutoIt Error
Line 0 (File "C:\Users\Public\bin.au3"):
Error: Error opening the file.

• AutoIt Error is the window title. Every AutoIt program uses it, whatever the program is called.
• Line 0 means no line of the script ran. The program stopped before it read anything.
• File and the path in quotes is the script it looked for. This path is your best clue: it tells you which entry to delete.
• Error opening the file means the file is missing, moved or locked, so it could not be opened.

The file name changes from PC to PC. Besides .au3 scripts, readers see odd extensions such as .bui in a folder with a random name, as in a 2018 thread on the AutoIt forum. The same steps apply to every spelling.

Why the AutoIt Line 0 error appears: causes ranked

AutoIt developers on their own forum said the program is likely a compiled script, an .exe that carries AutoIt inside, so you will often find no AutoIt installed at all. What matters is what starts it.

Where the program that shows the box is started from

Windows can start a program at sign-in from several places. Microsoft's support answer names the Run keys in the registry and the C:\Users\Public folder. The AutoIt team adds startup items and any file that mentions the script name. Autoruns covers all of them in one window.

• Run keys: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run and the same path under HKEY_LOCAL_MACHINE.
• Scheduled tasks: a task in Task Scheduler, often with a random or harmless-sounding name. A box that returns every few minutes almost always comes from here.
• Startup folders: shell:startup for your account and shell:common startup for all users.
• The files: the launcher .exe and the rest of its folder, often next to where the missing script was.

How to fix AutoIt Error Line 0: Error opening the file

Fix 1 finds the entry wherever it is and works for most readers. Fixes 2 and 3 do the same by hand if you cannot run Autoruns. Fixes 4 and 5 clean up what the program left behind. Fixes 6 to 8 are for a box that survives all of that.

Fix 1. Find and delete the startup entry with Autoruns

5 to 10 minutesLow riskEveryone who sees the box. This is the quickest way to find the entry, wherever Windows keeps it.

Microsoft's Autoruns lists Run keys, scheduled tasks, startup folders and services in one window and can search them all. Typing the file or folder name from the box shows exactly the entry that still starts the missing script.

1. Click OK on the box and write down the full path it shows, for example C:\Users\Public\bin.au3.
2. Download Autoruns from Microsoft's Sysinternals page at learn.microsoft.com/sysinternals/downloads/autoruns (version 14.3, about 3 MB).
3. Extract the ZIP file, right-click Autoruns64.exe and choose Run as administrator. Accept the licence.
4. Wait until the scan finishes, then type the file name without its extension (bin) or the random folder name (cedmw) into the filter box at the top.
5. Check the Logon and Scheduled Tasks tabs. Note each line whose command or path contains that name.
6. Right-click each matching line and choose Delete. Clearing its check box only disables it.
7. Clear the filter and also look for lines with .au3 or AutoIt3 in the command. Delete those you did not set up yourself.
8. Restart the PC.

Fix 2. Remove the Run entry in Registry Editor

5 minutesRead the warningYou cannot use Autoruns, or Autoruns showed the entry under a Run key and you want to check it yourself.

Microsoft's support answer for this exact box points to the two Run keys: Windows reads them at every sign-in and starts whatever they list, including a launcher whose script is gone.

1. Press Win + R, type regedit and press Enter. Click Yes.
2. Click File > Export, choose Selected branch or All, name the file and click Save.
3. Paste this path into the address bar at the top and press Enter:

   HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run

4. In the Data column, look for a value that points to the path from the box, to C:\Users\Public, or to an .exe in a folder with a random name.
5. Right-click that value, choose Delete and click Yes.
6. Repeat steps 4 and 5 for the same key for all users:

   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

7. Close Registry Editor and restart the PC.

Judge a value by its Data, not its name. The earlier version of this page listed names like "Windows Update" or "Google Chrome" to delete. A launcher can borrow such a name, but your real Chrome or OneDrive may also be there, so delete only a value whose path matches the box.

Fix 3. Check Task Scheduler, startup apps and the Startup folders

10 minutesLow riskThe box returns every few minutes, or the path names a program you once used.

A box that comes back while you work is started on a timer, which only a scheduled task does. A box only at sign-in may also come from a shortcut in a Startup folder or a startup app.

1. Press Win, type Task Scheduler and open it. Click Task Scheduler Library.
2. Click each task outside the Microsoft folder and open its Actions tab. Look for the path from the box, an .exe in a random folder, or C:\Users\Public.
3. Right-click a matching task and choose Delete, then click Yes.
4. Press Ctrl + Shift + Esc. On Windows 11 open Startup apps, on Windows 10 the Startup tab. Right-click any unknown entry and choose Open file location to see where it lives.
5. Select an entry that points to the leftover folder and click Disable.
6. Press Win + R, type shell:startup and press Enter. Delete any shortcut that points to the leftover folder.
7. Repeat step 6 with shell:common startup, then restart.

Fix 4. Delete the leftover folder and launcher

5 minutesLow riskAfter Fix 1, 2 or 3, when the folder from the box or a random folder in your user profile is still on the disk.

The launcher that shows the box often sits next to the missing script. Removing it means nothing is left that a forgotten entry could start again.

1. Open File Explorer and click View > Show > Hidden items on Windows 11, or tick Hidden items on the View tab of Windows 10.
2. Open the folder from the path in the box, for example C:\Users\Public or C:\Users\<your name>\<random folder>.
3. Look for .au3 files, .exe files you did not install, and files with odd extensions or random names.
4. If Windows says a file is in use, press Ctrl + Shift + Esc, find the process with the same name on Processes or Details, and click End task.
5. Delete the random folder, or the odd files in C:\Users\Public, and empty the Recycle Bin.
6. Leave normal folders such as Public Documents and Public Downloads in place.

If you are not sure whether a file is safe to delete, do not guess. Right-click it, choose Scan with Microsoft Defender, and let the scan in Fix 5 decide.

Fix 5. Run a full and an offline Microsoft Defender scan

30 to 90 minutesLow riskEveryone with a path in C:\Users\Public or a random folder, and anyone whose entry or folder came back.

The pattern behind this box, a hidden script in an odd folder with a launcher that starts itself, matches malware that an antivirus removed only in part. A full scan finds what is left; the offline scan runs before Windows starts, so active malware cannot hide.

Microsoft's support answer for this box lists a full antivirus scan among its fixes. Run the full scan first:

1. Open Windows Security. Select Start, type Windows Security and open the app.
2. Open Virus & threat protection. Select Virus & threat protection. Under Current threats you see when the last scan ran, how long it took and how many files it checked.
3. Run a quick scan. Select Quick scan. If Windows Security thinks a deeper scan is needed, it tells you when the quick scan is done.
4. Open Scan options. If the quick scan finds nothing and you still suspect an infection, select Scan options under Current threats.
5. Run a full scan. Select Full scan and start it. It checks every file and program on the device, so it takes much longer than a quick scan. Leave the PC on until it ends.
6. Or scan one folder. To check only a download or a USB drive, select Custom scan in Scan options and choose the folder. You can also right-click a file or folder in File Explorer and select Scan with Microsoft Defender. On Windows 11 you may have to select Show more options first.
7. Read Protection history. Go back to the first page of Windows Security and select Protection history. Select a card to expand it and see the details.

These steps were written for Windows 11 25H2 and 26H2, Windows 10 22H2. The full page with the other versions and what each result means: How to scan for malware with Microsoft Defender

• Offline scan: on the same Scan options page, choose Microsoft Defender Antivirus (offline scan) and click Scan now. The PC restarts and scans before Windows loads.
• After both: open Protection history and remove or quarantine what was found, then repeat Fix 1 to delete the entry the removed program left.

Fix 6. Find the source with a clean boot

15 to 30 minutesLow riskAutoruns and the manual checks found nothing, yet the box still appears.

Microsoft's support answer starts with a clean boot. With only Microsoft services and no startup apps running, the box should stop. Turning items back on a few at a time shows which one starts it.

1. Open System Configuration. Select Search on the taskbar, type msconfig and select System Configuration from the results.
2. Hide Microsoft services. On the Services tab, select the Hide all Microsoft services check box. Only services from other companies stay in the list.
3. Disable the remaining services. Select Disable all, then select Apply.
4. Open Task Manager. On the Startup tab of System Configuration, select Open Task Manager.
5. Disable the startup apps. On the Startup apps tab in Task Manager, select each item whose status is Enabled and select Disable. Write down or take a screenshot of the items you disable: you need the list to turn them back on.
6. Confirm the changes. Close Task Manager. On the Startup tab of System Configuration, select OK.
7. Restart and test. Restart the PC. Windows now starts in a clean boot environment: try again the thing that failed (run the app, install the update, uninstall the program).

These steps were written for Windows 11 25H2 and 26H2. The full page with the other versions and what each result means: How to perform a clean boot in Windows

When you find the item, delete it with Autoruns (Fix 1) rather than leaving it disabled. Then return to a normal start as the clean boot page explains.

Fix 7. Go back with System Restore

20 to 40 minutesRead the warningThe box started on a day you remember, after an install or a download, and you have a restore point from before.

The AutoIt developers advise tracking back what you installed lately and doing a system restore to before that date. It removes the programs and startup entries added since, without touching your documents.

Pick the newest restore point before the box first appeared.

1. Open System Restore. Press Windows+R, type the command below and press Enter. You can also open Control Panel > Recovery > Open System Restore. If a first page opens, select Next.

   rstrui.exe

2. Choose a restore point. Select a restore point from a time before the problem started. The Description often names the event, such as a driver or app install. If the one you need is missing, select Show more restore points (shown only when there are more).
3. See what will change. Select Scan for affected programs. The upper list shows programs and drivers that will be removed; the lower list shows those that might come back and may need to be reinstalled. Select Close.
4. Start the restore. Select Next, check the summary and select Finish. Windows restarts and applies the restore point. Do not turn the PC off.
5. Check the result. After sign-in Windows reports whether the restore succeeded. Check whether the problem is gone.

These steps were written for Windows 11 and Windows 10 (the steps are the same). The full page with the other versions and what each result means: Undo recent changes with System Restore

Fix 8. Reset this PC and keep your files

1 to 2 hoursRead the warningLast resort: the box or the malware keeps coming back after every other fix.

Microsoft's support answer ends with a fresh Windows install if nothing else works. Reset this PC with Keep my files reinstalls Windows and removes every program and startup entry, which takes the launcher with it.

1. Press Win + I. On Windows 11 open System > Recovery, on Windows 10 Update & Security > Recovery.
2. Next to Reset this PC, click Reset PC on Windows 11 or Get started on Windows 10.
3. Choose Keep my files.
4. Choose Cloud download or Local reinstall and follow the screens to the end.

If the AutoIt Line 0 box still appears: what to check

The box itself does not say which program showed it. These places do.

1. When the box is on screen, press Ctrl + Shift + Esc, open Details, add the Command line column (right-click a column header, Select columns) and look for the process that names the missing file.
2. Right-click that process and choose Open file location. That folder is what Fix 4 should delete.
3. Open Event Viewer > Applications and Services Logs > Microsoft > Windows > TaskScheduler > Operational. An entry at the minute the box appeared names the task that ran.
4. Run Autoruns again and filter for the name of the process from step 1.

• To ask for help: post the exact path from the box, the process path from step 2 and a screenshot of Autoruns with the filter applied, on Microsoft Q&A or your antivirus maker's forum.
• Not hardware: a disk, memory or graphics fault does not produce this message. It is always a program asking for a missing file.
• Not Windows: neither Microsoft nor the AutoIt team ships a program that shows this box at startup.

A related case is a black command window that flashes up on its own; our guide to the cmd.exe window popping up in Windows uses the same tools.

How to keep the AutoIt Line 0 error from coming back

If you write AutoIt scripts yourself and get this box for your own script, the path is simply wrong: check that the shortcut or task points to the file where it really is.

Frequently asked questions

What is the AutoIt Error Line 0 message?

It is the message an AutoIt program shows when it cannot open the script file it was told to run. Line 0 means it stopped before running any line, and the path after File is the script it looked for. On most PCs that file is gone, because an antivirus or a cleanup removed it, while the entry that starts the program at sign-in stayed. Deleting that entry with Autoruns in Fix 1 stops the box. If the path is in C:\Users\Public or a random folder, also run the malware scan in Fix 5.

Is the AutoIt error a virus?

The box itself is not a virus, but it often points to one. AutoIt is a legitimate free language, and AutoIt programs are also used by malware authors, because a compiled script is one small exe. A script in C:\Users\Public or a folder with a random name, a box every few minutes and a running exe next to it are signs that a malicious program was removed only in part or is still there. Delete its entries and folder, then run a full and an offline Microsoft Defender scan, as in Fixes 1, 4 and 5.

Should I uninstall AutoIt to fix it?

Only if AutoIt is in your list of installed apps and you do not use it. In most cases it is not installed at all: the AutoIt developers explained that the program showing the box is likely a compiled script that carries AutoIt inside, so removing AutoIt changes nothing. The box goes away when the startup entry that runs the missing script is deleted. That is why this page starts with Autoruns instead of uninstalling.

What does Line 0 Error opening the file mean in C:\Users\Public\bin.au3?

It means a startup entry runs a program that wants the script bin.au3 in the Public user folder, and that script is not there. The person who reported this on Microsoft Q&A could not find the file either. C:\Users\Public is shared by all accounts and is not a place where normal apps keep startup scripts. Delete the entry with Autoruns by filtering for bin, remove any other odd files from that folder, and run a full Microsoft Defender scan.

Why does the AutoIt error pop up every few minutes?

Because a scheduled task starts the program on a timer, and each start fails with the same box. A Run key or Startup folder shortcut only starts it once at sign-in. Open the Scheduled Tasks tab in Autoruns, or Task Scheduler as in Fix 3, and delete the task whose action points to the missing file or its folder. Users who only clicked OK, or only ran an antivirus, report that the box kept coming back until the task was removed.

My antivirus found nothing. Why do I still see the box?

Because there is nothing left for it to find. Many antivirus programs delete the malicious script but leave the Run key or scheduled task that started it, since an entry pointing to a missing file is not itself harmful. The reader on the AutoIt forum had Bitdefender and Malwarebytes and still saw the box. A tool that lists startup entries, such as Autoruns in Fix 1, finds what the scanners leave.

How do I fix the AutoIt error on Windows 10?

The same way as on Windows 11. Autoruns, Registry Editor, Task Scheduler and Microsoft Defender work on both, and where a menu differs, this page gives both paths. On Windows 10, Task Manager shows startup apps on a Startup tab instead of a Startup apps page. Windows 10 left support on 14 October 2025, so without Extended Security Updates it no longer gets security fixes, which matters if malware was involved.

What about AutoIt Error "Unable to open the script file"?

That message comes from the same situation in a slightly different form: AutoIt is started with a script path that does not exist. The fix does not change. Note the path the box shows, search for it in Autoruns and delete the matching entry, then remove the leftover folder. If you run the script yourself, check that the shortcut points to the right folder.

What does this AutoIt error mean (qué significa este error)?

This page is in English. The AutoIt Error Line 0, Error opening the file box means that a program starts with Windows and looks for a script file that has been deleted. It is usually a leftover of a program, often malware, that an antivirus removed. To fix it, run Autoruns as administrator, type the file name from the message into the filter and delete the matching entry. Then delete the leftover folder and run a full Microsoft Defender scan.