How to Perform Clean-Boot Troubleshooting for Windows 98

ID: Q192926

The information in this article applies to:
IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

SUMMARY

This article describes how to perform clean-boot troubleshooting for Windows 98.


MORE INFORMATION

Clean-boot troubleshooting refers to methods of reducing problems that may occur because of your computer's environment. Many problems running Windows or programs occur because of conflicting drivers, terminate-and-stay- resident programs (TSRs), and other settings that are loaded when your computer starts. Your computer's environment includes settings from the following files

These files are loaded as part of the boot process as Windows starts and help create the environment used by the operating system (OS) and programs.

For information about the files listed above, see the "Notes" section of this article.


Using System Configuration Utility

Windows 98 includes a System Configuration Utility tool (Msconfig.exe) to make performing a clean boot much easier. Use one of the following methods to run System Configuration Utility:

To use System Configuration Utility to perform a clean boot, use one of the methods listed above to start the program, and then follow these steps:

  1. On the General tab, click Selective Startup, and then click to clear the following check boxes: 

    
    - Process Config.sys File
    - Process Autoexec.bat File
    - Process Winstart.bat File (if available)
    - Process System.ini File
    - Process Win.ini File
    - Load Startup Group Items


  2. Click OK, and then restart your computer when you are prompted.


Each check box (except for Load Startup Group Items) represents files that are renamed with a troubleshoot (.tsh) extension when you clear the check box. Load Startup Group Items represents icons in the Startup folder or entries in the following registry keys registry:

When you click the Load Startup Group Items check box to clear it, the registry entries are written to the following keys:

The icons in the Startup folder are moved to the Disabled Startup Items folder in the Windows\Start Menu\Programs folder.

When you click to clear an entry in a file, a "remark" statement is placed at the beginning of each line. For the Config.sys and Autoexec.bat files, "rem tshoot" is used, followed by a space. For the System.ini and Win.ini files, "; tshoot" is used, followed by a space. These remarks are removed when you click to select an entry that was cleared previously. When you click to select an item in the Startup tab, the registry entry is restored to its original location.

You must restart your computer each time you make a change to any of the startup files because they are only read when your computer starts.

If System Configuration Utility is unavailable for some reason, clean-boot manually. For more information, see the "Clean Boot" section of the following article in the Microsoft Knowledge Base:
ARTICLE-ID: Q129260
TITLE : Windows 95 Setup: Description and Troubleshooting Steps



Narrowing the Focus

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).
If your computer no longer displays the problem, you can narrow the focus of the problem. This process involves using System Configuration Utility to restore files or file entries until you determine the specific entry that is causing the problem. This process can be called "restoring by halves," because you are restoring half of the entries you had previously removed, restarting your computer, and then testing to see if the problem persists.

To troubleshoot with this process, follow these steps:

  1. Clear all the entries under Selective Startup on the General tab in System Configuration Utility, click OK, and then restart your computer when you are prompted.


  2. If the problem persists, use the Advanced Troubleshooting Settings tab in System Configuration Utility. See the "Advanced Clean-Boot Troubleshooting" section of this article for more details.


  3. If the problem persists, restart your computer in Safe mode and test. If the problem persists in Safe mode, contact technical support. For information about how to start your computer in Safe mode, see the following article in the Microsoft Knowledge Base:
    ARTICLE-ID: Q180902
    TITLE : How to Start a Windows 98-Based Computer in Safe Mode


  4. If the problem does not occur when you clear all the entries, click to select the following entries, restart your computer, and then test: 

    
    - Process System.ini File
    - Process Win.ini File


  5. If the problem does occur when these files are processed, the problem is related to one of these files. In that case, click to clear one of the files. If the problem occurs, an entry in the file that is selected is causing the problem. Go to step 9.


  6. If the problem does not occur after the System.ini and Win.ini files are selected, click to select the Process Autoexec.bat File check box, restart your computer, and then test. If the problem occurs, an entry in the Autoexec.bat file is responsible. Go to step 9.


  7. If the problem does not occur after selecting the Autoexec.bat file, click to select the Process Config.sys File check box, restart your computer, and then test. If the problem occurs, an entry in the Config.sys file is responsible. If the problem does not occur, an item in the Startup group or Winstart.bat file is responsible.


  8. Click to select the Process Winstart.bat File check box, restart your computer, and then test. If the problem does not occur, an item in the Load Startup Items is responsible.


  9. Click to select the check box for file causing the problem on the General tab, click the tab representing that file, click to clear the bottom half of the list of check boxes, restart your computer, and then test.

    For example, if an entry in the Config.sys file is responsible, click to select the Process Config.sys File check box on the General tab, click the Config.sys tab, click to clear the bottom four of eight entries, click OK, and then restart your computer when you are prompted.


  10. If the problem persists, one of the entries that is selected is causing the problem. If the problem does not occur, one of the entries that is cleared is causing the problem.

    In the first case, click to clear half of the remaining entries that are selected, restart your computer, and then test. In the second case, click to select half of the file entries that are cleared, restart your computer, and then test.




