Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Wscript.exe or Cscript.exe process stops when WSH 5.7 exits on a computer that is running Windows Vista or Windows Server 2008


View products that this article applies to.

Symptoms

Assume that you use a Microsoft Visual Basic Scripting Edition (VBScript) script or a JScript script on a computer that is running Windows Vista or Windows Server 2008. The VBScript or Jscript script uses Windows Script Host (WSH) 5.7 objects to run an application. When WSH 5.7 exits, the Wscript.exe or Cscript.exe process stops unexpectedly, and an incorrect exit code is returned.

↑ Back to the top


Cause

This issue is caused by an access violation that occurs in WSH 5.7. When you use a VBScript or Jscript script that uses WSH 5.7 objects to run an application, the Wshom.ocx module creates a background thread to monitor the status of the application. When the script ends, WSH 5.7 unloads the Wshom.ocx module. However, the Wshom.ocx module does not stop the background thread. Therefore, an access violation occurs in WSH 5.7, and then the Wscript.exe or Cscript.exe process exits. Additionally, an incorrect error code is returned to the script in some cases.

↑ Back to the top


Resolution

To resolve this issue, we have released a hotfix for Windows Vista or Windows Server 2008.

Note After you download the hotfix package, decompress the package into a folder, and then double-click the Windows6.0-KB2706530-x86.msu, Windows6.0-KB2706530-x64.msu, or Windows6.0-KB2706530-ia64.msu file to install the fix.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running Windows Vista Service Pack 2 (SP2) or Windows Server 2008 SP2.

For more information about how to obtain a Windows Vista service pack, click the following article number to view the article in the Microsoft Knowledge Base:

935791 How to obtain the latest Windows Vista service pack

For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

968849 How to obtain the latest service pack for Windows Server 2008

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Vista and Windows Server 2008 file information notes
Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    VersionProductSR_LevelService branch
    6.0.600
    2.
    22xxx
    Windows Vista and Windows Server 2008SP2LDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Vista and for Windows Server 2008" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Vista and of Windows Server 2008
File nameFile versionFile sizeDateTime
Cscript.exe5.7.6002.18653135,16815-Jun-201213:50
Dispex.dll5.7.0.1800032,76819-Jan-200807:34
Scrobj.dll5.7.0.18005180,22411-Apr-200906:28
Scrrun.dll5.7.0.18005172,03211-Apr-200906:28
Wscript.exe5.7.6002.18653155,64815-Jun-201213:50
Wshcon.dll5.7.6002.1865336,86415-Jun-201215:52
Wshom.ocx5.7.6002.18653131,07215-Jun-201215:52
Cscript.exe5.7.6002.22882135,16815-Jun-201213:33
Dispex.dll5.7.6002.2288232,76815-Jun-201214:40
Scrobj.dll5.7.6002.22882180,22415-Jun-201214:42
Scrrun.dll5.7.6002.22882172,03215-Jun-201214:42
Wscript.exe5.7.6002.22882155,64815-Jun-201213:33
Wshcon.dll5.7.6002.2288236,86415-Jun-201214:43
Wshom.ocx5.7.6002.22882135,16815-Jun-201214:43
For all supported x64-based versions of Windows Vista and of Windows Server 2008
File nameFile versionFile sizeDateTime
Cscript.exe5.7.6002.18653147,96815-Jun-201214:14
Dispex.dll5.7.0.1800018,94419-Jan-200808:01
Scrobj.dll5.7.0.18005227,32811-Apr-200907:11
Scrrun.dll5.7.0.18005198,65611-Apr-200907:11
Wscript.exe5.7.6002.18653166,91215-Jun-201214:14
Wshcon.dll5.7.0.1800028,16019-Jan-200808:04
Wshom.ocx5.7.6002.18653144,38415-Jun-201216:17
Cscript.exe5.7.6002.22882148,48015-Jun-201214:11
Dispex.dll5.7.6002.2288218,94415-Jun-201215:33
Scrobj.dll5.7.6002.22882227,32815-Jun-201215:36
Scrrun.dll5.7.6002.22882199,16815-Jun-201215:36
Wscript.exe5.7.6002.22882167,42415-Jun-201214:11
Wshcon.dll5.7.6002.2288228,16015-Jun-201215:38
Wshom.ocx5.7.6002.22882144,38415-Jun-201215:38
For all supported IA-64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTime
Cscript.exe5.7.6002.18653304,64015-Jun-201213:49
Dispex.dll5.7.0.1800035,84019-Jan-200808:26
Scrobj.dll5.7.0.18005491,00811-Apr-200906:59
Scrrun.dll5.7.6002.18653406,01615-Jun-201215:31
Wscript.exe5.7.6002.18653343,55215-Jun-201213:50
Wshcon.dll5.7.0.1800071,68019-Jan-200808:29
Wshom.ocx5.7.6002.18653276,99215-Jun-201215:32
Cscript.exe5.7.6002.22882304,64015-Jun-201213:16
Dispex.dll5.7.6002.2288235,84015-Jun-201214:12
Scrobj.dll5.7.6002.22882491,00815-Jun-201214:15
Scrrun.dll5.7.6002.22882406,52815-Jun-201214:15
Wscript.exe5.7.6002.22882344,06415-Jun-201213:16
Wshcon.dll5.7.6002.2288271,68015-Jun-201214:16
Wshom.ocx5.7.6002.22882277,50415-Jun-201214:16

