Windows 2003 Server Standard Edition startup Problem resolution (Resource repost)

One of the maintenance systems is deployed on the WINDOWS2003 Server Standard Edition of the servers, may be due to an application problem, causing the remote restart failed, so I spent a morning in the computer room, can be enough toss. Finally, according to the official documents to solve, just put the document address is: HTTP://SUPPORT.MICROSOFT.COM/KB/325375/ZH-CN

The content is:

This article describes the general procedures that you can use to troubleshoot startup issues in Windows Server 2003.

A successful Windows startup consists of the following four phases:

• Initial stage
• Boot loader phase
• Kernel phase
• Logon phase

If a problem occurs at one of these stages, Windows may not start correctly, and you may experience one of the following issues:

• The computer stops responding (hangs).
• You receive an error message.

If the startup issue occurs after you click Microsoft Windows Server 2003 on the boot loader menu or when you receive the "Please select the operating system to start" message, the file that the operating system requires may be missing or corrupted. Windows provides several options that you can use to resolve this issue, including Safe mode, Recovery Console, and Automated System recovery.

Back to the top how to start the computer using Last Known Good Configuration if the startup problem occurs immediately after you make a change to the computer, such as after you install a new driver, try to start the computer by using the Last Known Good Configuration feature.

When you use the last Known Good Configuration feature, you start your computer with the most recent possible setting. This feature restores valid registry information and driver settings when the computer was last successfully started. You should use this feature if you cannot start Windows after you make changes to your computer, such as after you install or upgrade a device driver.

To start the computer by using the Last Known Good Configuration feature, follow these steps:

1. Click Start, and then click Shut Down.
2. Click Restart, and then click OK.
3. When you see the "Please select the operating system to start" message, press the F8 key.
4. Use the arrow keys to select Last Known Good Configuration, and then press Enter.
   
   Note : Num Lock must be turned off so that the arrow keys on the numeric keypad will work.
5. If you are running a different operating system on your computer, click Microsoft Windows Server 2003 in the list, and then press Enter.

Note

• By selecting Last Known Good Configuration, you can recover from a problem, such as a newly added driver that might not be appropriate for your hardware. This feature does not resolve problems caused by driver or file corruption or missing.
• When you select Last Known Good Configuration, only the information in the registry key Hklm/system/currentcontrolset is restored. Any changes that you make in other registry keys are preserved.

If you can use Last Known Good configuration to start your computer, the last change you made to your computer, such as installing a driver, might be the cause of the wrong startup behavior. Microsoft recommends that you remove or update the driver or program, and then test whether Windows starts correctly.

Back to the top how to start your computer in Safe mode when you start your computer in Safe mode, Windows loads only the drivers and computer services that you need. You can use Safe mode to identify and resolve problems that are caused by an automatically initiated, faulty driver, program, or service.

If the computer can start successfully in Safe mode, but cannot start in normal mode, the computer may have a conflict in hardware settings or resource allocation. It is possible that the system is incompatible with some programs, services, or drivers, or the registry is corrupted. In Safe mode, you can disable or Remove Programs, services, or device drivers that may prevent your computer from starting.

To troubleshoot startup issues in Safe mode, follow these steps:

1. Click Start, and then click Shut Down.
2. Click Restart, and then click OK.
3. When you see the "Please select the operating system to start" message, press F8.
4. In the Windows Advanced Options menu, use the arrow keys to select Safe Mode, and then press Enter.
   
   Note : Num Lock must be turned off so that the arrow keys on the numeric keypad will work.
5. If you are running a different operating system on your computer, click Microsoft Windows Server 2003 on the list that appears, and then press Enter.
6. Perform one of the following actions:
   • If the computer does not start in safe mode, try to start the computer by using the Recovery Console. If you still cannot start the computer, look for possible hardware problems, such as defective devices, installation problems, cable problems, or connector problems. Remove any newly added hardware, and then restart the computer to see if the problem has been resolved.
   • If your computer can start in safe mode, go to the next section to continue troubleshooting startup issues.

Use Event Viewer to determine the cause of the startup problem view the event log in Event Viewer for additional information that can help you identify and diagnose the cause of the startup problem. To view the events that are logged in the event log, follow these steps:

1. Perform one of the following actions:
   • Click Start, point to Administrative Tools, and then click Event Viewer.
   • Start the Event Viewer snap-in in Microsoft Management Console (MMC).
2. In the console tree, expand Event Viewer, and then click the log that you want to view. For example, click the System log or the application log.
3. In the details pane, double-click the event that you want to view.
   
   To copy the details of the event, click Copy, open a new document with the program in which you want to paste the event (for example, 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 or DOWN ARROW key.

Use System information to determine the cause of the startup problem The System Information tool displays comprehensive information about the computer hardware, system components, and the software environment. Use this tool to help identify possible problems with device and device conflicts. To do this, follow these steps:

2. Click Start, and then click Run.
4. In the Open box, type msinfo32, and then click OK.
6. Look for a problem device or device conflict. To do this, follow these steps:
   1. In the console tree, expand Components, and then click Problematic Devices.
      
      Note any devices that are listed in the right pane.
   2. In the console tree, expand Hardware Resources, and then click Conflicts/Sharing.
      
      Note Any resource conflicts that are listed in the right pane.
   3. If you find a device that has the problem, perform the appropriate action (for example, remove, disable, or reconfigure the device, or update the driver), and then restart the computer in normal mode.
      
      You can use Device Manager to remove or disable the device and its drivers. For more information about Device Manager, see the section using Device Manager to determine the cause of a startup problem in this article.
      
      If the computer starts normally, that particular device may be the cause of the startup problem.
      
      If you are troubleshooting the problem by disabling the device, make sure that the device is listed in the Windows Server 2003 hardware Compatibility List (HCL) and that it is installed correctly. Also, report the problem to the manufacturer for information about possible updates that can resolve the startup issue. For information about how to contact your computer hardware manufacturer, click the appropriate article number in the following list to view the article in the Microsoft Knowledge Base: 65416 Hardware and software vendor contact information, A-k
      
      60781 Hardware and software vendor contact information, L-p
      
      60782 Hardware and software vendor contact information, Q-zmicrosoft provides third-party contact information to facilitate your search for technical support. These contact information is subject to change without prior notice. Microsoft does not guarantee the accuracy of these third-party contact information.
8. If the System Information tool does not report any device conflicts or problematic devices, check the programs that start automatically when Windows starts. To do this, follow these steps:
   1. In the console tree, expand Software Environment, and then click Start Program.
      
      The right pane lists programs that start automatically when Windows starts.
   2. Disable these programs, and then restart your computer.
      
      For information about how to disable a program, see the program documentation or contact the manufacturer.
   3. If startup issues are resolved after disabling the startup program, enable the programs again (one program at a time).
      
      Shut down and restart the computer each time a program is enabled, and notice that there is an incorrect startup problem. If this problem occurs, the last program that is enabled may be the cause of the error startup problem.

View Safe mode startup log files to resolve startup issues, review the boot log file Ntbtlog.txt, and then note the drivers and services that were not loaded when you started your computer in Safe mode.

This log file is located in the%SystemRoot% folder (the Windows folder by default). This log file lists the devices and services that are loaded (and not loaded) when you start your computer in Safe mode. You can use a text editor, such as Notepad, to open and view the log files.

Using a list of drivers and services that were not loaded during startup helps you determine the possible cause of the startup problem.

Note: Some startup issues may occur early in the startup process. In this scenario, Windows may not have the startup log file saved to your hard disk.

Use Device Manager to determine the cause of the startup Problem Device Manager displays the hardware installed in the computer in a graphical view. Use this tool to resolve any possible device conflicts or to identify incompatible devices that may cause startup problems.

To start Device Manager, follow these steps:

1. Click Start, right-click My Computer, and then click Manage.
2. , expand System Tools, and then click Device Manager.  
   
   The device installed on your computer is listed in the right pane. If a symbol is displayed next to the device, there may be a problem with the device. For example, a black exclamation point (!) on the yellow bottom indicates that the device is in a failed state.
   
   Note : To disable a device in Device Manager, right-click the device, and then click Disable.
3. to investigate possible device conflicts. To do this, double-click the device in the right pane, and then on the Resources tab.  
   
   If there is a device conflict, the device is listed under the Conflicting Devices list.  
   
   Note the Use Automatic settings check box. If Windows successfully detects a device, this check box is selected and the device is functioning correctly. However, if the resource settings are 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 a different base configuration in the list, or manually change the resource settings. Warning : This procedure may require you to change your computer's complementary metal oxide Semiconductor (CMOS) settings and basic input/output system (BIOS) settings. Incorrect changes to the computer BIOS can cause serious problems. Changing your computer's CMOS settings requires you to be at your own risk.  
   
   If Windows cannot resolve a resource conflict, verify that the computer is configured to allow Windows to enumerate the devices in the computer. To do this, enable the "Plug and Play OS" setting in the Setup tool in the computer BIOS. To change your computer's BIOS settings, see your computer's documentation or contact the computer manufacturer.
4. If you identify the device that has the problem, disable it, and then restart the computer in normal mode.  
   
   If the computer starts normally, the device that you disabled may be the cause of the startup problem.  
   
   Make sure that the device is listed on the Windows Server 2003 hardware Compatibility List (HCL) and that it is installed correctly. Also, report the problem to the manufacturer for information about possible updates that can resolve the startup issue.

For additional information about how to configure devices in Device Manager, click the following article number to view the article in the Microsoft Knowledge Base: 323423 How to do this in Windows Server 2003 Use Device Manager to configure the device back to the top how to use the System Configuration Utility System Configuration Utility (Msconfig.exe) to automate the general troubleshooting steps that Microsoft product Support Services technicians use when diagnosing Windows configuration problems. You can use the exclusion method to modify the system configuration and resolve the problem using this tool.

You must be logged on as an administrator or a member of the Administrators group to use the System Configuration Utility. If your computer is networked, network policy settings may prevent you from using the utility. As a "best practice" for security, consider using the Run as command to perform these procedures.

Note: Microsoft strongly recommends that you do not use the System Configuration Utility to modify the boot. ini file on your computer without the help of a Microsoft technical support professional. Doing this may cause your computer to be unusable.

Create a clean environment for troubleshooting

1. Click Start and Run, type msconfig in the Open box , and then click OK. (To use the Run as command, type Runas/user:administrator/msconfig.exe in the Open box Path , and then click OK.) )
2. Click the General tab, click Diagnostic Startup-load basic device drivers and services only, click OK, and then click Restart to restart the computer.
3. After you start Windows, determine whether the problem still occurs.

