Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
Overview of Windows Script Host in Windows
Article ID: 232211 - View products that this article applies to.
This article was previously published under Q232211
NoticeThis article applies to Windows 2000. Support for Windows 2000 ends on July 13, 2010. The Windows 2000 End-of-Support Solution Center
(http://support.microsoft.com/?scid=http%3a%2f%2fsupport.microsoft.com%2fwin2000)is a starting point for planning your migration strategy from Windows 2000. For more information see the Microsoft Support Lifecycle Policy
Windows Script Host (WSH) enables scripts to be run directly in Windows by double-clicking a script file or by typing the name of a script file at a command prompt. Like Microsoft Internet Explorer, WSH serves as a controller of ActiveX scripting engines. WSH has very low memory requirements and is ideal for both interactive and non-interactive scripting needs (such as logon scripting and administrative scripting).
There are two versions of WSH: a Windows-based version (Wscript.exe) that provides Windows-based properties for setting script properties, and a command prompt-based version (Cscript.exe) that provides command-line switches for setting script properties. You can run either of these versions by typing "wscript.exe" or "cscript.exe" at a command prompt.
To Run Scripts Using the Windows-Based Script Host (Wscript.exe)
You can also set properties for an individual script by right-clicking a script file in My Computer or Windows Explorer, clicking Properties, and then clicking the Script tab.
To Set Properties for Individual Scripts
A .wsh file is a text file that uses a format similar to that of .ini files. A .wsh file contains a [ScriptFile] section, which identifies the script file with which the .wsh file is associated, and an [Options] section, which corresponds to the settings you selected on the Script tab.
A .wsh file is analogous to the .pif files used to run earlier 16-bit Windows-based and MS-DOS-based programs. It can be treated as if it were an executable or batch file. For example, if you have a script named Myscript.vbs for which you have created a .wsh file named Myscript.wsh, you can run Myscript.vbs with the options recorded in Myscript.wsh by double-clicking Myscript.wsh in Windows Explorer, or by passing Myscript.wsh as a script argument to Cscript.exe or Wscript.exe at a command prompt.
For additional information about WSH, please visit the following Microsoft Web site: