How to Fix Windows Script Host

By Tyran DeWalt

If you are experiencing script host issues, you might notice error messages such as "Library not registered." Script host issues occur when scripting components do not exist in the Windows registry, according to Microsoft. Your version of Windows determines how the missing scripting components affect your system. You can repair script host problems by using your PC's native features.

Register Components on 32-Bit Systems

Step 1

Press the "Windows" key. Type "cmd" in the dialog box and press "Enter." This will open the Command Prompt.

Step 2

Type the following commands at the prompt one at a time and press "Enter:"regsvr32 %systemroot%\system32\vbscript.dllregsvr32 %systemroot%\system32\jscript.dllregsvr32 %systemroot%\system32\dispex.dllregsvr32 %systemroot%\system32\scrobj.dllregsvr32 %systemroot%\system32\scrrun.dllregsvr32 %systemroot%\system32\wshext.dllregsvr32 %systemroot%\system32\wshom.ocx

Step 3

Exit the Command Prompt.

Register Components on 64-bit Systems

Step 1

Press the "Windows" key. Type "cmd" in the dialog box and press "Enter." This will open the Command Prompt.

Step 2

Type the following commands at the prompt one at a time and press "Enter:"%systemroot%\system32\regsvr32 %systemroot%\system32\vbscript.dll%systemroot%\system32\regsvr32 %systemroot%\system32\jscript.dll%systemroot%\system32\regsvr32 %systemroot%\system32\dispex.dll%systemroot%\system32\regsvr32 %systemroot%\system32\scrobj.dll%systemroot%\system32\regsvr32 %systemroot%\system32\scrrun.dll%systemroot%\system32\regsvr32 %systemroot%\system32\wshext.dll%systemroot%\system32\regsvr32 %systemroot%\system32\wshom.ocx

Step 3

Exit the Command Prompt.