Use the System startup option to isolate the problem

1. Click Start and Run, type msconfig in the Open box , and then click OK.
2. Click the General tab, and then click Selective Startup.
3. Click to clear the following check boxes: process SYSTEM. INI file
   Handle WIN. INI file
   Loading System Services you will not be able to clear the "use original BOOT." INI check box.
4. To test the software load process, make sure that the Load Startup items check box is selected, and then click OK.
5. Restart the computer as prompted.

Use the Selective startup option to isolate the problem

1. Click Start and Run, type msconfig in the Open box , and then click OK.
2. Click the General tab, and then click Selective Startup.
3. Click to clear all the check boxes under Selective startup. You will not be able to clear the "use original BOOT." INI check box.
4. Click to select the process SYSTEM. INI file check box, click OK, and then restart the computer when you are prompted.
   
   Repeat this procedure by selecting one check box at a time. You should restart your computer every time. Repeat this process until the problem occurs.
5. When the problem occurs, click the tab that corresponds to the selected file. For example, if the problem occurs after you select the Win.ini file, click Win in the System Configuration Utility. INI tab.

Use the Startup tab to find the problem the Startup tab lists the items that are loaded at startup from the Startup group, Win.ini load=, and run=, and the registry.

1. Click Start and Run, type msconfig in the Open box , and then click OK.
2. Click the Startup tab.
3. Click to clear all the check boxes.
4. To start troubleshooting, click to select the First check box, click OK, and then restart the computer when you are prompted to do so.
   
   Repeat this procedure by selecting one check box at a time. You should restart your computer every time. Repeat this process until the problem occurs.

Troubleshoot system service issues

1. Click Start and Run, type msconfig in the Open box , and then click OK.
2. Click the Services tab.
3. Make a note of all services that are not selected.
   
   important : Do not skip this step. You will need this information later.
4. Click Disable all, click OK, and then restart the computer.
5. Click Start and Run, type msconfig in the Open box , and then click OK.
6. Click the Services tab.
7. Click to select the check box for a service to enable the service, and then click OK.
8. Restart your computer to see if this problem occurs.
9. Repeat steps 5 through 8 for each service until the problem occurs. When a problem occurs, you can conclude that the last service opened is the cause of the problem. Make a note of the service, and then go to step 10.
10. Click Enable all, click to clear the check box next to the problematic service, click to clear the check box for any other services that you noted in step 3, click OK, and then restart the computer.
    
    As an alternative, you can turn off (uncheck) the problematic service. Please contact the manufacturer of the problematic service for further assistance.
    
    Note : By testing services by group, you may be able to determine faster which service is causing the problem. Divide these services into two groups, select the check boxes for the first group, and clear the check boxes for the second group. Restart the computer, and then test whether the problem occurs. If the problem occurs, the problematic service is in the group that has the check box selected. If the problem does not occur, the problematic service is in the group that has the cleared check box. Repeat this process for the group that has the problem until you find the problematic service.

Troubleshoot problems with System.ini files

1. Click Start and Run, type msconfig in the Open box , and then click OK.
2. Click SYSTEM. INI tab.
3. Make a note of all items that are not selected. You may need to expand some items (for example, "[Drivers]") to determine whether there are any unselected subkeys.
   
   important : Do not skip this step. You will need this information later.
4. Click Disable all, click OK, and then restart the computer.
5. Click Start and Run, type msconfig in the Open box , and then click OK.
6. Click SYSTEM. INI tab.
7. Expand all the items in the list, click the check box for an item to open it, and then click OK.
8. Restart your computer to see if this problem occurs.
9. Repeat steps 5 through 8 for each item until the problem occurs.
   
   When a problem occurs, you can conclude that the last item opened is the cause of the problem. Make a note of the entry, and then go to step 10.
10. Click Enable all, click to clear the check box next to the problematic item, click to clear the check box for any other items that you noted in step 3, click OK, and then restart the computer.
    
    As an alternative, you can turn off (unchecked) the problematic item. If possible, contact the manufacturer of the item in question for further assistance.
    
    Note : By testing items by group, you may be able to quickly determine which System.ini item is causing the problem. Divide the items into two groups, select the check boxes for the first group, and clear the check boxes for the second group. Restart the computer, and then test whether the problem occurs. If the problem occurs, the problematic service is in the group that has the check box selected. If the problem does not occur, the problematic service is in the group that has the cleared check box. Repeat this process for the group that has the problem until you find the problematic System.ini item.

Troubleshoot problems with Win.ini files

1. Click Start and Run, type msconfig in the Open box , and then click OK.
2. Click WIN. INI tab.
3. Make a note of all items that are not selected. You may need to expand some items (for example, "[OLFax Ports]") to determine if there are any unselected subkeys.
   
   important : Do not skip this step. You will need this information later.