Using this process, you can isolate the specific file entry that is causing the problem after restarting your computer several times. Once the specific file entry that is causing the problem is determined, you should edit the appropriate file or registry entry to remove this entry and return the System Configuration Utility to Normal Startup.

To return the System Configuration Utility to Normal Startup, follow these steps:

1. Click Start, click Run, type "msconfig" (without quotation marks) in the Open box, and then click OK.

2. On the General tab, click Normal Startup, and then click OK.

3. When you are prompted to restart the computer, click No.

If the problem entry is in the Config.sys, Autoexec.bat, Win.ini, or System.ini file, use System Configuration Editor (Sysedit.exe) to edit the file and disable the appropriate line(s). To do so, follow these steps:

1. Click Start, click Run, type "sysedit" (without quotation marks) in the Open box, and then click OK.

2. On the Window menu, click the appropriate file name (for example, C:\Windows\System.ini).

3. Type "REM" (without quotation marks), followed by a space at the beginning of the appropriate line that is causing the problem.

4. On the File menu, click Save.

5. On the File menu, click Exit.

6. Restart your computer.

If the problem entry is a program on the Startup tab, remove the program from the Startup folder or delete the program from the registry. To remove the program from the Startup folder, follow these steps:

1. Click Start, point to Settings, and then click Taskbar And Start Menu.

2. Click the Start Menu Programs tab, and then click Remove.

3. Double-click Startup, click the appropriate entry, and then click remove.

4. Click Close, click OK, and then restart your computer.

If the problem entry is not in the Startup folder, the program may be loading in the registry. To remove the entry from the registry, follow these steps:

1. Using Registry Editor, export the appropriate registry key (for backup purposes):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\ RunServices
2. Delete the <filename.exe> value from the appropriate registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\ RunServices


where <filename.exe> is the name of the file that is causing the problem.

3. Quit Registry Editor and restart the computer.


A Troubleshooting Example

The following troubleshooting example illustrates the process for determining a specific entry causing a problem with a program:

  1. You click to clear all the files in the Selective Startup option, and then restart your computer. The problem no longer occurs.


  2. If the problem still occurs, you have a more serious problem with your computer than clean booting can solve. See the "Advanced Clean-Boot Troubleshooting" section of this article, use the Microsoft Knowledge Base to query for information about your problem, or contact Microsoft Technical Support.


  3. On the General tab in System Configuration Utility, click Selective Startup, click to select the following check boxes, click OK, and then restart your computer when you are prompted: 

    
    - Process Win.ini File
    - Process System.ini File


  4. You test your program, and the problem does not occur. You click the following check box, click OK, and then restart your computer when you are prompted: 

    
    - Process Autoexec.bat File


    If the problem occurs, then you click to select the following check box, click OK, and then restart your computer when you are prompted: 

    
    - Process System.ini File


  5. You test the program, and the problem does not occur. You perform the following steps:

    a. Click to select the "Process Config.sys file" check box, and then click the Config.sys tab.

    b. On the Config.sys tab, click to clear the first half of the entries in the list of check boxes. In this example, you click to clear the first four of eight check boxes, where each check box represents a line in the Config.sys file.

    c. Click OK, and then restart the computer when you are prompted.


  6. You test the program, and the problem does not occur. You click to select the first half of the entries (the first two in this example), click OK, and then restart your computer when you are prompted.


  7. You test the program, and the problem does not occur. You click to select the first half of the entries (the first entry in this example), click OK, and then restart your computer when you are prompted.


  8. You test the program, and the problem does not occur. You have isolated the problem to a single entry. To complete the process, on the General tab in System Configuration Utility, click "Normal startup - load all device drivers and software," click OK, and then click Yes when you are prompted to restart your computer.


  9. The entry may be required to run another program and gain access to hardware on your computer. If this is the case, check the documentation for the software or hardware manufacturer who added the line to the file or contact the manufacturer to get an updated driver.




