************************************* ** ** ** Windows Update & Windows Script ** ** ** ** (revised) ** ** ** ************************************* ------------ - Contents - ------------ * Overview * Platforms & Versions Tested * Testing Procedures * Limitations * Questions & Answers - Extensions - Registered File Types - Files * Table Summary of Results * Conclusions * Windows 98 & "Windows Scripting Host" - Installed Components - Uninstallation * More Information * Credits ---------------- - End Contents - ---------------- OVERVIEW ======== To clear up confusion (if only my own) about the relationship between Microsoft's Windows Update service and Windows Script (otherwise known as the Windows Scripting Host or WSH), I decided to do some testing. Using three different platforms and versions of Internet Explorer, I disabled Windows Script (WS) through a variety of means (see below for details) and then tried connecting to and using Microsoft's Windows Update. This document reports the results of those tests. At the end there is also a short section on uninstalling the "Windows Scripting Host" from Windows 98 & WIndows 98SE. PLATFORMS & VERSIONS TESTED =========================== The following Windows platforms and Internet Explorer versions were tested: #1 Windows 95C (OSR 2.5) w/ Internet Explorer 4.01 w/SP2 #2 Windows 98 (original) w/ Internet Explorer 4.01 w/SP1 #3 Windows NT 4.0 w/ SP6a and Internet Explorer 5.01 w/SP2 The following versions of Windows Script (WS) were used: #1 The Windows 95 box was initially tested with Windows Script 5.5 (12/15/00) and then upgraded to Windows Script 5.5 (4/11/01) #2 The Windows 98 box was initially tested with the default Windows Script components that ship with Windows 98 ("Windows Scripting Host") and then upgraded to Windows Script 5.5 (4/11/01) #3 The Windows NT 4.0 box was initially tested with Windows Script 5.5 (12/15/00) and then upgraded to Windows Script 5.5 (4/11/01) NOTE: Internet Explorer 4.0 or above must be installed in order to access and use Windows Update. The latest versions of Internet Explorer are available here: http://www.microsoft.com/windows/Ie/default.htm ActiveX controls, Active scripting, and cookies must be enabled. Windows Update can be accessed here: http://windowsupdate.microsoft.com/ Microsoft's Office Update service, which can be accessed here... http://officeupdate.microsoft.com/ ...is a similar service and has the same requirements as Windows Update. NOTE: the latest versions of Windows Script 5.1, 5.5, & 5.6 (beta) can be downloaded from Microsoft here: http://msdn.microsoft.com/scripting/ TESTING PROCEDURES ================== To make changes to Windows Script Extensions and File Types in the Registry, a batch file (in combination with .REG files) was used. This same batch was used to "disable" Windows Script files by renaming them to *.DIS. This batch file (which includes the .REG files) is available from: https://netfiles.uiuc.edu/ehowes/www/resource2.htm The same changes to Windows Script Extensions and File Types can be made "manually" either through REGEDIT.EXE, or through Windows Explorer (Tools >> Folder Options... >> File Types). Windows Explorer can also be used to "disable" Windows Script files by renaming each file to *.DIS. Connections to Windows Update were made over both a dial-up networking connection (Windows 98 & Windows NT 4.0) as well as an Ethernet networking connection (Windows 95C). LIMITATIONS =========== Windows: Windows 95, 95A, 95B (OSR 2.0/2.1), 98SE, and ME were not used during any of these tests. Windows 2000 was not used during any of these tests. Windows NT 4.0 was tested with Service Pack 6a, but not with earlier Service Packs. Internet Explorer: no version of Internet Explorer 4.0, 5.0 or 5.5 was used in these tests. All versions of IE 4.01 and 5.01 were service pack levels. Windows Script: Windows Script 5.1 was not used during any of these tests. Windows Script 5.6 (beta 1 & 2) was not used during any of these tests. Earlier versions of components of Windows Script (i.e., pre-5.1) were tested only on Windows 98. Disabling WS: As a means to disable "Windows Script," deletion of Windows Script Extensions or File Types was never employed. Windows Script Extensions and File Types were only modified in one way or another. "Minor Updates": only "minor updates" to Internet Explorer and Windows were made. "Minor updates" include, for example, run-of-the-mill "security" and "critical" updates. By contrast, installations of new versions of Internet Explorer, operating system service packs, or versions of Microsoft Office would all, for example, be considered *major* updates. No installations or version upgrades of Internet Explorer or Microsoft Office were attempted, thus, the testing results detailed below do NOT necessarily reflect what would happen if installations or version upgrades of IE or Office were performed. QUESTIONS & ANSWERS =================== This series of tests was designed to answer a number of main questions about the relationship between Windows Update and Windows Script. What follows are the questions that were at issue as well as the answers to those questions supplied by the testing. These questions and answers are divided into three categories which correspond to the three different means used to disable Windows Script. ---------- Extensions ---------- If the Windows Script Extensions are modified to point to the "Unknown" File Type... 1) will Windows Update still work (both for accessing a catalog and downloading and installing updates)? Answer: YES. 2) will merely accessing Windows Update restore the Extensions to point to the correct/default File Types? Answer: NO. 3) will downloading and installing *minor* updates from Windows Update restore the Extensions to point to the correct/default File Types? Answer: NO. 4) will updating Windows Script from Microsoft (with Windows Script 5.1, 5.5, or 5.6 beta) restore the Extensions to point to the correct/default File Types? Answer: YES. NOTE: the Windows Script Extensions tested were: Extension >> File Type --------- --------- .JS >> JSFile .JSE >> JSEFile .VBE >> VBEFile .VBS >> VBSFile .WSF >> WSFFile .WSH >> WSHFile --------------------- Registered File Types --------------------- If one changes the default action for Windows Script File Types to "Edit"... 1) will Windows Update still work (both for accessing a catalog and downloading and installing updates)? Answer: YES. 2) will merely accessing Windows Update restore the default action to "Open"? Answer: NO. 3) will downloading and installing *minor* updates from Windows Update restore the default action to "Open"? Answer: NO. 4) will updating Windows Script from Microsoft (with Windows Script 5.1, 5.5, or 5.6 beta) restore the default action to "Open"? Answer: NO. NOTE: the following File Types were tested: Registered File Type (Name) File Type (Registry) --------------------------- -------------------- JScript File JSFile JScript Encoded File JSEFile VBScript Encoded File VBEFile VBScript File VBSFile Windows Script File WSFFile Windows Script Host Setting File WSHFile ----- Files ----- If the files shipped with Windows Script 5.5 (see note below) are disabled (by renaming them to *.DIS) or deleted... 1) will Windows Update still work (both for accessing a catalog and downloading and installing updates)? Answer: NO. Explanation: the following files are necessary even to *access* Windows Update (let alone *use* it): DISPEX.DLL JSCRIPT.DLL VBSCRIPT.DLL If these three files (DISPEX.DLL, JSCRIPT.DLL, & VBSCRIPT.DLL) are left alone, but the remaining files shipped with Windows Script 5.5 are renamed or deleted... 1) will Windows Update still work (both for accessing a catalog and downloading and installing updates)? Answer: YES. 2) will merely accessing Windows Update restore the files? Answer: NO. 3) will downloading and installing *minor* updates from Windows Update restore the files? Answer: NO. 4) will updating Windows Script from Microsoft (with Windows Script 5.1, 5.5, or 5.6 beta) restore the files? Answer: YES (obviously). NOTE: Windows Script 5.5 ships with the following files: PROPER NAME 9x Location NT/2000 Location ----------- ----------- ---------------- cscript.exe \WINDOWS\COMMAND \WINNT\SYSTEM32 wscript.exe \WINDOWS \WINNT\SYSTEM32 dispex.dll \WINDOWS\SYSTEM \WINNT\SYSTEM32 jscript.dll \WINDOWS\SYSTEM \WINNT\SYSTEM32 scrobj.dll \WINDOWS\SYSTEM \WINNT\SYSTEM32 scrrun.dll \WINDOWS\SYSTEM \WINNT\SYSTEM32 vbscript.dll \WINDOWS\SYSTEM \WINNT\SYSTEM32 wshext.dll \WINDOWS\SYSTEM \WINNT\SYSTEM32 wshom.ocx \WINDOWS\SYSTEM \WINNT\SYSTEM32 TABLE SUMMARY OF RESULTS ======================== This table summarizes the results of the tests detailed above. :------------------------------------------------------------: | Disable | Access/Use Access = Use = WS Upd = | | Action | WinUpd? Reversal? Reversal Reversal? | | ------- | ---------- --------- -------- --------- | | | | | Ext=Unk | YES NO NO YES | | | | | FT=Edit | YES NO NO NO | | | | | Ren Files1 | NO -- -- [YES]+ | | | | | Ren Files2 | YES NO NO YES | | | | :------------------------------------------------------------: + : not attempted, but can be inferred from "Ren Files2" results. KEY to TERMS ------------ WS: Windows Script Disable Action: the action taken to "disable" Windows Script Ext=Unk: set WS Extensions to point to "Unknown" File Type FT=Edit: set default action for WS File Types to "Edit" Ren Files1: rename all WS files to *.DIS Ren Files2: rename all WS files except DISPEX.DLL, JSCRIPT.DLL, & VBSCRIPT.DLL to *.DIS Access/Use WinUpd?: can Windows Update still be accessed and used to download & install "minor updates"? Access=Reversal?: will accessing Windows Update reverse the action used to "disable" WS? Use=Reversal?: will using Windows Update to download & install "minor updates"reverse the action used to "disable" WS? WS Upd= Reversal?: will updating WS with WS 5.5 (4/11/01) reverse the action used to "disable" WS? CONCLUSIONS =========== The entire Windows Script package need not be installed in order to access and use Microsoft's Windows Update. The proper Extensions and default actions for File Types certainly do not need to be properly set in the Registry for Windows Update to work. Certain files or components that are shipped with the later Windows Script packages from Microsoft (e.g., versions 5.1, 5.5, or 5.6 beta), however, must be installed for Windows Update to work. These required files or components are: DISPEX.DLL, JSCRIPT.DLL, & VBSCRIPT.DLL. Windows 98, 98SE, ME, and 2000 all ship with at least these required components. Early versions of Windows 95 and Windows NT 4.0, however, may lack even these three basic, required components. In such cases users might be advised by Microsoft or Windows Update to install the latest version of Windows Script or a package called the "Visual Basic Scripting Host." Moreover, merely accessing and using Windows Update will not restore the default Extensions or default actions for File Types to the Registry. Nor will accessing or using Windows Update restore disabled or deleted Windows Script files (with the exception of the three noted above, which are necessary to access Windows Update). Finally, if the default action for WS File Types has been changed to "Edit," updating Windows Script with one of the later Windows Script packages from Microsoft will not reset the default File Type action to "Open." Updating Windows Script will restore proper Extensions and disabled or deleted files, however. Although no "major updates" (e.g., installations of Internet Explorer, Microsoft Office, or service packs) were made during these tests, it is entirely possible that such "major updates" would restore the default Windows Script Extensions, File Types, and files. WINDOWS 98 & "WINDOWS SCRIPTING HOST" ===================================== Windows 98 includes a component called the "Windows Scripting Host" as an option in the Setup menu (Control Panel >> Add/Remove Programs >> Windows Setup >> Accessories...). Users can uncheck this box to uninstall the "Windows Scripting Host." What follows are details of what components comprise this "Windows Scripting Host" as well as what happens when uninstallation of the "Windows Scripting Host" is chosen from Add/Remove Programs >> Windows Setup >> Accessories. -------------------- Installed Components -------------------- Windows 98 & Windows 98SE ship with the following files, later versions of which are also found in the Windows Script packages available from Microsoft (e.g., versions 5.1, 5.5, or 5.6 beta): PROPER NAME Install Location ----------- ---------------- cscript.exe \WINDOWS\COMMAND wscript.exe \WINDOWS dispex.dll \WINDOWS\SYSTEM jscript.dll \WINDOWS\SYSTEM scrrun.dll \WINDOWS\SYSTEM vbscript.dll \WINDOWS\SYSTEM wshext.dll \WINDOWS\SYSTEM wshom.ocx \WINDOWS\SYSTEM Note that one of the components from the latest version of Windows Script 5.1, 5.5, and 5.6 (beta) -- SCROBJ.DLL (normally installed in \WINDOWS\SYSTEM) -- is not present here. The following File Types & Extensions are registered by default in Windows 98 & 98SE: Registered Extension File Type File Type ---------- --------- --------- JScript File .JS JSFile VBScript File .VBS VBSFile Windows Script .WSH WSHFile Host Setting File Note that three of the Extensions and File Types from the latest version of Windows Script 5.1, 5.5, and 5.6 (beta) -- .JSE (JSEFile), .VBE (VBEFile), and .WSF (WSFFile) -- are not present here. -------------- Uninstallation -------------- If one unchecks the "Windows Scripting Host" component in Add/Remove Programs >> Windows Setup >> Accessories, the following files and Registry entries are removed during uninstallation: -- Extensions: all removed -- File Types: all removed -- Files: all removed except... dispex.dll jscript.dll vbscript.dll With these three files still in place, Windows Update remains accessible and useable. And as we saw above, merely accessing Windows Update or using Windows Update (for *minor* updates) will not restore the files or Extensions and File Types that were uninstalled. "Windows Scripting Host" component is available as a setup option only on Windows 98 & Windows 98SE. The WSH is not available as a setup option for Windows ME. A "Windows Scripting Host" component is NOT available as a setup option for Windows 95 (any version), Windows NT 4.0, or Windows 2000. MORE INFORMATION ================ For links to more information on Windows Script, see: https://netfiles.uiuc.edu/ehowes/www/info10a.htm For links to utilities which can disable or "de-fang" Windows Script, see: https://netfiles.uiuc.edu/ehowes/www/soft4.htm One such utility (a batch file, in fact) is available on this very same site: https://netfiles.uiuc.edu/ehowes/www/resource2.htm#EBURGER If you are interested in completely uninstalling Windows Script from your computer, you can use another batch file utility that I wrote: the Windows Script (Host) Uninstaller: https://netfiles.uiuc.edu/ehowes/www/resource2.htm#WSH-UN CREDITS ======= Thanks to "CK," Graciella, Jack Benny, Randy Welborn, Gina Dennison, and Kevin McAleavey for prompting me to dig a little deeper into the relationship between Windows Script and Windows Update. Any errors in this document are, of course, solely my own fault and responsibility. ------------------------------------------------- Date: 4/21/01 Revised: 4/22/01, 4/28/01 From: https://netfiles.uiuc.edu/ehowes/www/ Made By: Eric L. Howes ------------------------------------------------- © 2000, 2001 Eric L. Howes