4. Click Disable all, click OK, and then restart the computer.
5. Click Start and Run, type msconfig in the Open box , and then click OK.
6. Click WIN. INI tab.
7. Expand all the items in the list, click the check box for an item to open it, and then click OK.
8. Restart your computer to see if this problem occurs.
9. Repeat steps 5 through 8 for each item until the problem occurs.
   
   When a problem occurs, you can conclude that the last item opened is the cause of the problem. Make a note of the entry, and then go to step 10.
10. Click Enable all, click to clear the check box for the problematic item, click to clear the check box for any other items that you noted in step 3, click OK, and then restart the computer.
    
    As an alternative, you can turn off (unchecked) the problematic item. If possible, contact the manufacturer of the item in question for further assistance.
    
    Note : By testing items by group, you may be able to quickly determine which Win.ini item is causing the problem. Divide the items into two groups, select the check boxes for the first group, and clear the check boxes for the second group. Restart the computer, and then test whether the problem occurs. If the problem occurs, the problematic service is in the group that has the check box selected. If the problem does not occur, the problematic service is in the group that has the cleared check box. Repeat this process for the group that has the problem until you find the problematic Win.ini item.

Troubleshooting the boot. ini file only system administrators and advanced users should attempt to change the boot. ini file. The steps to resolve issues related to boot. ini are beyond the scope of this article.

For additional information, please search the Microsoft Knowledge Base. To do this, visit the following Microsoft Web site: Microsoft Product Support Services
http://support.microsoft.com Resetting the System Configuration Utility to normal startup to reset the system Configuration Utility to normal startup, follow these steps:

1. Click Start and Run, type msconfig in the Open box , and then click OK.
2. On the General tab, click Normal Startup-load all device drivers and services, and then click OK.
3. Restart the computer.

Back to the top how to use the Microsoft Windows Recovery Console Recovery Console is a command-line tool that you can use to repair Windows when your computer does not start properly. You can start the Recovery Console from the Windows Server 2003 CD, or you can start the Recovery Console at startup If the Recovery Console was previously installed on your computer.

If you used the last Known Good Configuration startup option but did not succeed and you cannot start the computer in Safe mode, use the Recovery Console. Microsoft recommends that you use this Recovery Console method only if you are an advanced user who can use basic commands to identify and locate problematic drivers and files.

To use the Recovery Console, follow these steps:

1. Insert the Windows Server 2003 installation CD into your CD-ROM or DVD-ROM drive, and then restart the computer.
2. When prompted during text-mode Setup, press R to start the Recovery Console.

You can use the Recovery Console to perform the following actions:

• Access the drives on your computer.
• Enable or disable a device driver or service.
• Copy files from the Windows Server 2003 installation CD or copy files from other removable media. For example, you can copy the deleted files that you want.
• Creates a new boot sector and a new master boot record (MBR). You will need to do this if there is an issue caused by an existing boot sector.

Confirm that the hard disk or file system is intact to determine that your hard disk or file system is not damaged, start the computer from the Windows Server 2003 CD, start the Recovery Console, and then use ChkdskCommand-line utility. This may solve the problem.

Important Notes: Microsoft recommends only advanced users or administrators to use the Recovery Console. You must know the password of the administrator account to use the Recovery Console.

about how to use ChkdskFor additional information on testing and repairing a damaged hard drive, see "Using the Recovery Console" and "Using Recovery Console command Prompt" in the following article: 307654 How to install and use the Recovery Console for Windows XP Note: If ChkdskReports that it cannot access the hard disk, your hardware may be faulty. Check all cable connections and jumper settings on the drive. Contact the computer repair Professional or computer manufacturer for further assistance.

If ChkdskThe report cannot fix all hard disk problems, your file system or MBR may be compromised or no longer accessible. Try using the appropriate Recovery Console commands (such as FixmbrAnd Fixboot), contact the data recovery service, or repartition and then reformat the hard disk.

Warning: If you repartition and reformat your hard disk, you will lose all the information on your hard disk.