Tips for Clean-Boot Troubleshooting

The process of removing all the startup files listed in the Selective Startup section on the General tab of System Configuration Utility and then restoring them by halves can sometimes be reduced by disabling the following entries:

See the "Using System Configuration Utility" section of this article for information about how file entries are disabled for different boot files.


Advanced Clean-Boot Troubleshooting

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it.

If you use the Selective Startup option on the General tab in System Configuration Utility to clear all the boot entries and the problem still occurs, there are other troubleshooting steps you can perform. You can also:

To check the items on the Advanced Troubleshooting Settings tab:

  1. Click Start, click Run, type "msconfig.exe" (without quotation marks), and then click OK.


  2. On the General tab, click Advanced, click to select each check box, click OK, and then restart your computer when you are prompted.


  3. Use the process of restoring by halves to isolate the problem. See the "Narrowing the Focus" section of this article to learn more about this process. Many of the problems that are isolated through this process are related to hardware or driver-compatibility issues. When you isolate the problem, contact the hardware or software manufacturer of the affected driver for a possible updated driver, or for information about compatibility issues with Windows 98.


For more information about the Advanced Troubleshooting Settings tab in System Configuration Utility, see the following article in the Microsoft Knowledge Base:
ARTICLE-ID: Q181966
TITLE : System Configuration Utility Advanced Troubleshooting> Settings


To change your display adapter driver to Standard VGA, follow these steps:

  1. Click Start, point to Settings, click Control Panel, and then double-click Display.


  2. Click the Settings tab, click Advanced, click the Adapter tab, and then click Change.


  3. Click Next, click "Display a list of all the drivers in a specific location, so you can select the driver you want," and then click Next.


  4. Click Show All Hardware, click Standard Display Types in the Manufacturer's box, click Standard Display Adapter (VGA) in the Models box, and then click Next.


  5. Click Yes, click Next, and then click Finish.


  6. Click Close, click Close, and then click Yes when you are prompted to restart your computer.

    If changing your display adapter to the Standard VGA driver causes the problem not to occur, contact your display adapter manufacturer for an updated Windows 98 display adapter driver.


For more information about how to troubleshoot display problems, see the following article in the Microsoft Knowledge Base:
ARTICLE-ID: Q127139
TITLE : Troubleshooting Video Problems in Windows


To select Diagnostic Startup and avoid loading static .vxd files, follow these steps:

  1. Click Start, click Run, type "msconfig.exe" (without quotation marks), and then click OK.


  2. On the General tab, click "Diagnostic startup - interactively load device drivers and software," and then click OK.


  3. Restart your computer when you are prompted.


  4. On the Microsoft Windows 98 Startup menu, choose Step-By-Step Confirmation, and then press ENTER.


  5. See the following table for the choices and your response: 

    

      Prompt                                            Response
      ----------------------------------------------------------
      Load DoubleSpace Driver?                           Yes
      Process the system registry                        Yes
      Create a startup log file (BOOTLOG.TXT)            Yes
      Process your startup device drivers (CONFIG.SYS)   No
      DEVICE=C:\WINDOWS\HIMEM.SYS                        Yes
      DEVICE=C:\WINDOWS\DBLBUFF.SYS                      Yes
      DEVICEHIGH=C:\WINDOWS\IFSHLP.SYS                   Yes
      Process your startup command file (AUTOEXEC.BAT)   No
      Load the Windows graphical user interface          Yes
      Load all Windows drivers?                          Yes


    Note that the location of the Windows folder may vary. You may not see all these prompts, depending on the startup files present on your computer. Use ENTER to respond with Yes, ESC to respond with No.


  6. Note each static .vxd file and respond with No to avoid loading each file. See the following partial list of Microsoft static .vxd files: 

    
      Name of static .vxd file   Provides support for
      -----------------------------------------------
      Vnetsup.vxd                Microsoft Networking
      Ndis.vxd                   Microsoft Networking
      Ndis2sup.vxd               Microsoft Networking
      Javasup.vxd                Microsoft Java
      Vrtwd.386                  Clock
      Vfixd.vxd                  Video Phone helper
      Vnetbios.vxd               Microsoft Networking
      Vserver.vxd                Microsoft Networking
      Vredir.vxd                 Microsoft Networking
      Dfs.vxd                    Microsoft Networking
      Ndiswan.vxd                Microsoft Networking
      Msmouse.vxd                Microsoft Mouse




  7. If the problem no longer occurs, repeat steps 1-6, but respond with Yes to each of the files in the list above. If the problem no longer occurs, it is not related to any of the static .vxd files listed above.


  8. Use the process of restoring by halves to isolate the static .vxd file responsible for the problem.


  9. Delete the incompatible static .vxd folder from the following key in the registry:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD




Notes

The Msdos.sys file contains basic information about the location of the Windows folder and startup files, and other options. Some of these options can be edited using the Advanced Troubleshooting Settings tab in System Configuration Utility.

For more information about the Msdos.sys file, see the following article in the Microsoft Knowledge Base:
ARTICLE-ID: Q118579
TITLE : Contents of the Windows Msdos.sys File


The Config.sys file is provided for backwards compatibility with MS-DOS- based and older Windows-based programs and may not be present on your computer. It loads low-level MS-DOS-based drivers, many with a system (.sys) extension.

The Autoexec.bat file is also provided for backwards compatibility with MS-DOS-based and older Windows-based programs and may not be present on your computer. It loads MS-DOS-based programs, often with .com and .exe extensions.

The Winboot.ini file is a temporary version of the Msdos.sys file that may be present if a program is making changes to your computer that may affect the boot process. Under normal conditions, it is deleted after the program is complete, resides in the root directory, and overrides settings in the Msdos.sys file.

The Winstart.bat file may not be available as a check box on the General tab in System Configuration Utility. The Winstart.bat file is created for programs that need to run an MS-DOS-based program to enable functionality of a Windows-based program. Most users do not have this program.

The System.ini file contains information about your computer's settings for specific hardware. This file must be present in the Windows folder for Windows to start. It is used to load various drivers including sound and video adapter drivers. It may also contain additional 16-bit drivers for hardware does not use 32-bit drivers.

When you click to clear the Process System.ini File check box in System Configuration Utility and restart your computer, the following changes take place:

The Win.ini file contains information specific to the overall appearance of Windows. This file must be present in the Windows folder or it is re- created by Windows, is read at startup for backwards-compatibility with Windows 3.x, and many of the settings are duplicated in the registry. When you clear the Process Win.ini File check box in System Configuration Utility, a generic version of the Win.ini file is created.

The Wininit.ini file is used to complete the installation of various components for Windows and third-party products. Each time a program needs to copy or remove a file that is in use, instructions are written to the Wininit.ini file. Windows checks for the presence of the Wininit.ini file during the boot process and, if found, performs the instructions. Rename this file to troubleshoot problems, if present.

The System.dat file is one of two registry files that are required to start Windows. The System.dat is similar to the System.ini file, containing computer and software settings. The Load Startup Group option contains the entries that are loaded from the System.dat portion of the registry.

The User.dat file is the second of two registry files that are required to start Windows. The User.dat file is similar to the Win.ini file in that it contains information for running specific programs and information about the overall appearance of Windows.

You can use System Configuration Utility to create a backup of the startup files described in this article. To do so, click Create Backup on the General tab in System Configuration Utility. You can choose to save the files to a folder on one of your hard disks, or save it to a floppy disk (recommended).

Static .vxd files are used to load virtual hardware and software drivers. Many third-party manufacturers add their own virtual drivers (static .vxd files).

Additional query words: 


Keywords          : kbenv kbtool kbtshoot win98 
Version           : WINDOWS:
Platform          : WINDOWS 
Issue type        : kbhowto

Last Reviewed: February 27, 1999