Article ID: 952033 - Last Review: May 6, 2008 - Revision: 3.1 The "CScript //H" or "WScript //H" command may not work as expected on a Windows XP-based computer after you install or uninstall Windows XP Service Pack 3
SYMPTOMSWhen you use the CScript //H or WScript //H command to change the default script host on a Windows XP-based
computer, the operation may not work as expected. For example, if you use the CScript //H:CScript command, WScript is set as the default script host instead of
CScript. You may experience this issue in the following scenarios. Scenario 1 On a Windows XP Service Pack 2 (SP2)-based computer, you change the default script host to CScript. Then, you install Windows XP Service Pack 3 (SP3). However, when you try to change the default script host again, you experience this issue. Scenario 2 On a Windows XP SP3-based computer, you change the default script host to CScript. Then, you uninstall Windows XP SP3. However, when you try to change the default script host again, you experience this issue. Note This issue occurs only if the default script host is changed to CScript before you install or uninstall Windows XP SP3. CAUSEWindows XP SP3 installs Windows Script Host (WSH) 5.7. The
mechanism to change the default script host in WSH 5.7 differs from the
corresponding mechanism in WSH 5.6. Because of this difference, you experience
this issue when Windows XP SP3 is installed or uninstalled. Note Windows XP SP2 installs WSH 5.6. WORKAROUNDImportant This section, method, or task contains steps that tell you how to
modify the registry. However, serious problems might occur if you modify the
registry incorrectly. Therefore, make sure that you follow these steps
carefully. For added protection, back up the registry before you modify it.
Then, you can restore the registry if a problem occurs. For more information
about how to back up and restore the registry, click the following article
number to view the article in the Microsoft Knowledge Base: 322756
(http://support.microsoft.com/kb/322756/
)
How to back up and restore the registry in Windows To work around this issue, follow these steps one
time for each script file name extension with which you experience this issue.
For example, if you experience this issue with the .vbs file name extension,
follow these steps:
| Other Resources Other Support Sites
CommunityGet Help NowArticle Translations
|






Windows Live
Facebook
Twitter
Linkedin
Digg it
Yahoo
Delicious
StumbleUpon
Yammer
Reddit
Technorati
FriendFeed
Email
Back to the top
