Microsoft KB 293623 for IE

 

This article was previously published under Q293623

Important This article discusses a very specific Internet Explorer crash in older versions of the script debugger (Pdm.dll) that was included with Office 2000 and Visual Studio 6 (pre-SP3 version). If you view the error report details listed in the "Symptoms" section, and Pdm.dll version 6.0.0.8169 is not listed under Module Name, then this article does not apply to you.
:

You receive the following error message in Windows Explorer, Internet Explorer, or MSN Explorer:

Microsoft Internet Explorer has encountered a problem and needs to close. We are sorry for the inconvenience.

In the error message, click the click here link at the bottom of the message box. For this particular error, the following error signature information is displayed:

Program Name   Program Version   Module Name   Module Version   Offset
   ------------------------------------------------------------------------
   Explorer.exe   various           Pdm.dll       6.0.0.8169       0001259d
   Iexplore.exe   various           Pdm.dll       6.0.0.8169       0001259d
   Netdocs.exe    various           Pdm.dll       6.0.0.8169       0001259d
   Msn6.exe       various           Pdm.dll       6.0.0.8169       0001259d

If your error signature information does not match this one, this article does not apply to you.

This error message occurs when the Pdm.dll file is out of date. 

This resolution requires you either to disable script debugging or to update the Pdm.dll file. If you must have the script debugging capability, you have to update the Pdm.dll file. To update your version of the Pdm.dll file, go to the "Download the updates to the Pdm.dll from the product update Web site" section. Otherwise, to avoid this error, disable script debugging in Internet Explorer. If you are running Windows XP, use Guided Help to disable script debugging. If you are running any other operating system, go to the "Manually disable script debugging" section.

Manually disable script debugging

This resolution can be used for all operating systems. If you do not want to disable script debugging, go to the "Download the updates to the Pdm.dll from the product update Web site" section.

To manually disable script debugging in Internet Explorer, follow these steps:

1. Start Internet Explorer.
2. On the Tools menu, click Internet Options.
3. On the Advanced tab, under the Browsing section, click to select the Disable script debugging (Internet Explorer) check box and the Disable script debugging (Other) check box if it is present.
4. Click OK, and then restart your computer.

If these steps resolved the error message, you are finished.

If these steps did not resolve the error message, go to the "Download the updates to the Pdm.dll from the product update Web site" section.

Download the updates to the Pdm.dll from the product update Web site

This resolution can be used for all operating systems except Windows 98 and Windows Millennium Edition (Me). Use this resolution if you must have the script debugging capability. To repair and use script debugging, you have to update the Pdm.dll file. To update the Pdm.dll file, install the appropriate upgrades that are described in this section.

Note If you are running Windows 98 or Windows Millennium Edition (Me), the following upgrades do not install an updated version of the Pdm.dll file. The only resolution available to you is to upgrade your operating system.

If you are running Microsoft Office 2000, upgrade to Microsoft Office 2000 Service Release 1a (SR-1a). To download this upgrade, visit the following Microsoft Web site:

http://www.microsoft.com/downloads/details.aspx?FamilyID=AF6C8D03-7633-45B4-AB96-795EE656F2A2&displaylang=EN (http://www.microsoft.com/downloads/details.aspx?FamilyID=AF6C8D03-7633-45B4-AB96-795EE656F2A2&displaylang=EN)

If you are running Microsoft Visual Studio 6.0, upgrade to Microsoft Visual Studio 6.0 Service Pack 5 (SP5) or a later version. To download this upgrade, visit the following Microsoft Web site, click the Service Packs link, and then click the service pack version that you want to download:

http://msdn2.microsoft.com/en-us/vstudio/aa718353.aspx (http://msdn2.microsoft.com/en-us/vstudio/aa718353.aspx)

If you are running the Microsoft Script Debugger in Windows 2000, Windows NT 4.0, Windows Server 2003, or Windows XP, upgrade to a newer version.

Note Although the Script Debugger upgrade is available for these operating systems, it is no longer supported. You can still download and use this upgrade.

To download this upgrade or for more information, visit the following Microsoft Web site:

http://www.microsoft.com/downloads/details.aspx?FamilyId=2F465BE0-94FD-4569-B3C4-DFFDF19CCD99&displaylang=en (http://www.microsoft.com/downloads/details.aspx?FamilyId=2F465BE0-94FD-4569-B3C4-DFFDF19CCD99&displaylang=en)

If these updates resolve the error message, you are finished.

If you still receive the error message after you download and install these updates, go to the “Next Steps” section for information about how to contact Support.

If the steps in this article did not resolve the error message, you might want to ask someone you know for help, or, you can also use the Microsoft Customer Support Services Web site to find other solutions. Some services that the Microsoft Customer Support Services Web site provides include the following:

• Searchable Knowledge Base (http://support.microsoft.com/search/?adv=1) : Search technical support information and self-help tools for Microsoft products.
• Solution Centers (http://support.microsoft.com/select/?target=hub) : View product-specific frequently asked questions and support highlights.
• Microsoft Customer Support Newsgroups (http://www.microsoft.com/communities/newsgroups/default.mspx) : Contact counterparts, peers, and Microsoft Most Valuable Professionals (MVPs).
• Other Support Options (http://support.microsoft.com/default.aspx?pr=csshome) : Use the Web to ask a question, contact Microsoft Customer Support Services, or provide feedback.

If you continue to have questions after you use these Microsoft Web sites or if you cannot find a solution on the Microsoft Support Services Web site, click the following link to contact

Not able to Defragmnet
 
Microsft Kb 160043

When you run Disk Defragmenter (Defrag.exe), you may receive the following error message:
 Error Defragmenting Drive . Windows could not access part of the drive. Click Help and carry out the instructions for running ScanDisk. IMPORTANT: To fix this problem, you must run ScanDisk and choose the Thorough option.
ID No: DEFRAG005 

Note that the "ID No: DEFRAG005" portion of the error message may be replaced by "ID No: DEFRAG006."

This error occurs when Disk Defragmenter is unable to read from or write to one or more bad sectors on the hard disk. The DEFRAG005 error message is displayed when Disk Defragmenter is unable to write to a sector. The DEFRAG006 error message is displayed when Disk Defragmenter is unable to read from a sector.


Before you attempt to work around this problem, you should first make a backup copy of any important data on your hard disk. After doing so, run ScanDisk (Scandskw.exe) and perform a thorough test on the hard disk. To do so, follow these steps:

1. Click the Start button, point to Programs, point to Accessories, point to System Tools, and then click ScanDisk.
2. Click the hard disk referenced in the error message, and then click Thorough in the Type Of Test area.
3. Click Options, verify that System And Data Areas is selected, and then click OK.
4. Click Start to begin the test.

If ScanDisk does not find any bad sectors, or if running ScanDisk does not correct the problem, configure ScanDisk to detect disk timeouts and check each cluster five times while performing a surface scan. To do so, follow these steps:

1. Use any text editor (such as Notepad) to open the Scandisk.ini file in the Windows\Command folder.
2. Create an [Environment] section in the file, if the section does not already exist, and then add the following lines to the section:
   ScanTimeOut=On
   NumPasses=5
   Note that the "ScanTimeOut=" and "NumPasses=" lines may already exist, but with different values.
3. Save and then close the Scandisk.ini file.
4. Click the Start button, click Shut Down, click "Restart the computer in MS-DOS mode," and then click Yes.
5. Type the following line and then press ENTER to run ScanDisk
   scandisk :
   where is the drive letter of the hard disk you want to check. Note that you should run a surface scan when ScanDisk prompts you to do so, repair any errors that ScanDisk finds, and view and save the log file that ScanDisk creates.
6. When ScanDisk is finished, type exit and then press ENTER to return to Windows 95.
7. Run Disk Defragmenter again.

If you still receive the above error message, run Disk Defragmenter to consolidate free space only, then defragment files only, and then perform a full defragmentation (both files and free space). To do this, follow these steps:

1. Click Start, point to Programs, point to Accessories, point to System Tools, and then click Disk Defragmenter.
2. Click the hard disk referenced in the error message, and then click OK.
3. Click Advanced, click Consolidate Free Space Only, and then click OK.
4. Click No when you are prompted to quit Disk Defragmenter.
5. Click the hard disk referenced in the error message, and then click OK.
6. Click Advanced, click Defragment Files Only, and then click OK.
7. Click No when you are prompted to quit Disk Defragmenter.
8. Click the hard disk referenced in the error message, and then click OK.
9. Click Advanced, click "Full defragmentation (both files and free space)", and then click OK.
10. Click Yes when you are prompted to exit Disk Defragmenter.

If ScanDisk does not find any bad sectors, or if running ScanDisk does not correct the problem, contact the manufacturer of your computer or hard disk to inquire about additional workarounds that may correct the problem.

Many hard disks have sectors that are unusable. If the sectors have been marked as bad by ScanDisk or another disk tool, Disk Defragmenter displays the sector as a white box with a red line through it. This indicates that the cluster has been marked as bad and cannot be used to store data.

If the disk tool you use is unable to detect bad sectors on your hard disk, or if you do not run a disk tool on a regular basis, unusable sectors that are not marked as bad may exist on the disk. When this occurs, you may not realize that the bad sectors exist until Windows 95 attempts to store data in them. Therefore, it is possible for bad sectors to appear while you are using the drive normally. If bad sectors begin to appear on a regular basis, your hard disk may need to be repaired or replaced.

Note that you may be able to prevent the error message from being displayed by deleting some files on your hard disk, but doing so does not fix the problem that is causing the error message to appear. Disk Defragmenter does not read from unused sectors while defragmenting a drive. Therefore, if an unusable sector that does not contain any data exists on your hard disk, the problem described in this article may not occur. 

APPLIES TO

• Microsoft Windows 95
• Microsoft Plus! 95 Standard Edition
• Microsoft Windows 98 Standard Edition

Microsoft KB 314464

How to troubleshoot unknown devices that are listed in Device Manager in Windows XP

Device Manager displays a list of all devices that are installed on a Windows XP-based computer. When you view device information in Device Manager, you may see a device listed as Unknown Device next to a yellow question mark. It may be difficult to determine the cause of this unknown device, because there are few indications of what generates it. This article discusses the possible reasons that an unknown device may appear in Device Manager.


The main reason for Unknown Device to display in your Device Manager is because you have a device that is not working correctly. To fix this issue, obtain an updated driver for the device.

Use the following methods to enable Windows to recognize your device.

Method 1: Windows Update

Visit the following Microsoft Web site to see whether the Web site autodetects an updated driver for your device. Install all recommended drivers.

http://www.windowsupdate.com (http://www.windowsupdate.com)

Method 2: Download and install the latest driver from the Internet

When you download a driver from the Internet, download the Windows XP version of the driver when multiple Windows versions are listed. Use one of the following options:

• Visit the Web site of the computer manufacturer if the device came with the computer.
• Visit the Web site of the device manufacturer if the device was installed after you purchased your computer.
• Visit the Web site of the device manufacturer if the device was preinstalled on your computer and the computer manufacturer does not have an updated driver.

Look for a Drivers section or a Download section on the manufacturer’s Web site, and search for the device name. Download and install the Windows XP version of the driver.

Advanced user section

This section is intended for advanced computer users. If you are not comfortable with advanced troubleshooting, you might want to ask someone for help or contact support. For information about how to do this, visit the following Microsoft Web site:

http://support.microsoft.com/contactus (http://support.microsoft.com/contactus)

Causes of unknown devices in Device Manager

• The device does not have a device driver: When a device driver for a device is not available, Device Manager displays the device as Unknown Device and puts it in the Other devices branch. This is very common with universal serial bus (USB) and Institute of Electrical and Electronics Engineering (IEEE) 1394 composite devices. Also, a status of Error Code 1 or Error Code 10 may be displayed when you view the properties of the device in Device Manager.
  
  Note Most USB and IEEE 1394 devices function correctly without additional device drivers because they are configured by the drivers that are included with Windows for these bus types. However, an additional device driver is needed if the device does not fit the defined and supplied Windows class drivers. If the bus cannot identify the device, it interprets the device as a composite device and then reports it as such in Device Manager.
• You are using a Microsoft Windows 98 or Microsoft Windows 95 Device Driver: You cannot use virtual device driver (.vxd) files that are common to Windows 98 or to Windows 95 drivers in Windows XP. If you try to install them on your Windows XP-based computer, the device may be listed as unknown in Device Manager. This typically occurs when the device driver manufacturer does not correctly differentiate between the two drivers or assumes that Windows XP can use Windows 98 or Windows 95 .vxd files.
• Unrecognized Device ID: Every hardware device has a special identifier that is used by Plug and Play. This identifier can include several different types, such as vendor ID, device ID, subsystem ID, subsystem vendor ID, or revision ID. If a device ID is not present, or your Windows XP-based computer does not recognize the device ID, Device Manager may list the device as unknown.
  
  Note Software programs that require virtual hooks into hardware may create these devices. Additionally, devices that bridge between bus types, such as a device driver that enables a parallel port device to emulate a SCSI or an AT Attachment Packet Interface (ATAPI) bus, are also known to generate an unknown-device response in Device Manager.
• Faulty Hardware or Firmware: Faulty hardware or firmware may cause a device to be displayed as Unknown Device in Device Manager. Software-only device drivers do not expose a device ID, and there is no standard method for installing these devices. Some manufacturers install the device by using the InstallShield installation program or a similar method. Be aware that software installed by other methods may not be completely removed when the device is removed in Device Manager. Therefore, you may have to check the registry to verify that all entries are removed.

Troubleshooting for advanced users

Troubleshooting software issues

Use any of the following methods to determine whether an unknown device is being created by software:

• Start your computer in safe mode
  
  Although not 100-percent reliable, starting your computer in safe mode can be one of the easiest ways to determine whether the unknown device is created by software.
  
  To start your computer in safe mode, press F8 after you restart your computer. On the Windows Advanced Option Menu that appears, use the ARROW keys to select Safe Mode, and then press ENTER. If the unknown device is no longer listed in Device Manager, it is likely that the unknown device is not hardware.
• Check the Startup folder
  
  If you suspect that a particular program is the cause of the unknown device, check the Startup folder on your computer to see which programs are configured to start when your computer starts. The Startup folder is in the following location on your hard disk, where C is the drive on which Windows is installed, and user profile is your user profile:
  
  C:\Documents and Settings\user profile\Start Menu\Programs
  
  
  
• Use the System Information tool
  
  The System Information tool can be useful when you have to determine the cause of an unknown device.
  
  To use the System Information tool to view a list of programs that start when your computer starts, follow these steps:
  
  1. Click Start, click Run, type msinfo32, and then click OK.
  2. Expand Software Environment, and then double-click Startup Programs.
     
     A list of the programs that are configured to start when your computer starts is displayed.
     
     Check the event log for errors that refer to any of these programs. If you find an event that is related to a program in this list, remove the program. Be aware that when a program creates an unknown device, it is not necessarily an indication that the program does not work, unless the program depends on that device to start.
  
  To use the System Information tool to view a list of problem devices, follow these steps:
  
  1. Click Start, click Run, type msinfo32, and then click OK.
  2. Expand Components, and then double-click Problem Devices.
     
     A list of the devices that are installed on your computer that may have a problem is displayed in the details pane, as follows:
     
     • The Device column lists the common name for the device, or the name of the device driver associated with it.
     • The PNP Device ID column lists device IDs, such as Peripheral Component Interconnect (PCI) ID, ISA ID, an ID for some other bus type, or an unknown type.
     • The Error Code column lists the error code associated with this specific problem. Frequently, the Device Manager error code helps determine what created the unknown device. For example, if your computer generates a "Bad or missing device driver" error message, three types of entries may be listed under Problem Devices, depending on the device type:
       
       • PCI PnP Device ID:
         
         Device Name | PCI\VEN_00000&DEV_0000&SUBSYS_00000000&REV_00\0&0000 | Error code
       • ISA PnP ID:
         
         Device Name | ?\PNP0000\0
       • Bad or Incompatible Device Driver:
         
         Device Name | ROOT\UNKNOWN\0000
       
       
     
     
  
  
• View the Setupapi.log file
  
  If the device has a meaningful name, use the information in the Setupapi.log file to determine the cause of an unknown device. By default, the Setupapi.log file is located in the %SystemRoot% folder.
  
  Sometimes the listed device name can be misleading. For example, a device may be listed as a serial device in Device Manager, when in reality it is not related to a serial port. This typically occurs when a partial Plug and Play ID is available, and Device Manager interprets it as a serial device. This interpretation may occur because of a compatible ID specified by the device. Again, this can be corrected by locating the startup program that may not be behaving correctly.
  
  Be aware that merely removing the unknown device in Device Manager does not work if a software program is the cause of the unknown device. You must remove the program and then restart your computer. If the unknown device is still listed in Device Manager after you restart your computer in safe mode, contact Microsoft Customer Support Services for help in removing the device.

Troubleshooting hardware issues

To determine the cause of an unknown device, use one of the following methods:

• Remove hardware devices from your computer
  
  Remove hardware devices one at a time until the unknown device is no longer listed in Device Manager. Be aware that this method may be time-consuming and is not always reliable.
• Determine whether the device driver is digitally signed
  
  When you install a device driver, and Windows detects that it is not digitally signed, you may receive a warning message and the option to cancel or continue the installation This message is displayed only if your computer is configured to display a warning message whenever an installation program tries to install a device driver without a digital signature.
  
  Note A device driver that is digitally signed can still be listed as an unknown device in Device Manager.
  
  For more information about driver signing for Windows, visit the following Microsoft Web site:
  
  http://www.microsoft.com/whdc/devtools/ddk/default.mspx (http://www.microsoft.com/whdc/devtools/ddk/default.mspx/)
  
  
  

You can block the installation of device drivers that do not contain a digital signature. Use this approach when you want to prevent any deliberate attempts to destabilize the computer. To do this, follow these steps:

1. Click Start, click Run, type control sysdm.cpl in the Open box, and then click OK.
2. Click the Hardware tab.
3. Under Drivers, click Driver Signing, and then click Block - Never install unsigned driver software.
4. Click OK two times.

To view a list of device drivers installed on your computer that are not digitally signed, use either of the following methods:

• View the Setupapi.log file
  
  Look for entries that resemble the following:
  
  The file (C:\Windows\inf\ntapm.inf) is not digitally signed, ignoring driver date.
  
  Installing section epatapi_inst from C:\documents and settings\user name\my documents\parallel port test drivers\epatapnt.inf
  An unsigned or incorrectly signed driver (C:\documents and settings\user name\my documents\parallel port test drivers\epatapnt.inf) was installed for Parallel ATAPI Adapter.. Error 0xe000022f: The third-party INF does not contain digital signature information.
  Copying file C:\documents and settings\user name\my documents\parallel port test drivers\epatapnt.mpd to C:\Windows\System32\DRIVERS\epatapnt.mpd.
  An unsigned or incorrectly signed driver (C:\documents and settings\user name\my documents\parallel port test drivers\epatapnt.mpd) was installed for Parallel ATAPI Adapter.. Error 0xe000022f: The third-party INF does not contain digital signature information.
  
  
  
• Use the File Signature Verification tool
  
  The File Signature Verification tool lists all the unsigned drivers that are installed on your computer. It creates a Sigverif.txt log that is located in the %SystemRoot% folder. Use any text editor (for example, Notepad) to view the file. To use the File Signature Verification tool to display a list of drivers that are not digitally signed, follow these steps:
  
  1. Click Start, click Run, type sigverif, and then click OK.
  2. Click Advanced, click the Search tab, and then click Look for other files that are not digitally signed.
  3. Click to select the Include subfolders check box, and then click Browse.
  4. Locate and select the %SystemRoot%\System32\Drivers folder, click OK two times, and then click Start.
  Review the list, and then contact the driver manufacturer for information about how to obtain an updated driver that is digitally signed.
  

USB devices that are based on earlier versions of the USB specification may create ghost devices that appear when the device is connected, and then disappear when the device is disconnected. Also, the device may work fine, but may create a disassociated unknown device. This is typically caused by firmware that is either outdated or configured incorrectly. In this case, contact the device manufacturer for updated firmware.

A ghosted device can appear if you manually install a driver for a Plug and Play device that the computer has already detected and installed. You can resolve this issue by deleting the ghosted device.

Similar problems and resolutions for advanced users

For more information about how to use Device Manager to manage devices in Windows XP, click the following article numbers to view the articles in the Microsoft Knowledge Base:

283658  (http://support.microsoft.com/kb/283658/ ) How to manage devices in Windows XP

307970  (http://support.microsoft.com/kb/307970/ ) How to configure devices by using Device Manager in Windows XP

304514  (http://support.microsoft.com/kb/304514/ ) How to configure Device Manager to display detailed information

310126  (http://support.microsoft.com/kb/310126/ ) Troubleshooting device conflicts with Device Manager

283361  (http://support.microsoft.com/kb/283361/ ) Device Manager still lists a device after you try to remove it

310123  (http://support.microsoft.com/kb/310123/ ) Explanation of error codes generated by Device Manager in Microsoft Windows XP Professional

For more information about the System Information tool, click the following article numbers to view the articles in the Microsoft Knowledge Base:

308549  (http://support.microsoft.com/kb/308549/ ) Description of Windows XP System Information (Msinfo32.exe) tool

300887  (http://support.microsoft.com/kb/300887/ ) How to use System Information (MSINFO32) switches

For more information about how to troubleshoot with the Msconfig tool, click the following article numbers to view the articles in the Microsoft Knowledge Base:

310560  (http://support.microsoft.com/kb/310560/ ) How to troubleshoot configuration errors by using the System Configuration utility in Windows XP

If the articles listed here do not help you resolve the problem or if you experience symptoms that differ from those that are described in this article, search the Microsoft Knowledge Base for more information. To search the Microsoft Knowledge Base, visit the following Microsoft Web site:

http://support.microsoft.com (http://support.microsoft.com/)

Then, type the text of the error message that you receive, or type a description of the problem in the Search Support (KB) field.

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

APPLIES TO

• Microsoft Windows XP Home Edition
• Microsoft Windows XP Professional
• Microsoft Windows XP Professional x64 Edition

Microsoft KB 315539
  

Device Manager does not display devices that are not connected to the Windows XP-based computer

Device Manager displays only non-Plug and Play devices, drivers, and printers when you click Show hidden devices on the View menu. Devices that you install that are not connected to the computer (such as a Universal Serial Bus [USB] device or "ghosted" devices) are not displayed in Device Manager, even when you click Show hidden devices.

To work around this behavior and display devices when you click Show hidden devices:

1. Click Start, point to All Programs, point to Accessories, and then click Command Prompt.
2. At a command prompt, type the following command , and then press ENTER:
   
   set devmgr_show_nonpresent_devices=1
   
   
   
3. Type the following command a command prompt, and then press ENTER:
   
   start devmgmt.msc
   
   
   
4. Troubleshoot the devices and drivers in Device Manager.
   
   NOTE: Click Show hidden devices on the View menu in Device Managers before you can see devices that are not connected to the computer.
5. When you finish troubleshooting, close Device Manager.
6. Type exit at the command prompt.
   
   Note that when you close the command prompt window, Window clears the devmgr_show_nonpresent_devices=1 variable that you set in step 2 and prevents ghosted devices from being displayed when you click Show hidden devices.

If you are a developer or power user and you want to be able to view devices that are not connected to your computer, set this environment variable globally:

1. Right-click My Computer.
2. Click Properties.
3. Click the Advanced tab.
4. Click the Environment Variables tab.
5. Set the variables in the System Variables box.

NOTE: Use this method only for troubleshooting or development purposes, or to prevent users from accidentally uninstalling a required device that is not connected to the computer (such as a USB device or docking station that is not connected to a laptop computer).
 In Device Manager, there are two types of hidden devices in addition to the devices that are displayed:

• Typical, hidden devices that are not displayed (non-Plug and Play drivers, printers, and so on)
  -and-
• Phantom devices that are not connected to the computer

APPLIES TO

• Microsoft Windows XP Home Edition
• Microsoft Windows XP Professional

Increasing System Performance

Remove Spyware

If the computer is performing very slowly after connecting to the Internet, the computer may have adware or spyware programs installed.

Spyware and adware software programs use the Internet to download and upload information in the background. Some of this information may be sensitive or unwanted advertising.

Spyware and adware can be very difficult to remove.

Close all open programs not being used

Only use programs that are necessary. Minimizing a programs window may not stop that program from using the computer's processor and memory. Being connected to the Internet, listening to music, and running virus scans are all ways to use a lot of system resources. Try running virus scans and other system tools while no one is using the computer or when away from the desk. Work offline when convenient. Closing programs that are not necessary helps Windows perform more efficiently.

Prevent background programs from loading

As software programs load, the small icons on the system tray increase (usually these icons are in the lower-right corner, next to the time). Each of these small pictures represents a program running in the background, and each one removes valuable system resources. Move the mouse pointer over each small picture to find what software it is. Common programs that load and run in the background are virus scanners, display settings, and multimedia programs. Increase system resources by stopping these tasks from loading, or by changing their settings. This can be achieved in a number of ways since these programs often start from various places. If the methods below do not apply to a specific icon, consult the applications documentation or Web site.

Figure 1: System tray icons

Use System Configuration to prevent programs from launching (98, ME, and XP)

Perform the following steps to selectively prevent items from starting when Windows launches.

CAUTION:

Only disable items that are known and unwanted. Disabling system critical items may cause problems.

1. Select Start , and then Run .
2. In the Open field type the following: msconfig .

The System Configuration Utility window appears.

3. Select the General tab and make sure Selective Startup is selected.
4. Select the Startup tab as shown in Figure 2 and remove the checks from any tasks that do not contribute to the system and are unwanted. If unsure about a task, write the name down and research it on the Internet later. Do not remove a check mark if you do not know what the task is. For a list of files that are recommended not to remove, review the support document Figure 2: The Startup tab of the System Configuration Utility

5. Click OK to accept the changes. Restart the computer.

After Windows starts, a System Configuration window appears. Place a check mark in the do not show this message again checkbox and click OK (XP only).

6. If Windows or other software stops working after a check mark is removed from a task you were unsure about, restart the computer and reverse these procedures to replace the checkmark. Press F8 after the very first blue startup screen (after the computer has been turned on) to get into Safe mode.

By completing these steps, Windows will run using Selective Startup. This means that Windows prevents the selected programs from starting. If Selective Startup is disabled in the future, all of the selected programs will start again.

Empty the Recycle Bin

1. From the Windows desktop, double-click Recycle Bin .
2. Restore any mistakenly deleted items by highlighting each file, then selecting File and Restore .
3. Select File and Empty Recycle Bin . Windows will remove the contents of the Recycle Bin from the hard disk (C: is most common). Select Yes to confirm.
4. Close the Recycle Bin .

Deleting temporary files and directories

This step increases hard disk space and reduces the time Windows takes to access the hard drive. It also resolves problems associated with spooling print jobs. Windows uses a TEMP directory to temporarily store files intended only for temporary use. Over time, these files can build up and cause problems. To delete these files, use the following set of steps depending upon the Windows version:

Windows XP

1. Close all open software.
2. Select Start , Programs , Accessories , System Tools , and then Disk Cleanup .
3. Place a check next to the types of files you want the Disk Cleanup utility to delete. Temporary files are safe to delete.
4. Select OK (see Figure 3).

Figure 3: Disk cleanup

ScanDisk and Defragment the hard drive

The program Scandisk checks a hard drive for errors. The program Disk Defragmenter takes all of the scattered bits of program data and groups them together in more efficient areas of the drive.

Run ScanDisk before running the Defragmenter as follows:

ScanDisk in Windows XP

1. Click Start , then open My Computer .
2. Right-click on the hard drive's icon (usually C:\).
3. Click Properties , and then click the Tools tab.
4. Click Check Now .
5. Place check marks in all check boxes.
6. Click OK , and then click Yes to schedule a full disk scan when the computer is restarted.
7. Restart the computer. The disk scan can take a very long time to complete.

Defragment, all versions of Windows

1. Close all programs that are running. This includes background programs such as scanners.
2. Click Start , Programs or All Programs , Accessories , then System Tools .
3. Click Disk Defragmenter and follow the onscreen instructions.

If Disk Defragmenter repeatedly starts, then a hidden background program is still accessing the hard drive. Restart the computer in Safe mode and try again.

Preventing memory leaks

A memory leak is unused memory that Windows thinks is still valid. Over time, unused memory can build up, causing Windows to slow down and use the hard drive more. Memory leaks are probably occurring if the PC runs well when first turned on, but performs noticeably slower after several programs are opened and closed.

Memory leaks can occur if software is closed before it has fully opened. Always allow programs to load completely. As a rule, wait 10 to 20 seconds after a program starts before closing it again, even if the program was opened unintentionally.

To immediately fix memory leaks, restart the computer. For a permanent fix, isolate the program causing the leaks by using the following steps:

1. Start with a fresh session of Windows by shutting down, then turning on the computer.
2. In Windows XP press Ctrl+ Alt + Delete.

In Windows 98 and Me, right-click the My Computer icon on the desktop and select Properties .

3. In Windows XP this is the amount of available physical memory.

Figure 4: Viewing available physical memory in Windows XP

Adjusting system restore settings in Windows XP

System Restore is a feature of Windows that can revert system software and settings back to a particular date. System Restore does this by saving the changes made to system files in a restore point. These restore points use a lot of hard space. System Restore can fill twelve percent of the hard drive with restore points if left unadjusted, regardless of the entire size of the hard drive. To save hard drive space, use the following steps to reduce the amount of restore points that system restore creates:

1. Click Start , and right-click My Computer .
2. Select Properties .
3. Click the System Restore tab.
4. Select the (C:) drive and click the Settings button.
5. Adjust the Disk space to use slider to a lower setting. A lower setting will save disk space but will reduce how many restore points you can select from when restoring in the future. On a 120 gigabyte hard drive, a setting of one percent saves over 11 gigabytes of future disk space and still provides enough room for several restore points.
6. Click OK to save the settings.

Figure 6: Disk space to use

Updating software

Software conflicts can cause the system to slow. Microsoft, and other software manufacturers release updates to address these problems. Make sure that you visit  software download site and use Windows Update tool regularly. For more information refer to the support document

In Windows 98, and Me, select the Performance tab. Note the percentage next to System Resources .

4. Open a program suspected of causing the computer to run more slowly.
5. View the System Resources percentage or the amount of physical memory again and write it down.
6. Close and re-open a suspected program repeatedly, comparing this number to the one recorded. Each time, wait about 10 seconds before opening again.
7. If the system resources percentage or available physical memory continues to decrease, then a memory leak is occurring. Contact the program's vendor for available patches or fixes.
8. If the System Resource percentage or available physical memory comes back near to the same numbers each time, then the suspected program is probably not creating a memory leak.

Freeing up space on the hard drive

Windows uses this space for different types of operations such as caching and virtual memory. The computer may not run reliably if the free disk space drops below five percent of the total disk space.

To see how much space remains on the hard drive, double-click My Computer , located on the desktop. Right-click the hard drive (C: is most common), and select Properties .

Use the following steps to remove unwanted programs and increase hard drive space:

1. Click Start , Settings , and Control Panel .
2. Open Add/Remove Programs .
3. Click the Install/Uninstall tab. Select programs that are no longer used and will not be used.
4. Highlight the program name, and then click the Add/Remove or Change/Remove button and OK .

Figure 5: Removing programs

5. When done, a prompt may appear to restart Windows. Wait until completely removing the unwanted programs; then restart Windows.

Computer Management Overview

Computer Management is a collection of Windows administrative tools that you can use to manage a local or remote computer. The tools are organized into a single console, which makes it easy to view administrative properties and to gain access to the tools that are necessary to perform your computer-management tasks.

The Computer Management Console

The Computer Management console consists of a window divided into two panes. The left pane contains the console tree; the right pane contains details. When you click an item in the console tree, information about that item is displayed in the details pane. The information that is displayed is specific to the item that you select.

The administrative tools in Computer Management are grouped into the following three categories in the console tree:

• System Tools
• Storage
• Services and Applications

Each category includes several tools or services.

System Tools

• Event Viewer
  
  Use the Event Viewer tool to manage and view events that are recorded in the Application, Security, and System logs. You can monitor the logs to track security events and to identify possible software, hardware, and system problems.
• Shared Folders
  
  Use the Shared Folders tool to view connections and resource in use on the computer. You can create, view, and manage shares, view open files and sessions, and close files and disconnect sessions.
• Local Users and Groups
  
  Use the Local Users and Groups tool to create and manage your local user accounts and groups. Local Users and Groups is available only in Windows XP Professional.
• Performance Logs and Alerts
  
  Use the Performance Logs and Alerts tool to configure performance logs and alerts to monitor and collect data about your computer's performance.
• Device Manager
  
  Use Device Manager to view the hardware devices installed in your computer, update device drivers, modify hardware settings, and troubleshoot device conflicts.

Storage

• Removable Storage
  
  Use the Removable Storage tool to track your removable storage media and manage the libraries, or data-storage systems, that contain them.
• Disk Defragmenter
  
  Use the Disk Defragmenter tool to analyze and defragment volumes on your hard disks.
• Disk Management
  
  Use the Disk Management tool to perform disk-related tasks such as converting disks or creating and formatting volumes. Disk Management helps you manage your hard disks, and the partitions or volumes that they contain.

Services and Applications

• Services
  
  Use Services to manage services on local and remote computers. You can start, stop, pause, resume, or disable a service.
• WMI Control
  
  Use WMI Control to configure and manage the Windows Management Instrumentation (WMI) service.
• Indexing Service
  
  Use Indexing Service to manage the Indexing service, and to create and configure additional catalogs to store index information.

NOTE: The actual set of tools and services that is listed in Computer Management depends on the services that are installed on the host computer.

How to Use Computer Management on the Local Computer

NOTE: You must be logged on as Administrator or as a member of the Administrators group view and modify most properties and perform most computer-management tasks.

To start and use Computer Management on the local computer:

1. Click Start, and then click Control Panel. Click Performance and Maintenance, click Administrative Tools, and then double-click Computer Management.
   
   The Computer Management window for the local computer is displayed. "Computer Management (Local)" is displayed at the root of the console tree.
2. In the console tree, expand System Tools, Storage, or Services and Applications to view the tools and services in each of these containers.
3. Click the item that you want (for example, Event Viewer) to use the tool, and then view the information that is associated with it.

How to Use Computer Management on a Remote Computer

NOTE: You must be logged on as Administrator or as a member of the Administrators group to view and modify most properties and perform most computer-management tasks.

To connect to and use Computer Management on another computer:

1. Click Start, and then click Control Panel. Click Performance and Maintenance, click Administrative Tools, and then double-click Computer Management.
2. Right-click Computer Management (Local), and then click Connect to another computer.
3. Click Another Computer, and then type the name of the computer that you want to manage remotely, or click Browse to locate the computer. Click OK and then click OK to return to the Computer Management window. The Computer Management window of the remote computer is displayed. The name of the remote computer is displayed at the root of the console tree.
4. In the console tree, expand System Tools, Storage, or Services and Applications to view the tools and services in each of these containers.
5. Click the item that you want (for example, Event Viewer) to use the tool, and then view the information that is associated with it.

How to Use Help in Computer Management

To use Computer Management Help or to use the Help files for any of the individual administrative tools that are contained in Computer Management:

1. Start Computer Management.
2. Use either of the following steps:
   
   
   
   
   • In the console tree, right-click the item that you want (for example, Computer Management or Device Manager), and then click Help.
   • Click the item in the console tree (for example, Device Manager or Computer Management), and then click Help on the Action menu.
   
   
   
   
   

Microsoft KB 307545

This article describes how to recover a Windows XP system that does not start because of corruption in the registry. This procedure does not guarantee full recovery of the system to a previous state; however, you should be able to recover data when you use this procedure.

Warning Do not use the procedure that is described in this article if your computer has an OEM-installed operating system. The system hive on OEM installations creates passwords and user accounts that did not exist previously. If you use the procedure that is described in this article, you may not be able to log back into the recovery console to restore the original registry hives.

You can repair a corrupted registry in Windows XP. Corrupted registry files can cause a variety of different error messages. See the Microsoft Knowledge Base for articles about error messages that are related to registry issues.

This article assumes that typical recovery methods have failed and access to the system is not available except by using Recovery Console. If an Automatic System Recovery (ASR) backup exists, it is the preferred method for recovery. Microsoft recommends that you use the ASR backup before you try the procedure described in this article.

Note Make sure to replace all five of the registry hives. If you only replace a single hive or two, this can cause potential issues because software and hardware may have settings in multiple locations in the registry.

When you try to start or restart your Windows XP-based computer, you may receive one of the following error messages:

Windows XP could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM

Windows XP could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SOFTWARE

Stop: c0000218 {Registry File Failure} The registry cannot load the hive (file): \SystemRoot\System32\Config\SOFTWARE or its log or alternate

System error: Lsass.exe
When trying to update a password the return status indicates that the value provided as the current password is not correct.

 

Manual steps to recover a corrupted registry that prevents Windows XP from starting

The procedure that this article describes uses Recovery Console and System Restore. This article also lists all the required steps in specific order to make sure that the process is fully completed. When you finish this procedure, the system returns to a state very close to the state before the problem occurred. If you have ever run NTBackup and completed a system state backup, you do not have to follow the procedures in parts two and three. You can go to part four.

Part one

In part one, you start the Recovery Console, create a temporary folder, back up the existing registry files to a new location, delete the registry files at their existing location, and then copy the registry files from the repair folder to the System32\Config folder. When you have finished this procedure, a registry is created that you can use to start Windows XP. This registry was created and saved during the initial setup of Windows XP. Therefore any changes and settings that occurred after the Setup program was finished are lost.

To complete part one, follow these steps:

1. Insert the Windows XP startup disk into the floppy disk drive, or insert the Windows XP CD-ROM into the CD-ROM drive, and then restart the computer.
   Click to select any options that are required to start the computer from the CD-ROM drive if you are prompted to do so.
2. When the "Welcome to Setup" screen appears, press R to start the Recovery Console.
3. If you have a dual-boot or multiple-boot computer, select the installation that you want to access from the Recovery Console.
4. When you are prompted to do so, type the Administrator password. If the administrator password is blank, just press ENTER.
5. At the Recovery Console command prompt, type the following lines, pressing ENTER after you type each line:
   
   
   
   
   md tmp
   copy c:\windows\system32\config\system c:\windows\tmp\system.bak
   copy c:\windows\system32\config\software c:\windows\tmp\software.bak
   copy c:\windows\system32\config\sam c:\windows\tmp\sam.bak
   copy c:\windows\system32\config\security c:\windows\tmp\security.bak
   copy c:\windows\system32\config\default c:\windows\tmp\default.bak
   
   delete c:\windows\system32\config\system
   delete c:\windows\system32\config\software
   delete c:\windows\system32\config\sam
   delete c:\windows\system32\config\security
   delete c:\windows\system32\config\default
   
   copy c:\windows\repair\system c:\windows\system32\config\system
   copy c:\windows\repair\software c:\windows\system32\config\software
   copy c:\windows\repair\sam c:\windows\system32\config\sam
   copy c:\windows\repair\security c:\windows\system32\config\security
   copy c:\windows\repair\default c:\windows\system32\config\default
   
   
   
   
   
   
   
6. Type exit to quit Recovery Console. Your computer will restart.

Note This procedure assumes that Windows XP is installed to the C:\Windows folder. Make sure to change C:\Windows to the appropriate windows_folder if it is a different location.

If you have access to another computer, to save time, you can copy the text in step five, and then create a text file called "Regcopy1.txt" (for example). To use this file, run the following command when you start in Recovery Console:

batch regcopy1.txt

With the batch command in Recovery Console, you can process all the commands in a text file sequentially. When you use the batch command, you do not have to manually type as many commands.

Part two

To complete the procedure described in this section, you must be logged on as an administrator, or an administrative user (a user who has an account in the Administrators group). If you are using Windows XP Home Edition, you can log on as an administrative user. If you log on as an administrator, you must first start Windows XP Home Edition in Safe mode. To start the Windows XP Home Edition computer in Safe mode, follow these steps.

Note Print these instructions before you continue. You cannot view these instructions after you restart the computer in Safe Mode. If you use the NTFS file system, also print the instructions from Knowledge Base article KB309531. Step 7 contains a reference to the article.

1. Click Start, click Shut Down (or click Turn Off Computer), click Restart, and then click OK (or click Restart).
2. Press the F8 key.
   
   On a computer that is configured to start to multiple operating systems, you can press F8 when you see the Startup menu.
3. Use the arrow keys to select the appropriate Safe mode option, and then press ENTER.
4. If you have a dual-boot or multiple-boot system, use the arrow keys to select the installation that you want to access, and then press ENTER.

In part two, you copy the registry files from their backed up location by using System Restore. This folder is not available in Recovery Console and is generally not visible during typical usage. Before you start this procedure, you must change several settings to make the folder visible:

1. Start Windows Explorer.
2. On the Tools menu, click Folder options.
3. Click the View tab.
4. Under Hidden files and folders, click to select Show hidden files and folders, and then click to clear the Hide protected operating system files (Recommended) check box.
5. Click Yes when the dialog box that confirms that you want to display these files appears.
6. Double-click the drive where you installed Windows XP to display a list of the folders. If is important to click the correct drive.
7. Open the System Volume Information folder. This folder is unavailable and appears dimmed because it is set as a super-hidden folder.
   
   Note This folder contains one or more _restore {GUID} folders such as "_restore{87BD3667-3246-476B-923F-F86E30B3E7F8}".
   
   Note You may receive the following error message:
   
   
   
   
   C:\System Volume Information is not accessible. Access is denied.
   
   If you receive this message, see the following Microsoft Knowledge Base article to gain access to this folder and continue with the procedure:
   
   
   
   
   309531  (http://support.microsoft.com/kb/309531/ ) How to gain access to the System Volume Information folder
   
   
   
   
   
   
8. Open a folder that was not created at the current time. You may have to click Details on the View menu to see when these folders were created. There may be one or more folders starting with "RPx under this folder. These are restore points.
9. Open one of these folders to locate a Snapshot subfolder. The following path is an example of a folder path to the Snapshot folder:
   
   
   
   
   C:\System Volume Information\_restore{D86480E3-73EF-47BC-A0EB-A81BE6EE3ED8}\RP1\Snapshot
   
   
   
   
   
   
10. From the Snapshot folder, copy the following files to the C:\Windows\Tmp folder:
    
    
    
    
    • _REGISTRY_USER_.DEFAULT
    • _REGISTRY_MACHINE_SECURITY
    • _REGISTRY_MACHINE_SOFTWARE
    • _REGISTRY_MACHINE_SYSTEM
    • _REGISTRY_MACHINE_SAM
    
    
    
    
    
11. Rename the files in the C:\Windows\Tmp folder as follows:
    
    
    
    
    • Rename _REGISTRY_USER_.DEFAULT to DEFAULT
    • Rename _REGISTRY_MACHINE_SECURITY to SECURITY
    • Rename _REGISTRY_MACHINE_SOFTWARE to SOFTWARE
    • Rename _REGISTRY_MACHINE_SYSTEM to SYSTEM
    • Rename _REGISTRY_MACHINE_SAM to SAM
    
    
    
    
    

These files are the backed up registry files from System Restore. Because you used the registry file that the Setup program created, this registry does not know that these restore points exist and are available. A new folder is created with a new GUID under System Volume Information and a restore point is created that includes a copy of the registry files that were copied during part one. Therefore, it is important not to use the most current folder, especially if the time stamp on the folder is the same as the current time.

The current system configuration is not aware of the previous restore points. You must have a previous copy of the registry from a previous restore point to make the previous restore points available again.

The registry files that were copied to the Tmp folder in the C:\Windows folder are moved to make sure that the files are available under Recovery Console. You must use these files to replace the registry files currently in the C:\Windows\System32\Config folder. By default, Recovery Console has limited folder access and cannot copy files from the System Volume folder.

Note The procedure described in this section assumes that you are running your computer with the FAT32 file system. For more information about how to access the System Volume Information Folder with the NTFS file system, click the following article number to view the article in the Microsoft Knowledge Base:

309531  (http://support.microsoft.com/kb/309531/ ) How to gain access to the System Volume Information folder

Part Three

In part three, you delete the existing registry files, and then copy the System Restore Registry files to the C:\Windows\System32\Config folder:

1. Start Recovery Console.
2. At the command prompt, type the following lines, pressing ENTER after you type each line:
   
   
   
   
   del c:\windows\system32\config\sam
   
   del c:\windows\system32\config\security
   
   del c:\windows\system32\config\software
   
   del c:\windows\system32\config\default
   
   del c:\windows\system32\config\system
   
   copy c:\windows\tmp\software c:\windows\system32\config\software
   
   copy c:\windows\tmp\system c:\windows\system32\config\system
   
   copy c:\windows\tmp\sam c:\windows\system32\config\sam
   
   copy c:\windows\tmp\security c:\windows\system32\config\security
   
   copy c:\windows\tmp\default c:\windows\system32\config\default
   
   Note Some of these command lines may be wrapped for readability.
   
   
   
   
3. Type exit to quit Recovery Console. Your computer restarts.

Note This procedure assumes that Windows XP is installed to the C:\Windows folder. Make sure to change C:\Windows to the appropriate windows_folder if it is a different location.

If you have access to another computer, to save time, you can copy the text in step two, and then create a text file called "Regcopy2.txt" (for example). To use this file, run the following command when you start in Recovery Console:

batch regcopy2.txt

Part Four

1. Click Start, and then click All Programs.
2. Click Accessories, and then click System Tools.
3. Click System Restore, and then click Restore to a previous RestorePoint.