When I run a script in Windows Script, I receive an error message: "Library not registered"

When you try to run a script in Windows Script, you receive the following error message:

This problem occurs because one or more of the scripting components are not registered in the Windows registry.

To resolve this problem, use one of the following methods.

Method 1: Download and then reinstall Windows Script

To download and then reinstall Windows Script, visit one of the following Microsoft Web sites, depending on the version of Windows Script that you are using and the operating system that the computer is running.

Windows Script 5.7 for Windows Server 2003

The following file is available for download from the Microsoft Download Center:

Download the scripten.exe package now. (http://www.microsoft.com/downloads/details.aspx?FamilyID=f00cb8c0-32e9-411d-a896-f2cd5ef21eb4&DisplayLang=en)

Windows Script 5.7 for Windows XP

The following file is available for download from the Microsoft Download Center:

Download the scripten.exe package now. (http://www.microsoft.com/downloads/details.aspx?FamilyID=47809025-d896-482e-a0d6-524e7e844d81&DisplayLang=en)

Windows Script 5.7 for Windows 2000

The following file is available for download from the Microsoft Download Center:

Download the scripten.exe package now. (http://www.microsoft.com/downloads/details.aspx?FamilyID=c03d3e49-b40e-4ca1-a0c7-cc135ec4d2be&DisplayLang=en)

Windows Script 5.6 for Windows Server 2003

The following file is available for download from the Microsoft Download Center:

Download the WindowsServer2003-Script56-KB917344-x86-enu.exe package now. (http://www.microsoft.com/downloads/details.aspx?familyid=887FCE82-E3F5-4289-A5E3-6CBB818623AA&displaylang=en)

Windows Script 5.6 for Windows XP and for Windows 2000

The following file is available for download from the Microsoft Download Center:

Download the http://www.microsoft.com/downloads/details.aspx?FamilyID=c717d943-7e4b-4622-86eb-95a22b832caa&DisplayLang=en package now. (http://www.microsoft.com/downloads/details.aspx?FamilyID=f00cb8c0-32e9-411d-a896-f2cd5ef21eb4&DisplayLang=en)

Method 2: Register the scripting components on your computer

To fix this problem, change the scripting components on your computer. To have us fix this problem for you, go to the "Fix it for me" section. If you’d rather fix this problem yourself, go to the "Let me fix it myself" section.

Fix it for me

To fix this problem automatically, click the Fix this problem link. Then click Run in the File Download dialog box, and follow the steps in this wizard.



Note This wizard may be in English only; however, the automatic fix also works for other language versions of Windows.

Note If you are not on the computer that has the problem, you can save the automatic fix to a flash drive or a CD so that you can run it on the computer that has the problem.

Now go to the "Did this fix the problem?" section.

Let me fix it myself

To manually register the scripting components on your computer, use one of the following sets of steps, as appropriate for your situation.

You are running a 32-bit version of the Windows operating system

1. Click Start, click Run, type cmd, and then click OK.
2. Type regsvr32 %systemroot%\system32\vbscript.dll, and then press ENTER.
3. Type regsvr32 %systemroot%\system32\jscript.dll, and then press ENTER.
4. Type regsvr32 %systemroot%\system32\dispex.dll, and then press ENTER.
5. Type regsvr32 %systemroot%\system32\scrobj.dll, and then press ENTER.
6. Type regsvr32 %systemroot%\system32\scrrun.dll, and then press ENTER.
7. Type regsvr32 %systemroot%\system32\wshext.dll, and then press ENTER.
8. Type regsvr32 %systemroot%\system32\wshom.ocx, and then press ENTER.

You are running a 64-bit version of the Windows operating system, and you receive the error message that is mentioned in the "Symptoms" section while you are using the 64-bit scripting components

1. Click Start, click Run, type cmd, and then click OK.
2. Type %systemroot%\system32\regsvr32 %systemroot%\system32\vbscript.dll, and then press ENTER.
3. Type %systemroot%\system32\regsvr32 %systemroot%\system32\jscript.dll, and then press ENTER.
4. Type %systemroot%\system32\regsvr32 %systemroot%\system32\dispex.dll, and then press ENTER.
5. Type %systemroot%\system32\regsvr32 %systemroot%\system32\scrobj.dll, and then press ENTER.
6. Type %systemroot%\system32\regsvr32 %systemroot%\system32\scrrun.dll, and then press ENTER.
7. Type %systemroot%\system32\regsvr32 %systemroot%\system32\wshext.dll, and then press ENTER.
8. Type %systemroot%\system32\regsvr32 %systemroot%\system32\wshom.ocx, and then press ENTER.

You are running a 64-bit version of the Windows operating system, and you receive the error message that is mentioned in the "Symptoms" section while you are using the 32-bit scripting components

1. Click Start, click Run, type cmd, and then click OK.
2. Type %systemroot%\syswow64\regsvr32 %systemroot%\syswow64\vbscript.dll, and then press ENTER.
3. Type %systemroot%\syswow64\regsvr32 %systemroot%\syswow64\jscript.dll, and then press ENTER.
4. Type %systemroot%\syswow64\regsvr32 %systemroot%\syswow64\dispex.dll, and then press ENTER.
5. Type %systemroot%\syswow64\regsvr32 %systemroot%\syswow64\scrobj.dll, and then press ENTER.
6. Type %systemroot%\syswow64\regsvr32 %systemroot%\syswow64\scrrun.dll, and then press ENTER.
7. Type %systemroot%\syswow64\regsvr32 %systemroot%\syswow64\wshext.dll, and then press ENTER.
8. Type %systemroot%\syswow64\regsvr32 %systemroot%\syswow64\wshom.ocx, and then press ENTER.

Did this fix the problem?

Check whether the problem is fixed. If the problem is fixed, you are finished with this article. If the problem is not fixed, you can contact support (http://support.microsoft.com/contactus) .

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.