Important Notes: For further assistance, please contact your computer manufacturer or Microsoft product Support Services professional. Only people with the appropriate qualifications should attempt to repair the computer. If a computer repair is performed by a non-professional, it may invalidate the computer's warranty. For additional information about how to use the Recovery Console, click the following article number to view the article in the Microsoft Knowledge Base: 326215 How to start a Windows Server 2003-based On the computer using the Recovery Console back to the top how to use automatic system recovery to recover from a system failure using Automated System Restore (ASR), follow these steps:

1. Before you begin the recovery process, make sure that you have the following items at hand:
   • The ASR floppy disk that you previously created.
   • The backup media that you created earlier.
   • The original operating system installation CD.
   • If you have a mass storage controller and you know that the manufacturer has provided it with a separate driver file (which differs from the driver file that is provided on the installation CD), obtain the file (on the floppy disk) before you begin this procedure.
2. Insert the original operating system installation CD into the CD-ROM or DVD-ROM drive.
3. Restart the computer. If you are prompted to press a key to start the 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 prompted to use the driver as part of the installation.
5. When the system prompts you at the beginning of the plain text mode of installation, press the F2 key.
   
   You will be prompted to insert a previously created ASR floppy disk.
6. Follow the on-screen instructions.
7. If you have a separate driver file as described in step 1, press F6 (the second time) when prompted after the system restarts.
8. Follow the on-screen instructions.

Note

• ASR does not restore your data files. For more information about backing up and restoring data files, see Windows Help.
• If all the nodes in the server cluster that you are restoring fail and cannot restore the quorum disk from the backup, use ASR on each node in the original cluster to restore the disk signature and partition layout of the cluster disks (quorum and non-quorum). For more information about backing up and restoring a server cluster, see Windows Help.

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, follow these steps:

1. Click Start, point to All Programs, point to Accessories, point to System Tools, and then click Backup.
   
   The Backup or Restore Wizard starts by default, unless the wizard is disabled. You can do so by "what are you going to back up?" section, answer "All information on this computer" and use the Backup or Restore Wizard to create an ASR disk set. Otherwise, you can go to the next step and create an ASR disk set in Advanced mode.
2. In the Backup or Restore Wizard, click the Advanced Mode link.
3. On the Tools menu, click 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 you need a media to hold the backup files. If your computer does not have a floppy disk drive, perform an ASR backup on a computer that does not have a floppy disk drive. Copy the Asr.sif and Asrpnp.sif files from the%systemroot%/repair folder to another computer that has a floppy disk drive, and then copy the 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 have the appropriate authorization. If the computer is joined to a domain, members of the Domain Admins group should be able to perform this procedure. As a "best practice" for security, consider using the Run as command to perform this procedure.
• This procedure backs up only those system files that you must have to start the system. You must back up your data files separately.
• After you create the ASR set, carefully label the floppy disk and the backup media, and keep them together. To use backup media, you must have a floppy disk created with that media set. You cannot use floppy disks that are created at different times or with different media sets. You must also have an available installation CD when you perform the ASR.
• Please keep the ASR set in a safe place. The ASR set contains information about the system configuration that may be used to compromise your system.
• If you are backing up a server cluster, run the Automated System Recovery Wizard on all nodes of the cluster, and ensure that the Cluster service is running when each ASR backup starts. When you run the Automated System Recovery Preparation Wizard, make sure that one of the nodes running the wizard is listed as the owner of the quorum resource.

Back to the top how to fix Windows Setup by running Windows Setup from a Windows CD, you might be able to repair a damaged Windows Server 2003 installation.

To repair your Windows installation, follow these steps:

2. Insert a Windows Server 2003 CD into the CD-ROM or DVD-ROM drive.
4. If the Windows CD displays "What do you want to do?" menu, click Exit.
6. Turn off the computer, wait 10 seconds, and then turn the computer back on.
8. If you are prompted to start the computer from the CD, do so.
   
   Note : You must be able to start the computer from the Windows Server 2003 CD-ROM before you can run Windows Setup. You must configure the CD-ROM or DVD-ROM drive to enable this operation. For information about how to configure your computer to boot from a CD-ROM or DVD-ROM drive, see the documentation that is included with your computer or contact the computer manufacturer.
10. After the installation begins, press Enter to continue the installation process.
12. Press ENTER to select the "to install Windows now, press ENTER" option. Instead of selecting the Recovery Console option.
13. The
14. accepts the license agreement by F8.  
    
    Setup will search for previous Windows installations.
    • If the Setup program does not find a previous Windows Server 2003 installation, there may be a hardware failure. The
      
      hardware failure is not covered in this article. Check with your computer hardware professional for more help, or try the Hardware troubleshooter. For more information about the Hardware troubleshooter, see the Windows Server 2003 Help topic, "Using Troubleshooting."
    • If Setup finds a previous Windows Server 2003 installation, the following message may be displayed: if one of the following Windows Server 2003 installations is compromised, Setup may try to repair it. Please use the UP ARROW and DOWN ARROW keys to select an installation. To repair the selected installation, press R. To continue without repairing, press ESC. Select the appropriate Windows Server 2003 operating system installation, and then press R to try the fix.
    • Follow the onscreen instructions to repair the installation.
      
      Note
      • You may need to change the order of the boot drives in the BIOS settings to successfully start the computer from the Windows Server 2003 CD. Contact your computer manufacturer or refer to the documentation provided by the manufacturer for more information.
      • If you are unable to start the computer from the Windows Server 2003 CD, there may be a CD-ROM or DVD-ROM drive failure or other hardware failure. The
        
        hardware failure is not covered in this article. Check with your computer hardware professional for more help, or try the Hardware troubleshooter. For more information about the Hardware troubleshooter, see the Windows Server 2003 Help topic, "Using Troubleshooting."
      • After you repair Windows Server 2003, you may have to reactivate your copy of Windows Server 2003.

Back to the top how to find a solution using the Microsoft Product Support Services Web site if you do not resolve the problem by following the steps provided in this article, you can use the Microsoft Product Support Services Web site to find a solution to the problem. The following list describes some of the services that are available on the Microsoft Product Support Services Web site:

• Searchable Knowledge Base-search technical support information and self-service tools for Microsoft products.
• FAQs-View Product-specific FAQs and important support information.
• Microsoft Product Support Newsgroups-Consult with your partner, peers, and Microsoft's most valuable expert (MVP).
• Software and updates-find software and updates in the Download Center.
• Additional support options-use the Web to ask a support question or call Microsoft product Support Services.

Back to the top The information in this article applies to:

• Microsoft Windows Server 2003 Datacenter Edition
• Microsoft Windows Server 2003 Enterprise Edition
• Microsoft Windows Server 2003 Standard Edition
• Microsoft Windows Server 2003 Web Edition
• Microsoft Windows Server 2003, 64-bit Datacenter Edition
• Microsoft Windows Server 2003, Enterprise x64 Edition
• Microsoft Windows Small Business Server 2003 Standard Edition
• Microsoft Windows Small Business Server 2003 Premium Edition

Back to the top

Key words:

Kbhowtomaster kbenv kbmgmtservices KB325375

Back to the top

Microsoft and/or its suppliers make no representations regarding the suitability of the documents published on this server for any purpose and the information contained in the graphics. All such documents and related graphics are provided "as is" without warranties of any kind. Microsoft and/or its suppliers hereby disclaim all warranties and conditions with respect to such information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event will Microsoft and/or its suppliers be liable for any special, indirect, consequential or any loss of use, data or profits arising out of or in connection with the use or operation of the information on the server or in any proceedings relating to such use or operation, No liability for data or profits.

Windows 2003 Server Standard Edition startup Problem resolution (Resource repost)