Microsoft has a patch available for download that has helped on some
This post from alt.windows98 may help with windows 98 SE power down problems.
On Sun, 18 Jul 1999 05:04:59 GMT, firstname.lastname@example.org (Frank Hagan) wrote:
:->There's a post on the Microsoft news group
:->(microsoft.public.win98.shell, if your ISP carries it) that is by
:->James A. Eshelman, under the name "email@example.com." I'll repeat it
:->here, but I may not have the most current version. Check that
:->newsgroup for the latest version:
:->FOURTEEN STEPS TO TROUBLESHOOTING WINDOWS SHUTDOWN (Ver 3.4)
:->[The following article is based on many sources, including Microsoft
:->Knowledge Base articles and input from individuals in the Microsoft
:->groups. In particular, most MVPs in the Desktop Systems section have
:->contributed to the contents and form of this article as it has
:->evolved. My thanks to all.]
:->Shutdown problems in Windows 95 and 98 can be caused by many factors
:->including, but not limited to: a damaged exit sound file; incorrectly
:->configured or damaged hardware; conflicting programs, or an
:->incompatible, damaged, or conflicting device driver. This article can
:->be used to troubleshoot the possible causes. If you don't know how to
:->use utilities such as MSConfig or SysEdit, see notes at the bottom of
:->NOTE ON WINDOWS 98 SECOND EDITION: There is a widespread shutdown
:->problem with Windows 98 Second Edition that has, at present, no
:->reliable solution. Microsoft is giving priority to resolving it. The
:->following fourteen troubleshooting steps should be tried, but might
:->not work. A patch is expected soon. Some fixes have been posted that
:->have limited applicability on some computers, but nothing so far has
:->amounted to a general solution.
:->This article does not, therefore, in its present form, attempt to
:->address the general Win98 SE shutdown problem comprehensively. (A very
:->few Win98 SE points are summarized near the end.) I am expecting an
:->eventual comprehensive article on this issue from MrScary once he
:->figures it all out!
:->FIRST STEP: DISABLE FAST SHUTDOWN (Skip this step if you are using
:->Launch MSCONFIG. Click Advanced. Place a check mark in the box next to
:->"Disable fast shutdown." (NOTE: If the box is already marked, go to
:->STEP TWO.) Click OK, then OK again. Test Windows shut down by
:->restarting the computer. (For proper troubleshooting, click Start |
:->Shut Down | Restart | OK. Give Windows three minutes to complete the
:->process before concluding that it is hung. This same procedure is
:->referred to in the following steps as, "Test Windows shut down.")
:->Disabling fast shutdown may solve the problem; but if it doesn't, go
:->to STEP TWO.
:->SECOND STEP: STARTUP/SHUTDOWN TROUBLESHOOTING WIZARD
:->Microsoft has an on-line Startup/Shutdown Troubleshooting Wizard at:
:->You can try this as your next option. It does overlap with some of the
:->THIRD STEP: RULE OUT DAMAGED EXIT SOUND FILE
:->In Control Panel, double-click Sounds. In the Events box, click Exit
:->Windows. In the Name box, click None. Click OK. Test Windows shut
:->down. If Windows does *not* hang, the problem may be a corrupt sound
:->file. Restore the file from your Windows disk or wherever you obtained
:->it and then test Windows shut down.
:->FOURTH STEP: RULE OUT CLOGGED TEMPORARY FILE FOLDERS
:->Manually deleting the contents of various temporary file folders may
:->solve the shutdown problem. Though these files can be relocated on a
:->given system, their default locations are usually on the C: drive.
:->Folders you might want to manually clean include: TEMP, Temporary
:->Internet Files, and MSDOWNLD.TMP.
:->FIFTH STEP: RULE OUT AUTOEXEC.BAT OR CONFIG.SYS COMMAND LINE PROBLEMS
:->(If there is neither an AUTOEXEC.BAT nor CONFIG.SYS file, or if both
:->are empty, go to STEP SIX. Otherwise:) Rename AUTOEXEC.BAT and
:->CONFIG.SYS to AUTOEXEC.TMP and CONFIG.TMP and test Windows shut down.
:->If it hangs, rename the files to the original names and go to STEP
:->SIX. If the system doesn't hang, rename the files and proceed with
:->Restart Windows and bring up the Boot Menu. Choose "Step-By-Step
:->Confirmation." Press Y at each of the following prompts if it occurs
:->(press N for any other prompts):
:->- Load DoubleSpace driver
:->- Process the system registry
:->- Load the Windows graphical user interface
:->- Load all Windows drivers
:->After Windows finishes loading, test Windows shut down. If the system
:->hangs, go to STEP SIX. If it shuts down properly, the problem may be
:->caused by a command line in the AUTOEXEC.BAT or CONFIG.SYS file.
:->To determine which line is causing the problem, follow these steps:
:->Restart Windows, bringing up the Boot Menu as before. Press Y for each
:->of the prompts listed above, plus one *additional* command. Press N
:->for all other prompts. (You will cycle through the additional lines,
:->selecting a *different* additional command each time until you have
:->gone through them all.) Each time, after Windows finishes loading,
:->test Windows shut down. Repeat the above until the shutdown problem
:->When the shutdown problem occurs, you have identified the command
:->causing the problem. Disable the command (using SYSEDIT to edit the
:->file containing the command, or, in Win98, MSCONFIG to remove the
:->check mark in front of the problematic item).
:->NOTE: MS-MVP Sky King has pointed out that CONFIG or AUTOEXEC files
:->ending with extensions of WIN, WOS, or W04, if they exist, will be
:->processed instead of CONFIG.SYS and AUTOEXEC.BAT. You may wish to
:->check for the existence of these files as well, and to apply the above
:->procedure to them also.
:->SIXTH STEP: RULE OUT VIRTUAL DEVICE DRIVER / SYSTEM.INI PROBLEMS
:->Launch SYSEDIT. Click on the SYSTEM.INI window. Examine the section
:->[386Enh] and place a semicolon (;) at the beginning of each line that
:->begins with "DEVICE=" and ends with ".386." Save the changes and exit
:->SYSEDIT. (NOTE: In Win98 you can use MSCONFIG and merely uncheck such
:->lines in the [386Enh] section.) Reboot, then test Windows shut down.
:->If Windows hangs, restore the SYSTEM.INI file to its original
:->configuration. If Windows does *not* hang during shutdown, a virtual
:->device driver may be causing the problem. Contact
:->the driver's manufacturer for assistance.
:->SEVENTH STEP: RULE OUT WIN.INI COMMAND LINE PROBLEMS
:->Launch SYSEDIT. Click on the WIN.INI window and look for any lines
:->beginning with LOAD= or RUN=. Place a semicolon (;) at the beginning
:->of these lines if they have entries following the equal (=) sign. Save
:->the changes to the WIN.INI file and exit SYSEDIT. If you did not make
:->changes, go to STEP EIGHT; otherwise, reboot and then test Windows
:->shut down. If Windows continues to hang, remove the semicolons, save
:->the file and go to STEP EIGHT. If Windows does *not* hang, one of the
:->disabled program entries may be to blame. To determine the problem
:->program, re-enable them one at a time by removing the semicolon and
:->resaving the file. After each program is enabled, test Windows shut
:->EIGHTH STEP: RULE OUT PROGRAMS LOADED FROM STARTUP FOLDER
:->Restart Windows without any Startup folder programs loading. FOR
:->WIN98: Use MSCONFIG. Click Selective Startup. Remove the check mark
:->from in front of "Load startup group items." Restart Windows. FOR
:->WIN95: Restart the computer and, as soon as the Windows desktop
:->wallpaper appears, press and hold the SHIFT key until Windows 95
:->finishes loading. After doing one of these procedures, test Windows
:->shut down. If Windows hangs, go to STEP NINE. If Windows shuts down
:->properly, determine the culprit by ruling out the programs one-by-one:
:->FOR WIN98: Use MSCONFIG. On the Startup tab, place a check mark next
:->to the first program item listed. Click OK, then OK. FOR WIN95:
:->Manually remove all but one of the shortcut icons from the Startup
:->FOR BOTH SYSTEMS:
:->Test Windows shut down. If Windows shuts down properly, then the
:->program that remained is not causing the problem. Restore another
:->startup program per the appropriate method above. After each program
:->is restored, test Windows shut down. Continue re-enabling programs
:->until you either find the problem program (there may be more than one)
:->or all programs have been restored.
:->IMPORTANT WIN95 NOTE: Holding down the SHIFT key as soon as Windows
:->to load will launch Win95 in Safe Mode. (If you wait for the desktop
:->wallpaper to appear, it only suppresses Startup items.) If Safe Mode
:->used, not only are items in the Startup folder not loaded when this
:->but Windows also uses only basic system drivers, does not launch
:->programs normally launched from the Registry, does not execute
:->AUTOEXEC.BAT (already tested above), does not launch certain sections
:->System.ini file (already tested above), does not process the HIMEM.SYS
:->IFSHLP.SYS files, and does not load DoubleSpace or DriveSpace if
:->Therefore, for Win95 computers, if (1) all previous troubleshooting
:->have passed, and (2) this step causes proper shutdown behavior after
:->in Safe Mode, and (3) removing all items in the Startup folder then
:->rebooting in normal mode does *not* produce proper shutdown behavior,
:->Registry startup items, HIMEM.SYS, IFSHLP.SYS, and DoubleSpace or
:->must be considered as likely causes of the problem. Detailed
:->for troubleshooting these items are not given in the present article;
:->do not know how to test these steps, please seek help in the online
:->support newsgroups for these specific tasks.
:->NINTH STEP: RULE OUT EMM386-RELATED MEMORY CONFLICTS
:->A memory conflict sometimes exists when Emm386.exe is not loaded from
:->CONFIG.SYS file. To test for this, launch SYSEDIT. Click the
:->window. In the CONFIG.SYS file, make sure the following lines exist in
:->order, at the very beginning of the file:
:->DEVICE=C:\WINDOWS\EMM386.EXE NOEMS X=A000-F7FF
:->If you do not have a CONFIG.SYS file, create one with these three
:->Save the modified CONFIG.SYS and close SYSEDIT. Reboot, then test
:->shut down. If the system hangs, restore your CONFIG.SYS file to its
:->configuration. If it shuts down properly, see the following Microsoft
:->Knowledge Base article:
:->"Locating and Excluding RAM/ROM Addresses in the UMA"
:->TENTH STEP: RULE OUT ADVANCED POWER MANAGEMENT (APM) PROBLEMS
:->(Not all computers have APM features. If yours is one of them, go to
:->ELEVEN. Otherwise:) Right-click on My Computer, select Properties, and
:->the Device Manager tab. Double-click the System Devices branch to
:->Double-click Advanced Power Management Support in the device list.
:->Settings tab. Click the Enable Power Management check box to clear it.
:->OK until you return to Control Panel. (NOTE: This box doesn't exist in
:->SE. Disable APM from Control Panel | Power.) Reboot, then test Windows
:->down. If Windows shuts down properly, the problem may be caused by
:->contact the computer's manufacturer for assistance. NOTE: For
:->information about shutdown problems with APM enabled, see Microsoft
:->Knowledge Base article:
:->"Shutdown Hangs After 'Please Wait While...' Screen"
:->ELEVENTH STEP: RULE OUT WINDOWS FILE SYSTEM SETTINGS
:->Right-click on My Computer and select Properties. Click the
:->Click File System. Click the Troubleshooting tab. Mark all the check
:->click OK, click Close and click Yes. Reboot, then test Windows shut
:->Windows shuts down properly, the problem is related to the File System
:->settings. Go back and uncheck each box one at a time. Reboot and test
:->Windows shut down after each change to identify which item is the
:->TWELFTH STEP: RULE OUT WINDOWS DEVICE DRIVER PROBLEMS
:->See if a Windows device driver is causing the problem or if an
:->device is configured incorrectly or is improperly functioning. Right
:->on My Computer and select Properties. Click the Hardware Profiles tab.
:->the hardware profile you are currently using, and then click Copy.
:->"Test Configuration" in the To box. Click OK. Click the Device Manager
:->Double-click any device, then click the Test Configuration check box
:->clear it. Repeat this step until you have disabled all devices but DO
:->disable any system devices. When you are prompted to restart Windows,
:->NO. (NOTE: If you disabled a PCI hard disk controller, choose Yes to
:->Windows. PCI hard disk controllers cannot be unloaded dynamically.)
:->Restart Windows and you will receive the following message: "Windows
:->determine what configuration your computer is in. Select one of the
:->following:" Choose Test Configuration from the list of configurations.
:->Windows starts, you will receive the following error message: "Your
:->Adapter is disabled." To correct the problem, click OK to open Device
:->Manager. When the Display Properties dialog box opens, click Cancel.
:->Windows shut down. If Windows hangs, go to STEP THIRTEEN. If Windows
:->down properly, the problem may be caused by a Windows device driver or
:->device installed in your computer that is configured incorrectly or is
:->To determine which device driver or device is causing the problem, go
:->into Device Manager. Double-click a device that you disabled in step E
:->above, then click the Test Configuration check box to select it. When
:->prompted to restart Windows, click Yes. Test Windows shut down. Repeat
:->with each device until the shutdown problem recurs. If the problem
:->you have identified the device or device driver causing the problem.
:->NOTE: If the shutdown problem is being caused by a Plug and Play
:->is configured incorrectly or isn't functioning properly, removing the
:->from the current hardware profile will correct the problem. After you
:->the device from the current hardware profile and restart Windows, the
:->drivers associated with the device are removed from memory and the
:->problem does not occur. However, as Windows restarts, the Plug and
:->device will be detected automatically and installed in the current
:->profile. When you restart Windows a second time, the drivers
:->the device are again loaded in memory and the shutdown problem
:->If Windows continues to hang on shutdown after you complete steps the
:->steps, reinstall Windows to a different folder to rule out the
:->of damaged files. If your computer has a Plug and Play BIOS, reinstall
:->Windows using the "setup /P I" command to rule out a defective Plug
:->If Windows still hangs during the shutdown process after you reinstall
:->your computer may have faulty hardware or faulty system components
:->RAM, the CPU, the motherboard or an internal or external cache.
:->computer's manufacturer for assistance.
:->THIRTEENTH STEP: USE BOOTLOG.TXT TO IDENTIFY THE PROBLEM
:->If Windows still hangs during the shutdown process, create a
:->file by restarting the computer, bringing up the Boot Menu and
:->option to create a boot log. Let Windows load fully and then reboot
:->normally. Examine C:\BOOTLOG.TXT for "Terminate=" entries. These
:->located at the end of the file and may provide clues as to the cause
:->problem. Each "Terminate=" entry should have a matching
:->entry on a successful shutdown. If the last line in the BOOTLOG.TXT
:->"EndTerminate=KERNEL," Windows shut down successfully.
:->If the last line in BOOTLOG.TXT is one of the following entries, check
:->listed possible cause:
:->Terminate=Query Drivers: Possible QEMM or other memory manager issue.
:->Terminate=Unload Network: Possible conflict with real-mode network
:->Terminate=Reset Display: Disable video shadowing. You may also need an
:->updated video driver.
:->Terminate=RIT: Possible timer-related problems with the sound card or
:->Terminate=Win32: Problem with a 32-bit program blocking a thread.
:->Microsoft Visual C for Windows.
:->FOURTEENTH STEP: OTHER SOLUTIONS
:->(1) The PC Speaker driver (SPEAKER.DRV) can cause Windows to stop
:->at shutdown or startup. To disable the PC Speaker driver, disable the
:->"wave=speaker.drv" line in the SYSTEM.INI file, then restart the
:->(2) On a computer with a BIOS that expects IRQ 12 to be in use by a
:->PS/2-style mouse port, but instead has a software-configurable
:->device (such as a Plug and Play adapter) using IRQ 12, Windows can
:->shutdown. To work around this problem, reserve IRQ 12 in Device
:->change the IRQ for the software-configurable device in Device Manager.
:->may also want to consider upgrading the BIOS in your computer to a
:->version.) To reserve an IRQ with Device Manager: In Control Panel,
:->double-click System. On the Device Manager tab, double-click Computer.
:->the Reserve Resources tab, click the Interrupt Request (IRQ) option,
:->then click Add. In the Value box, click the IRQ you want to reserve.
:->OK until you return to Control Panel.
:->(3) If a network card is installed in the computer, do the following:
:->the network in Device Manager. Shut down Windows. Physically remove
:->network card. Restart Windows. Shut down Windows (observe whether it
:->down normally). Reinstall the network card. Restart Windows and let it
:->detect the card as new hardware. (This has been known to work in at
:->one case in Win98 SE, and should be tried for other versions of
:->(4) If your anti-virus software is set to scan your floppy drives on
:->shutdown, this can result in various symptoms including the computer
:->on shutdown. Often (but not always) a clue will be that the floppy
:->light comes on during shutdown. The solution is to disable this
:->feature in the anti-virus program.
:->(5) If the previous steps do not resolve the problem, try resetting
:->settings back to factory defaults. For information about changing CMOS
:->settings in your computer, consult the computer's documentation or
:->manufacturer. WARNING: Before you reset the computer's CMOS settings
:->the factory defaults, make sure to write down the CMOS settings.
:->not try this step unless you know what you are doing -- mistakes in
:->step can result in your computer not working at all!
:->WINDOWS WITH INTERNET EXPLORER SCENARIOS:
:->(1) If Internet Explorer 4.01 is installed, and one or more network
:->are mapped on your computer with the Desktop Update component
:->update to Internet Explorer 5 or apply the IE4.01 Service Pack 1 from
:->(2) If IE (any version) is installed and your user profile contains a
:->Temporary Internet Files folder (cache), Windows can hang on shutdown.
:->work around this behavior, use any of the following methods: METHOD 1:
:->your Temporary Internet Files folder each time you quit Internet
:->METHOD 2: Maintain each user's temporary Internet files in the user's
:->directory. Although this still consumes server storage, it does not
:->that the files be copied to the server when users log off. METHOD 3:
:->Maintain all users' temporary Internet files in a shared common
:->that if you use this method, all users' cookies are stored in the same
:->location. METHOD 4: Maintain each user's temporary Internet files on
:->local drive in a location other than the user's profile folder. This
:->most efficient method. However, this does not allow a user's cookies
:->follow the user to other stations.
:->WIN98 ONLY SCENARIOS:
:->(1) If you are using Cisco TCP/IP Suite 100 as your TCP/IP stack,
:->and install Microsoft TCP/IP. For step-by-step instructions, see the
:->Microsoft Knowledge Base article at:
:->(2) If you are using Norton AntiVirus with the Auto-Protect feature
:->disable Auto-Protect, then obtain the latest LiveUpdate for NAV from
:->Symantec's Web site.
:->(3) If your computer hangs at shutdown and it either uses Advanced
:->Configuration and Power Interface (ACPI) and the Fast Shutdown feature
:->disabled, or it contains a Matsonic BIOS and the "USB Function for
:->option is enabled in the BIOS, then you may receive one or both of the
:->following messages: Windows is shutting down. [-OR-] It's now safe to
:->off your computer. See
:->for details on a supported fix that corrects this problem. It has not
:->fully regression tested and should be applied only to computers
:->this specific problem. Also see Windows Startup
:->and Shutdown Issues:
:->WIN98 SECOND EDITION ONLY SCENARIOS:
:->(I promised a few; but this problem is far from solved)
:->(1) Check with your computer or BIOS manufacturer to see if there are
:->BIOS updates available for your system, and install them. If you BIOS
:->of date, while attempting to shut down Win98 SE may hang, or may
:->instead of shut down. (This is because Win98 SE includes updates for
:->Advanced Configuration and Power Interface (ACPI), OnNow, and Advanced
:->Management (APM) and may require the latest BIOS upgrade.) For
:->problem is known to exist with the Intel AL440LX motherboard using
:->BIOS version P07; a new BIOS version, P12 or later, is needed. Similar
:->problems occur with a D-Link DFE 530TX network adapter installed; the
:->solution is to obtain and install an updated driver (contact D-Link
:->(2) Microsoft has found that this issue can occur if your video
:->requires an interrupt request (IRQ) in MS-DOS mode, but your
:->does not assign one to it. Upgrading the BIOS may be an important
:->step. MS advises one of the following resolutions be used: (A) Check
:->computer's BIOS for a setting to assign an IRQ to the video adapter.
:->information about how to check your computer's BIOS, contact your
:->manufacturer.) (B) Contact the manufacturer of your video adapter to
:->about an updated BIOS for your video adapter. (C) Contact the
:->of your motherboard to inquire about an updated BIOS for your
:->(NOTE: If your computer is configured to use multiple monitor support,
:->may be able to shut down properly.)
:->(3) On several Win98 SE machines, disabling Advanced Power Management
:->and enabling Advanced Configuration and Power Interface (ACPI) has
:->the problem. Sometimes this solution was worked on its own; in other
:->it has worked only in combination with other actions; and in still
:->has not worked at all.
:->(4) Alex Nichol found two items that in combination cause Win98 SE on
:->computer to hang on the LOGOW.SYS waiting-to-shutdown message. (a) A
:->CONFIG.SYS, BUFFERSHIGH=10, results in the "Now Safe" screen (the
:->graphic) not being displayed on full shutdown, leaving the machine
:->on 'Please wait', even though the shutdown completed so that scandisk
:->not run after a reset. Raising the number to 15 cured the problem (as
:->independently, commenting out either of two DEVICEHIGH lines in the
:->file). (b) The setting in MSCONFIG | Advanced to 'Enable Pentium F0
:->workaround' causes the system to hang on the 'please wait' screen when
:->shutting down to a restart.
:->(5) MS-MVP MrScary found, in some cases, that IRQ steering and device
:->enumeration issues were the cause of these shutdown problems: Right
:->My Computer and select Properties. Click the Device Manager tab. Click
:->Devices by type" and open "System Devices" found at the bottom of the
:->tree. Highlight "PCI bus" and click on the Properties button. Adjust
:->disable the settings under the IRQ Steering and/or the Settings tab to
:->the desired results. (As a precaution, note how you found these
:->before you attempt to change them.) FIRST try changing the Device
:->Enumeration under the 'Settings' tab from Hardware to Bios. If this
:->solve the problem, then experiment with enabling or disabling all the
:->combinations of possible settings to try to get the desired results.
:->times, the BIOS setting that you may or may not have, PnP Aware OS,
:->a bearing on these settings. (See below for more info.) Make sure you
:->full reboot after every change while testing.
:->(6) A similar solution that has worked for some people: Right-click on
:->Computer and select Properties. Click the Device Manager tab. Expand
:->Devices. Double-click on PCI bus. Click the IRQ steering tab. Clear
:->checkmark from the last box, "Get IRQ Table From Real Mode PCIBIOS 2.1
:->(7) Bill Snyder has reported that the shutdown problem in SE, as well
:->several IRQ conflicts he was experiencing, were resolved by the
:->(1) In the computer's BIOS, turn OFF "PnP [Plug-and-Play] Operating
:->(2) in Device Manager/System Settings/PCI Bus Properties, set Device
:->Enumeration to BIOS and turn off IRQ steering. (These settings pretend
:->Win 98 SE is not a PnP operating system.)
:->(8) Clayton Burton has suggested that replacing the Win98 SE copy of
:->CONFIGMG.VXD with the copy from the pre-SE (original) version of Win98
:->solve the underlying problem. If this approach is used, the file
:->extracted to the C:\WINDOWS\SYSTEM\VMM32 folder, and also to the
:->C:\WINDOWS\SYSTEM folder. Please note, this has not been widely tested
:->its results are therefore unknown. CONFIGMG.VXD is the Windows
:->manager virtual device. The Win98 Original Edition copy will be
:->4.10.1998, 115,665 bytes in size. The Win98 SE copy will be version
:->4.10.2222, 125,057 bytes in size.
:->(9) At least one person has solved this problem by enabling Fast
:->from the disabled default, shutting down and discovering this didn't
:->(causing the computer to restart instead of shut down), and then
:->Fast Shutdown again. This time, it worked and the computer shut down
:->=========== HOW TO USE UTILITIES ===========
:->USING MSCONFIG (WIN 98 ONLY) or SYSEDIT (WIN98 or WIN95)
:->Click Start | Run (or, on an expanded feature keyboard, type Win+R).
:->MSCONFIG or SYSEDIT (whichever you intend to use). Click OK.
:->BRINGING UP THE BOOT MENU
:->FOR WIN98: Restart Windows. Press the Ctrl key as your computer starts
:->holding it until the Boot Menu appears.
:->FOR WIN95: Restart Windows. As soon as the message "Starting Windows
:->appears, press and hold the F8 key until the Boot Menu appears.