Member Avatar for RonR

I get a "windows script host" error msg when booting.


i am not using scripts.

this is one of the lines in the error msg displayed:

could not create object named "wscript.shell"

any ideas on how to fix this??

  • 3 Contributors
  • 2 Replies
  • 205 Views
  • 4 Days Discussion Span
  • Latest Post Latest Post by alc6379

Dani AI

Generated

The message "could not create object named 'WScript.Shell'" means a script tried to instantiate the WScript.Shell COM object but Windows couldn't hand it back. Common causes are: Windows Script Host (WSH) disabled in the registry, the WSH components (.dll/.ocx) not registered or corrupted, wscript.exe missing/altered, or a startup/scheduled script (or malware) running at boot. That matches 's note that no intentional scripts are in use — third‑party apps, scheduled tasks or malware often trigger scripts at startup.

A practical diagnostic order (fastest first): inspect the Startup folder and Scheduled Tasks for any .vbs/.js, check the Run keys in the registry (HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run and HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Run), try a clean boot via msconfig or Safe Mode to see whether the error appears, and run up‑to‑date antivirus/anti‑malware scans. As suggested, WSH error documentation is useful background, and as noted reinstalling the scripting engine can help — the next steps cover repair actions.

To repair common registration problems, run these from an elevated Command Prompt (Windows XP era: Start → Run → cmd):

regsvr32 /u "%windir%\system32\scrrun.dll"
regsvr32 "%windir%\system32\scrrun.dll"
regsvr32 /u "%windir%\system32\wshom.ocx"
regsvr32 "%windir%\system32\wshom.ocx"
sfc /scannow

To ensure WSH is enabled, import a registry file with the following content (save as EnableWSH.reg and merge). Back up the registry first.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Script Host\Settings]
"Enabled"=dword:00000001

Notes and cautions: sfc /scannow may request the Windows XP CD to restore system files. On 64‑bit systems the Wow6432Node variants should be checked. If wscript.exe has been replaced or is missing, reinstalling the Windows Script Host package from Microsoft (or using System File Checker) is appropriate. If the problem persists after these steps, run a startup‑item inspector (Sysinternals Autoruns) and a full anti‑malware clean — many persistent WSH boot errors trace back to unwanted startup scripts.

Recommended Answers

All 2 Replies

Member Avatar for alc6379

try downloading Windows Script:

Usually, if you've got a script error, you can resolve it by making sure Windows Script is installed correctly.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.