How to Fix Windows Script Host Error on Windows 11

The Windows Script Host error can pop up suddenly at startup, shutdown, or when launching an app, often showing messages related to .vbs, .js, or .wsf files. On Windows 11, this error is usually caused by startup scripts, leftover malware entries, broken registry references, or disabled scripting services—not by Windows itself being damaged.

This guide explains why Windows Script Host errors appear and walks you through all reliable fixes, from basic to advanced.

What Is Windows Script Host (WSH)?

Windows Script Host is a built-in Windows component that runs scripts written in:

• VBScript (.vbs)
• JScript (.js)
• Windows Script Files (.wsf)

It’s commonly used by:

• Startup tasks
• Admin scripts
• Legacy apps
• Malware remnants (very common cause)

When Windows tries to run a missing or blocked script, the error appears.

Common Windows Script Host Error Messages

You may see messages like:

• Windows Script Host – Script file cannot be found
• There is no script engine for file extension “.vbs”
• Access is denied
• The system cannot find the file specified

The exact wording helps identify the cause.

Fix Windows Script Host Error on Windows 11

Follow the steps in order. After each step, restart your PC and check if the error is gone.

1. Note the Script File Name Shown in the Error

Before fixing anything, read the error carefully.

• Look for a file path or script name (for example: startup.vbs)
• Note whether it points to:
  • AppData
  • Temp folders
  • Program Files
  • System32

This helps identify whether it’s a startup entry or malware leftover.

2. Scan Your PC for Malware (Very Important)

Windows Script Host errors are often caused by removed malware leaving broken startup entries.

1. Open Windows Security.
2. Go to Virus & threat protection.
3. Click Scan options.
4. Run a Full scan.
5. If possible, follow up with an Offline scan.

Remove any threats found and restart your PC.

3. Disable the Problematic Startup Script

If the error appears at startup, a startup item is triggering it.

Using Task Manager

1. Press Ctrl + Shift + Esc.
2. Open the Startup apps tab.
3. Look for:
   • Unknown entries
   • Entries with no publisher
4. Disable suspicious items.
5. Restart Windows.

4. Check Startup Script Locations Manually

Some scripts don’t appear in Task Manager.

1. Press Windows + R, type: shell:startup
2. Delete any suspicious .vbs or .js files.
3. Repeat with: shell:common startup

These folders commonly contain leftover scripts.

5. Remove Invalid Registry Startup Entries (Effective)

Broken registry references frequently cause WSH errors.

1. Press Windows + R, type regedit, and press Enter.
2. Navigate to: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
3. Also check: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run
4. Look for entries pointing to missing .vbs or .js files.
5. Delete only the suspicious entries.

Restart Windows afterward.

6. Re-enable Windows Script Host (If Disabled)

Some guides disable WSH for security, which can break legitimate apps.

1. Open Command Prompt (Admin).
2. Run: reg add "HKLM\Software\Microsoft\Windows Script Host\Settings" /v Enabled /t REG_DWORD /d 1 /f
3. Restart your PC.

This re-enables script execution.

7. Restore Default Script File Associations

If scripts fail to run entirely, file associations may be broken.

1. Open Command Prompt (Admin).
2. Run: assoc .vbs=VBSFile ftype VBSFile="%SystemRoot%\System32\WScript.exe" "%1" %*
3. Restart Windows.

This restores VBScript handling.

8. Run System File Checker

If core scripting components are damaged:

1. Open Command Prompt (Admin).
2. Run: sfc /scannow
3. After it finishes, run: DISM /Online /Cleanup-Image /RestoreHealth
4. Restart Windows.

This repairs Windows Script Host components.

9. Check Task Scheduler for Broken Script Tasks

Scheduled tasks can trigger WSH errors silently.

1. Open Task Scheduler.
2. Browse Task Scheduler Library.
3. Look for tasks running .vbs or .js files.
4. Disable or delete tasks pointing to missing files.

Restart and test again.

10. Clean Temporary Files

Some errors reference scripts in Temp folders.

1. Press Windows + R, type: %temp%
2. Delete all files you can.
3. Restart Windows.

Wrapping Up

The Windows Script Host error on Windows 11 is almost always caused by leftover startup scripts, broken registry entries, or malware remnants, not a serious Windows failure. By scanning for malware, removing invalid startup entries, fixing registry references, and repairing system files, you can permanently eliminate the error.

Once cleaned up, Windows will boot and run without script-related pop-ups.