How to Fix “Can Not Find Script File” Startup Error?

“Can not find script file” appears when Windows tries to run a script during startup, but the file linked to that task is missing, moved, or damaged. This usually happens when an app is uninstalled, a cleanup utility removes a file, or a security tool deletes a harmful script but leaves the startup shortcut behind. Windows keeps calling a script that no longer exists, and the prompt shows every time you boot.

In many cases, the issue becomes more stubborn if Windows can no longer open VBS files correctly. When the default handler changes, every script attempt fails. After understanding the cause, you can follow the reliable methods below. These have helped many users and do not require complicated actions.

1. Use Autoruns to Remove the Broken StartupCheck.vbs Entry

A leftover startup entry is the most common reason for this prompt. When a script is deleted or quarantined, the startup task linked to it stays active, so Windows keeps calling it during every boot. Autoruns reveals hidden entries that normal system tools cannot locate. Removing or disabling the invalid reference stops Windows from calling the missing script.

1. Download Autoruns from the official Microsoft Sysinternals page.
2. Right click the Autoruns.exe file and choose Run as administrator.
3. Allow Autoruns to complete its scan.
4. Press Ctrl + F, type task.vbs (replace the name with what your error shows), then click Find Next.
5. If Autoruns finds an entry linked to a missing VBS file, uncheck the box to disable it or right click and choose Delete.
6. Repeat the search until no more entries appear.
7. Restart your PC and check the result.

2. Repair the VBS File Association in the Registry

When Windows no longer recognizes VBS files, any script that tries to run will fail. This often occurs after powerful cleanup tools, registry edits, or security software remove related components. Restoring the default association brings back the correct Windows Script Host so VBS files open with the right handler.

1. Open Command Prompt as an administrator.
2. Enter the following and press Enter:

   assoc .vbs=VBSFile

   

3. Then run:

   ftype VBSFile="%SystemRoot%\System32\WScript.exe" "%1" %*

   

4. Restart your PC and check again.

3. Repair Corrupted System Files with SFC and DISM

If key Windows scripting components are missing or damaged, Windows may still try to run related tasks during startup, which results in this prompt. Failed updates or malware cleanup can cause this. SFC and DISM scan your system for damaged or missing files and restore correct versions so Windows can run its scripts normally.

1. Open Command Prompt as an administrator.
2. Run this and press Enter:

   sfc /scannow

   

3. Let the scan finish.
4. Then run:

   DISM /Online /Cleanup-Image /RestoreHealth

   

5. Restart your PC once DISM finishes.

4. Create a Dummy VBS File to Silence the Prompt

If a startup task continues calling a script that no longer exists, you can place a tiny replacement file at that location. This allows Windows to run the file and prevents the prompt. It does not fix the original cause, but it works as a dependable fallback when other methods do not help.

1. When the prompt appears, note the exact file path (for example C:\Windows\System32\task.vbs).
2. Press Windows + R, type notepad, and press Enter.
3. Type this inside Notepad:

   WScript.Quit

4. Click File > Save As.
5. Browse to the location shown in the error.
6. Change the extension from .txt to .vbs.
7. Select All Files as the file type and click Save.
8. Restart your PC and confirm whether the prompt disappears.