This task content
•summary
• How to use the most recently configured Startup Computer • How to start your computer in secure mode
• Use the Event Viewer to determine the reason for the startup problem • Use system information to determine the reason for the startup problem • View security mode Start log files • Use the Device Manager to determine the cause of the startup problem • How to use the system configuration utility
• Creating a clean environment for troubleshooting • Find a problem with the system start option • Find a problem with the "Selected Start" option • Use the "Start" tab to find a problem • Solve system service issues • Solve the System.ini file Question • Resolve the Win.ini file • Resolve the Boot.ini file problem • Reset the system configuration utility to normal start • How to use Microsoft Windows Fault Recovery Console
• Verify that the hard disk or file system is intact • How to use automatic system failure recovery
• Creating Automatic System Fault Recovery Sets by using backup • How to fix Windows installation • How to use Microsoft Product Support WEB Site Find Solutions
summary
This article describes the general processes that can be used when resolving the startup problem in Windows Server 2003.
Successful Windows boot includes the following four phases:
• Initial phase • Start loader phase • Nuclear phase • Login phase If there is a problem with the above phase, Windows may not start correctly, and you may encounter the following questions:
• The computer stops responding (hang). • You receive an error message. If you click on "Microsoft Windows Server 2003" on the boot loader menu, or when you see the "Microsoft Windows Server 2003" message, click "Microsoft Windows Server 2003", the operating system needs The file may be missing or damaged. Windows provides a variety of options available to resolve this issue, including "Security Mode", "Fault Recovery Console", and Automatic System Fault Repair.
Back to top
How to use the most recently configured Startup Computer If you change your computer (for example, after installing a new driver), try to start your computer using the "Last Custom Configuration" feature.
When using the "last correct configuration" feature, you will start your computer using the last possible settings. This feature recovers valid registry information and driver settings at the last successful start of the computer. This feature should be used if Windows cannot be started after changing your computer (for example, after the installation or upgrade device driver).
To start your computer using the "Last Configuration" feature, perform the following steps:
1. Click Start, and then click Shut. 2. Click Restart, and then click OK. 3. When you see "Please select the operating system" message to start, press the F8 key. 4. Use the arrow keys to select "The most recent configured configuration" and press Enter. Note: Num Lock must be turned off, and the arrow keys on the numeric keypad can work. 5. If you run other operating systems on your computer, click Microsoft Windows Server 2003 in the list and press Enter.
note:
• By selecting "The most recent configured configuration", you can recover from the issue (such as the newly added driver may not fit your hardware). This feature cannot solve problems caused by drivers or file corruption or missing. • When you select "The most correct configuration", only the information in the registry key HKLM / System / CurrentControlSet is restored. Will keep any changes you made in other registry keys. If you can start your computer using the "Last Correct Configuration", your last changes to your computer (for example, the installation driver) may be the cause of errors. Microsoft recommends deleting or updating the driver or program, then testing if Windows can start correctly.
Back to top
How to start your computer in secure mode When you start your computer in a secure mode, Windows only loads the drivers and computer services you need. You can use security mode to determine and solve problems caused by automatic start-up, faulty drivers, programs, or services. If your computer can start starting in security mode, it cannot be started in normal mode, the computer may have conflicts on hardware settings or resource allocation. It is possible that the system is not compatible with certain procedures, services, or drivers, or the registry is corrupt. In security mode, you can disable or delete programs, services, or device drivers that may hinder your computer startup.
To resolve the startup problem with security mode, perform the following steps:
1. Click Start, and then click Shut. 2. Click Restart, and then click OK. 3. When "Please select the operating system" message to start, press the F8 key. 4. On the Windows Advanced Options menu, use the arrow keys to select Safe Mode, then press Enter. Note: Num Lock must be turned off, and the arrow keys on the numeric keypad can work. 5. If you run other operating systems on your computer, click Microsoft Windows Server 2003 on the list, then press Enter. 6. Do one of the following:
• If your computer does not start with Security Mode, try to activate your computer using the "Fault Recovery Console". If you still can't start your computer, look for possible hardware issues, such as defective devices, installation issues, cable problems, or connectors. Delete any newly added hardware, then restart your computer to see if the problem has been resolved. • If the computer can start under Safe Mode, go to the next section to continue resolve the startup problem.
Back to top
Use the Event Viewer to determine the reason for the startup problem View the event log in the Event Viewer to get other information that helps determine and diagnose the cause of the problem. To view the events recorded in the event log, perform the following steps:
1. Do one of the following:
• Click Start, point to Administrative Tools, and then click the Event Viewer. • Start the "Event Viewer" management unit in Microsoft Management Console (MMC). 2. In the console tree, expand the event viewer, and then click the log you want to view. For example, click System Logs or Application Log. 3. In the Details pane, double-click the event you want to view. To copy the event, click Copy, use the program you want to paste (such as Microsoft Word), and then click Paste on the Edit menu. 4. To view the description of the previous event or the next event, press the up arrow button or down the arrow key. For additional information about how to use the Event Viewer diagnostic system problem, click the article number below to see the article in the Microsoft Knowledge Base:
324751 How to use event viewer diagnostic system issues in Windows Server 2003
Back to top
Use system information to determine the reason "System Information" tool for startup issues Display the detailed information of computer hardware, system components, and software environments. Using this tool helps determine device and device conflicts that may have problems. To do this, please follow these steps:
1. Click Start, and then click Run. 2. In the Open box, type MSINFO32 and click OK. 3. Find a problem with the device or device conflict. To do this, please follow these steps:
a. In the console tree, unfolding the components, and then click Problem. Please pay attention to any of the devices listed in the right pane. b. In the console tree, unfold hardware resources, then click Conflict / Sharing. Please pay attention to any resource conflicts listed in the right pane. c. If you find a problem with a problem, perform the appropriate action (for example, delete, disable, or reconfigure the device, or update the driver), then restart your computer in normal mode. You can use Device Manager to delete or disable devices and their drivers. For more information on "Device Manager", see the "Causes of Determining Start Using Device Manager" in this article. If the computer is started correctly, the particular device may be the cause of the startup problem. If you resolve this issue by disabling your device, make sure that the device is listed on Windows Server 2003 Hardware Compatibility List (HCL) and is properly installed. In addition, please report this phenomenon to the manufacturer and get information about possible updates that can resolve the startup problem. For information on how to contact your computer hardware manufacturer, click the article number below to see the article in the Microsoft Knowledge Base: 65416 Hardware and Software Third Party Supplier Contact List, A-K
60781 Hardware and Software Third Party Supplier Contact List, L-P
60782 Hardware and Software Third Party Supplier Contact List, Q-Z
Microsoft provides a third-party contact information for technical support. These contact information is subject to change without notice. Microsoft does not guarantee the accuracy of these third-party contact information. 4. If the System Information tool does not report any device conflict or a problem with a problem, check the program that is automatically started when Windows starts. To do this, please follow these steps:
a. In the console tree, expand the software environment and click Startup. The procedure that automatically starts automatically when Windows starts is launched in the right pane. b. Disable these programs, then restart your computer. For information on how to disable the program, see program documentation or contact with the manufacturer. c. If the startup problem is resolved after disabling the startup program, enabate these programs again (once a program is enabled). When a program is enabled, the computer is turned off and restarting the computer, and pay attention to whether an error occurred. If this phenomenon occurs, the last enabled program may be the cause of the error startup problem.
Back to top
To view the security mode Start log file To resolve the startup problem, check the startup log file ntbtlog.txt, and then write down the driver and service that the failed driver is loaded while launching your computer with Security Mode.
This log file is located in the% SystemRoot% folder (default for the Winnt folder). This log file lists devices and services that load (and load failed) when launching your computer in Security Mode. You can open and view log files using a text editor (such as "Notepad).
Using a list of drivers and services loaded during startup, it helps to determine the possible cause of startup issues.
Note: Some startup issues may appear early in the startup process. In this case, Windows may have not yet saved the launch log file to the hard disk.
Back to top
Using the Device Manager to determine the reason Device Manager "The Device Manager" is displayed in a graphical view to display the hardware installed in your computer. Use this tool to resolve any possible device conflicts or determine if it may result in an incompatible device that can start problems.
To launch the Device Manager, perform the following steps:
1. Click Start, right-click My Computer, and then click Manage. 2. Expand System Tools and click Device Manager. The device installed in the computer is listed in the right pane. If a symbol is displayed next to the device, the device may have problems. For example, the black exclamation mark (!) Indicates that the device is in a fault state. Note: To disable your device in Device Manager, right-click the device and click Disable. 3. Investigate possible devices conflicts. To do this, double-click the device in the right pane, then click Resource Tab. If there is a device conflict, the device will be listed under the Conflict Device List. Note "Use Auto Set" check box. If Windows successfully detects the device, this checkbox will be in the selected state, and the device will run normally. However, if the resource setting is based on "Basic Configuration N" (where N is any number from 0 to 9), you may need to change the configuration. To do this, click Different Basic Configurations in the list, or manually change the resource settings. WARNING: This process may need to change the complementary metal oxide semiconductor (CMOS) settings of your computer and the basic input / output system (BIOS) settings. Error changes to computer BIOS may result in serious problems. Change your computer's CMOS settings requires you to bother. If Windows cannot resolve resource conflicts, verify that the computer is configured to allow Windows to enumerate your computer. To do this, enable the "Plug and Play OS" settings in the computer BIOS setup tool. To change your computer's BIOS setting, see computer documentation or contact your computer manufacturer. 4. If you have determined a problematic device, disable it, then restart your computer in normal mode. If your computer is started correctly, your disabled device may be the cause of the startup problem. Make sure the device is listed on Windows Server 2003 Hardware Compatibility List (HCL) and is properly installed. In addition, please report this phenomenon to the manufacturer and get information about possible updates that can resolve the startup problem. For additional information about how to configure devices in Device Manager, click the article number below to view the article in the Microsoft Knowledge Base: 323423 How to use Device Manager in Windows Server 2003 to configure the device
Back to top
How to Use System Configuration Utility System (Msconfig.exe) can automatically complete the General Troubleshooting steps that "Microsoft Product Support Services" technicians use when diagnosing Windows configuration issues. You can use the exclusion method to modify the system configuration and solve the problem using this tool.
You must log in as a member of the Administrator or administrator group to use the System Configuration Utility. If your computer is connected, the network policy settings may prevent you from using the utility. As a "best practice" guaranteed, consider using the "Operations" command to perform these processes.
Note: Microsoft strongly recommends that you do not use the System Configuration Utility to modify the Boot.ini files on your computer without Microsoft support professionals. Doing this can cause your computer to not be used.
Back to top
Create a clean environment for troubleshooting
1. Click Start and Run in turn, type MSconfig in the Open box, and then click OK. (To use the Run Mode "command, type RunAs / User: Administrator path /msconfig.exe in the Open box, and then click OK.) 2. Click General tab, click" Diagnostic Start - Load Basic Device Drivers and Services, click OK, and then click Restart to restart your computer. 3. After starting Windows, determine if there is still a problem.
Back to top
Use the system start option to find a problem 1. Click Start and Run in turn, type MSconfig in the Open box, and then click OK. 2. Click the General tab and click Select Start. 3. Click the following checkbox to clear it:
Handling System.ini files
Handling Win.ini files
Load system service
You will not be able to clear the use of the original Boot.ini check box. 4. To test the software load process, make sure the Load Boot check box is selected, and then click OK. 5. Restart your computer based on the prompt.
Back to top
Use the "Selected Start" option to find a problem
1. Click Start and Run in turn, type MSconfig in the Open box, and then click OK. 2. Click the General tab and click Select Start. 3. Click All check boxes under the selected startup to clear it. You will not be able to clear the use of the original Boot.ini check box. 4. Click to process the System.ini file check box to select it, click OK, and then restart your computer when prompted. Repeat this process, select a check box each time. Restart your computer each time. Repeat this process until the problem occurs. 5. When there is a problem, click the tab corresponding to the selected file. For example, if you have a problem after selecting a Win.ini file, click the Win.ini tab in System Configuration Utility.
Back to top
Use the "Start" tab to find the problem
Start tabs list items from the "Start" group, Win.ini Load = and Run = and registry at startup.
1. Click Start and Run in turn, type MSconfig in the Open box, and then click OK. 2. Click Startup Tab. 3. Click all check box to clear it. 4. To start troubleshooting, click the first check box to select it, click OK, then restart your computer when prompted. Repeat this process, select a check box each time. Restart your computer each time. Repeat this process until the problem occurs.
Back to top
Solve system service issues
1. Click Start and Run in turn, type MSconfig in the Open box, and then click OK. 2. Click the Service tab. 3. Write down all the services unselected. Important: Do not skip this step. You will need this information later. 4. Click All Disabled, click OK, and then restart your computer. 5. Click Start and Run in turn, type MSConfig in the Open box, and then click OK. 6. Click the Service tab. 7. Click the check box for a service to select it to enable the service, and then click OK. 8. Restart your computer and see if this problem occurs. 9. Repeat step 5 to 8 for each service until the problem occurs. When the problem occurs, the last open service can be determined to cause problems. Write down the service and go to step 10. 10. Click All Enabled, click the check box next to the service, clear it; click the check box you record in step 3, clear it, click OK. Then restart the computer. As an alternative, you can turn off (unchecked) services with problems. Please contact the manufacturer of a problem with a problem to get more help. Note: By taking a group test service, you may be able to determine which service is a problem faster. Divide these services into two groups, select the first group of check boxes, and clear the second group of checkboxes. Restart your computer and then test this problem. If the problem occurs, there is a problem with the service in the selected check box. If the problem does not appear, a problem with a problem is in the group that has been cleared the check box. Repeat this process with that group with a problem until you find a problem with a problem.
Back to top
Solve the issue of the System.ini file
1. Click Start and Run in turn, type MSconfig in the Open box, and then click OK. 2. Click the System.ini tab. 3. Write down all items that are not selected. You may need to expand certain items (for example, [Drivers]) to determine if there is any child unchecked. Important: Do not skip this step. You will need this information later. 4. Click All Disabled, click OK, and then restart your computer. 5. Click Start and Run in turn, type MSConfig in the Open box, and then click OK. 6. Click the System.ini tab. 7. Expand all items in the list, click the checkbox of a item to open it, and then click OK. 8. Restart your computer and see if this problem occurs. 9. Each of the repeated steps 5 to 8 until the problem occurs. When the problem occurs, it can determine that the last open item is the cause of the problem. Write down the item and go to step 10. 10. Click All Enabled, click the check box next to the problem, clear it; click the check box you record in step 3, clear it, click OK. Then restart the computer. As an alternative, you can close (unchecked) issues with problems. If possible, please contact the manufacturer with questions to get more help. Note: By pressing group test items, you may be able to determine which System.ini items faster. These items are divided into two groups, select the first group of check boxes, and clear the second group of checkboxes. Restart your computer and then test this problem. If the problem occurs, there is a problem with the service in the selected check box. If the problem does not appear, a problem with a problem is in the group that has been cleared the check box. Repeat this process for the group of problems until you find a problematic System.ini item. Back to top
Solve the problem of Win.ini files
1. Click Start and Run in turn, type MSconfig in the Open box, and then click OK. 2. Click the Win.ini tab. 3. Write down all items that are not selected. You may need to expand certain items (for example, [Olfax Ports]) to determine if there is any child unchecked. Important: Do not skip this step. You will need this information later. 4. Click All Disabled, click OK, and then restart your computer. 5. Click Start and Run in turn, type MSConfig in the Open box, and then click OK. 6. Click the Win.ini tab. 7. Expand all items in the list, click the checkbox of a item to open it, and then click OK. 8. Restart your computer and see if this problem occurs. 9. Each of the repeated steps 5 to 8 until the problem occurs. When the problem occurs, it can determine that the last open item is the cause of the problem. Write down the item and go to step 10. 10. Click All Enable, click the check box with questions, clear it; click the check box for any other item you record in step 3, clear it, click OK, then Restart your computer. As an alternative, you can close (unchecked) issues with problems. If possible, please contact the manufacturer with questions to get more help. Note: By pressing group test items, you may be able to determine which Win.ini items have caused problems more quickly. These items are divided into two groups, select the first group of check boxes, and clear the second group of checkboxes. Restart your computer and then test this problem. If the problem occurs, there is a problem with the service in the selected check box. If the problem does not appear, a problem with a problem is in the group that has been cleared the check box. Repeat this process for the group of problems until you find a problem with Win.ini item. Back to top
Solving the problem with the Boot.ini file Only the system administrator and advanced users should try to change the boot.ini file. The steps to solve the problem related to Boot.ini are not within the scope of this article.
For additional information, search for Microsoft Knowledge Bases. To do this, please visit the following Microsoft Web site:
Microsoft Product Support Services
http://support.microsoft.com
Back to top
Resetting the System Configuration Utility To Normal Start To reset the System Configuration Utility to Normal startup, perform the following steps:
1. Click Start and Run in turn, type MSconfig in the Open box, and then click OK. 2. On the General tab, click "Normal Start-Load All Device Drivers and Services", and then click OK. 3. Restart your computer.
Back to top
How to use the Microsoft Windows Fault Recovery Console "Fault Recovery Console" is a command line tool, which can be used to fix Windows when the computer cannot start normally. You can launch the "Fault Recovery Console" from the Windows Server 2003 CD; or if the "failed recovery console" is installed on your computer, you can start the "Fault Recovery Console" at startup.
If you use "the most recent correct configuration" boot option, but not successful, and you can't start your computer under Safe Mode, use the "Fault Recovery Console". Microsoft recommends that this "failed recovery console" method can be used when you are an advanced user, you can use the basic command to determine and find a problematic driver and file.
To use the Fault Recovery Console, perform the following steps:
1. Insert the Windows Server 2003 installation CD into your CD-ROM or DVD-ROM drive and restart your computer. 2. When the system prompt is displayed during the text mode installation, press the R key to launch the "Fault Recovery Console". You can do the following: • Access the drive on your computer. • Enable or disable device drivers or services. • Copy files from Windows Server 2003 installation discs or copy files from other removable media. For example, you can copy the desired deleted file. • Create a new boot sector and a new main boot record (MBR). You will need this if you have problems caused by existing boot sectors.
Back to top
Confirm that the hard disk or file system is intact to determine if your hard disk or file system is not damaged, start the computer from the Windows Server 2003 CD, start the "Fault Recovery Console", then use
CHKDSK command line utility. This may solve this problem.
Important: Microsoft only recommends advanced users or administrators using the "Fault Recovery Console". You must know the password for the Administrator account to use the "Fault Recovery Console".
How to use
CHKDSK tests and fixes additional information about the damaged hard drive, see "Using the Fault Recovery Console" and "Using the Fault Recovery Console Command Prompt" in the article:
307654 How to install and use Windows XP failure recovery console
Note: If
The Chkdsk report cannot access the hard disk, and your hardware may have faults. Check all cable connections and jumper settings on your drive. Contact Professionals or Computer Manufacturers in Computer to get more help.
in case
The Chkdsk report cannot fix all hard disk issues, your file system or MBR may be damaged or cannot be accessed. Try using the appropriate "failed recovery console" command (for example,
Fixmbr and
FIXBOOT, contact data recovery service, or restrict the hard disk and reformat the hard drive.
WARNING: If you restrict and reformat your hard drive, all information on your hard drive will be lost.
Important: If you need further assistance, please contact your computer manufacturer or "Microsoft Product Support Services" professionals. Only person with appropriate qualifications should try to repair the computer. If computer repair is performed by non-professionals, the warranty of the computer may be invalidated.
For additional information about how to use the "Fault Recovery Console", click the article number below to see the article in the Microsoft Knowledge Base:
326215 How to use a failed recovery console on a Windows Server 2003-based computer that cannot be launched
Back to top
How to use Automatic System Fault Recovery To use Auto System Fault Recovery (ASR) to recover from the system failure, perform the following steps:
1. Before you start the recovery process, make sure that the hand has the following:
• The ASR floppy disk you created before. • The backup media you have created before. • Original operating system installation disc. • If you have a massive storage controller and know that the manufacturer has provided a separate driver file (the driver file is different from the driver file provided on the installation CD), you will get the process before starting this process. Document (on the floppy disk). 2. Insert the original operating system installation CD into the CD-ROM or DVD-ROM drive. 3. Restart your computer. If you prompt you to press a key to start your computer from the CD, press the appropriate key. 4. If you have a separate driver file as described in step 1, press the F6 key when the system prompt is prompted to use the driver as part of the installation. 5. Press the F2 key when the system is in the beginning of the installed plain text mode. The system will prompt you to insert the previously created ASR floppy disk. 6. Follow the instructions on the screen. 7. If you have a separate driver file as described in step 1, press the F6 key (second) when prompted after the system restarts. 8. Follow the instructions on the screen. note:
• ASR does not restore your data file. For more information on backup and restore data files, see Windows Help. • If all nodes in the server cluster in the server cluster are failed and cannot be reducing them from backups, the ASR on each node in the original cluster is used to restore disk signature and clustered partition layout (arbitration and non-exclaim) . For more information on backup and restore server clusters, see Windows Help.
Back to top
To create an ASR disk set using a backup To use ASR, you must have an ASR disk set. To create an ASR disk set, perform the following steps:
1. Click Start, point to All Programs, point to Accessories, point to System Tools, and then click Backup. The Backup or Restore Wizard will be launched by default unless the wizard is disabled. You can create an ASR disk set using the Backup or Restore Wizard by answering all the information on this computer in "What?" Section is to back up. Otherwise, you can go to the next step and create an ASR disk set in advanced mode. 2. Click Advanced Mode Link in Backup or Restore Wizard. 3. On the Tools menu, click the ASR wizard. 4. Follow the instructions that appear on the screen.
note:
• You need an empty 1.44 megabyte (MB) floppy disk to save your system settings and require a media to accommodate backup files. If your computer does not have a floppy drive, an ASR backup is performed on a computer without a floppy drive. Copy the ASR.SIF and ASRPNP.SIF files in the% SystemRoot% / Repair folder to other computers with floppy drives, and then copy these files to the floppy disk. • To perform this procedure, you must be a member of the Administrators group or the Backup Operators group on the local computer, or you must obtain the appropriate authorization. If the computer adds a certain domain, members of the Domain Admins group should be able to perform this process. As a "best practice" guaranteed, consider using the "Operation Mode" command to perform this process. • This procedure only backs up those system files necessary to start the system. You must back up the data file separately. • After creating an ASR set, then the floppy disk is labeled, then carefully back up the media and keep them together. To use backup media, you must have a floppy created with the media set. You cannot use floppy disks created at different times or with different media sets. You must have a available installation disc in executive ASR. • Please save the ASR set in the security. The ASR set includes information about system configuration, which may be used to destroy your system. • If you are backing up the server cluster, run Automatic System Fault Recovery Wizard on all nodes of the cluster, and make sure that the cluster service is running when each ASR backup is started. When running the Automatic System Failure Recovery Wizard, make sure that one of the nodes running the wizard is listed as the owner of the arbitration resource. How to fix Windows Installation You run a Windows installer from the Windows CD to repair corrupted Windows Server 2003 installation.
To fix the installation of Windows, perform the following steps:
1. Insert the Windows Server 2003 disc in the CD-ROM or DVD-ROM drive. 2. If the Windows CD displays "What do you want?" Menu, click Exit. 3. Turn off the computer, wait for 10 seconds, and turn it on again. 4. If the system prompts you to start your computer from the CD, please do this. Note: You must be able to boot your computer from the Windows Server 2003 CD-ROM to run the Windows installer. You must configure the CD-ROM or DVD-ROM drive to make this. For information on how to configure a computer to start from a CD-ROM or DVD-ROM drive, see a document included in your computer or contact your computer manufacturer. 5. After the installation begins, press ENTER to continue the installation process. 6. Press ENTER to select "To install Windows now, press ENTER" option. Not to choose a fault recovery console option. 7. Press the F8 key to accept the license agreement. The installer will search for previous Windows installations.
• If the installer does not find the previous Windows Server 2003 installation, you may have a hardware failure. Hardware failure is not within the discussion of this article. Please consult your computer hardware professionals to get more help, or try to use the Hardware Troubleshore. For more information on Hardware Troubleshooters, see Windows Server 2003 Help Topics "Use Troubleshooter". • If the installer finds the previous Windows Server 2003 installation, the following message may be displayed:
If one of the following Windows Server 2003 installation is destroyed, the installer may try to fix it. Use up and down arrows to select a installation. To fix the selected installation, press the R key. To continue without repair, press the ESC key.
Select the appropriate Windows Server 2003 operating system installation, then press R to try to fix. • Press the screen instructions to fix the installation. Note: • You may need to change the order in which the boot drive is changed in the BIOS settings to successfully start your computer from the Windows Server 2003 CD. Please contact your computer manufacturer or see the documentation provided by the manufacturer for more information. • If you are unable to start your computer from the Windows Server 2003 CD, there may be a CD-ROM or DVD-ROM drive failure or other hardware failures. Hardware failure is not within the discussion of this article. Please consult your computer hardware professionals to get more help, or try to use the Hardware Troubleshore. For more information on Hardware Troubleshooters, see Windows Server 2003 Help Topics "Use Troubleshooter". • After repairing Windows Server 2003, you may need to reactivate your copy of your Windows Server 2003.