↑ Back to the top


Status

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

↑ Back to the top


More Information

For more information about the Wscript.exe process issue or the Cscript.exe process issue, click the following article number to view the article in the Microsoft Knowledge Base:
2706051 Wscript.exe process or the Cscript.exe process stops unexpectedly when WSH 5.8 exits on a computer that is running Windows 7 or Windows Server 2008 R2
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows Vista and for Windows Server 2008

Additional files for all supported x86-based versions of Windows Vista and of Windows Server 2008
File nameX86_21173003d21acabdcc5d3ee26251402f_31bf3856ad364e35_6.0.6002.18653_none_fb41207cda2bce45.manifest
File versionNot applicable
File size697
Date (UTC)19-Jun-2012
Time (UTC)07:09
File nameX86_5f20fbc3e74f314a9a879affec8b97f4_31bf3856ad364e35_6.0.6002.22882_none_71bdac9ec5f2dd1e.manifest
File versionNot applicable
File size697
Date (UTC)19-Jun-2012
Time (UTC)07:09
File nameX86_microsoft-windows-scripting_31bf3856ad364e35_6.0.6002.18653_none_4a1bc755fda604b8.manifest
File versionNot applicable
File size181,385
Date (UTC)19-Jun-2012
Time (UTC)07:09
File nameX86_microsoft-windows-scripting_31bf3856ad364e35_6.0.6002.22882_none_4a83f5f916dcdc25.manifest
File versionNot applicable
File size168,929
Date (UTC)15-Jun-2012
Time (UTC)14:57
Additional files for all supported x64-based versions of Windows Vista and of Windows Server 2008
File nameAmd64_10b0fec0b001366151b77150f3bb8a81_31bf3856ad364e35_6.0.6002.22882_none_775ebb837fd2fc82.manifest
File versionNot applicable
File size1,042
Date (UTC)19-Jun-2012
Time (UTC)07:09
File nameAmd64_f324913ef8ec791ee07905c9054081b6_31bf3856ad364e35_6.0.6002.18653_none_1cc6a5b7e0575349.manifest
File versionNot applicable
File size1,042
Date (UTC)19-Jun-2012
Time (UTC)07:09
File nameAmd64_microsoft-windows-scripting_31bf3856ad364e35_6.0.6002.18653_none_a63a62d9b60375ee.manifest
File versionNot applicable
File size181,411
Date (UTC)19-Jun-2012
Time (UTC)07:10
File nameAmd64_microsoft-windows-scripting_31bf3856ad364e35_6.0.6002.22882_none_a6a2917ccf3a4d5b.manifest
File versionNot applicable
File size168,955
Date (UTC)15-Jun-2012
Time (UTC)15:52
Additional files for all supported IA-64-based versions of Windows Server 2008
File nameIa64_df84ad55a0753c333cc3e28553aa5265_31bf3856ad364e35_6.0.6002.22882_none_2ed8955685335e91.manifest
File versionNot applicable
File size1,040
Date (UTC)19-Jun-2012
Time (UTC)07:09
File nameIa64_fc8dc21cbe9417ce41205d37ec753f3a_31bf3856ad364e35_6.0.6002.18653_none_3228a4f811daa33b.manifest
File versionNot applicable
File size1,040
Date (UTC)19-Jun-2012
Time (UTC)07:09
File nameIa64_microsoft-windows-scripting_31bf3856ad364e35_6.0.6002.18653_none_4a1d6b4bfda40db4.manifest
File versionNot applicable
File size181,398
Date (UTC)19-Jun-2012
Time (UTC)07:10
File nameIa64_microsoft-windows-scripting_31bf3856ad364e35_6.0.6002.22882_none_4a8599ef16dae521.manifest
File versionNot applicable
File size168,942
Date (UTC)15-Jun-2012
Time (UTC)14:26

↑ Back to the top


Keywords: kb, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseadvanced, kbautohotfix

↑ Back to the top

Article Info
Article ID : 2706530
Revision : 1
Created on : 1/7/2017
Published on : 4/9/2015
Exists online : False
Views : 293