Troubleshooting boot failures in Windows 2003

Most of us have had the problem before. You start up your Windows machine and are greeted with a cryptic error message or “blue screen of death” before your system boots. It’s a sinking feeling. You cannot access the operating system and troubleshooting the problem can be difficult. In most cases, people end up resorting to drastic measures, such as reformatting the hard drive and re installing the operating system. It’s not always a lost cause. Windows Server 2003 includes a number of alternative boot options to help you troubleshoot and resolve these issues.

When attempting to recover from a Windows boot failure, the first step is to get to the boot options menu. You can do this by hitting the F8 key on your keyboard immediately after the Windows boot loader screen is displayed. Once you have accessed the boot options menu, you will have a number of options which are outlined below:

Safe Mode

This option starts the operating system with a bare minimum of system drivers. Safe Mode will help you when troubleshooting boot failures caused by device drivers and registry problems. This mode does not provide networking support and most system services are disabled.

Safe Mode with Networking

The same exact thing as Safe Mode, only with Networking support.

Safe Mode with Command Prompt

This is a command line interface. It can be useful for renaming files and doing other basic command line routines. The windows explorer shell is not loaded and it’s basically just a dos prompt.

Enable Boot Logging

Boot logging starts the system normally, but it creates a detailed log of all the services and drivers that are trying to load at boot time. This can help you determine what is causing the system to crash. The default location for the log file is C:Windowsntbtlog.txt.

Enable VGA Mode

This actually loads the currently installed video driver, but uses the lowest resolution and color depth available. This is a useful option if you are troubleshooting an issue with your video card or monitor driver.

Last Known Good Configuration

You can use this option to revert to a copy of the registry that was saved during the last successful login to Windows. Although it sounds great, I can’t remember a single instance that this has ever worked for me in the past, and believe me, I’ve tried it several times.

Directory Services Restore Mode

This is only applicable for Active Directory Domain Controllers. It allows you to perform maintenance and backup recovery tasks on Active Directory.

Debugging Mode

This will allow you to hook up a working server via a serial cable to send debugging messages for analysis. This requires a great deal of configuration on the receiving end and may not be a realistic option for most people.

Finally, you can use the Recovery Console to perform more advanced troubleshooting. The Recovery Console is not installed by default. If it is not installed, you can still use it by booting to the Operating System CD and choosing the “Repair with Recovery Console” option. The Recovery Console allows you to change service startup options, create or extend volumes and or select alternative boot options.

In this article we’ve covered the multiple boot options provided by Windows Server 2003. If you are not dealing with a hardware failure you can often narrow down and correct most boot problems in Windows Server 2003 using these tools.

When I run a script in Windows Script, I receive an error message: "Library not registered"

When you try to run a script in Windows Script, you receive the following error message:

Error: Library not registered.
Code: 8002801D
Source: (null)

Cause

This problem occurs because one or more of the scripting components are not registered in the Windows registry.

Resolution

To resolve this problem, use one of the following methods.

Method 1: Download and then reinstall Windows Script

To download and then reinstall Windows Script, visit one of the following Microsoft Web sites, depending on the version of Windows Script that you are using and the operating system that the computer is running.

Windows Script 5.7 for Windows Server 2003

The following file is available for download from the Microsoft Download Center:

Download the scripten.exe package now.

Windows Script 5.7 for Windows XP

The following file is available for download from the Microsoft Download Center:

Download the scripten.exe package now.

Windows Script 5.7 for Windows 2000

The following file is available for download from the Microsoft Download Center:

Download the scripten.exe package now.

Windows Script 5.6 for Windows Server 2003

The following file is available for download from the Microsoft Download Center:

Download the WindowsServer2003-Script56-KB917344-x86-enu.exe package now.

Windows Script 5.6 for Windows XP and for Windows 2000

The following file is available for download from the Microsoft Download Center:

Download the http://www.microsoft.com/downloads/details.aspx?FamilyID=c717d943-7e4b-4622-86eb-95a22b832caa&DisplayLang=en package now.

Method 2: Register the scripting components on your computer

To fix this problem, change the scripting components on your computer. To have us fix this problem for you, go to the "Fix it for me" section. If you’d rather fix this problem yourself, go to the "Let me fix it myself" section.

Fix it for me

To fix this problem automatically, click the Fix this problem link. Then click Run in the File Download dialog box, and follow the steps in this wizard.

Fix this problem
Microsoft Fix it 50181

Note This wizard may be in English only; however, the automatic fix also works for other language versions of Windows.

Note If you are not on the computer that has the problem, you can save the automatic fix to a flash drive or a CD so that you can run it on the computer that has the problem.

Now go to the "Did this fix the problem?" section.

Let me fix it myself

To manually register the scripting components on your computer, use one of the following sets of steps, as appropriate for your situation.

You are running a 32-bit version of the Windows operating system

1. Click Start, click Run, type cmd, and then click OK.
2. Type regsvr32 %systemroot%\system32\vbscript.dll, and then press ENTER.
3. Type regsvr32 %systemroot%\system32\jscript.dll, and then press ENTER.
4. Type regsvr32 %systemroot%\system32\dispex.dll, and then press ENTER.
5. Type regsvr32 %systemroot%\system32\scrobj.dll, and then press ENTER.
6. Type regsvr32 %systemroot%\system32\scrrun.dll, and then press ENTER.
7. Type regsvr32 %systemroot%\system32\wshext.dll, and then press ENTER.
8. Type regsvr32 %systemroot%\system32\wshom.ocx, and then press ENTER.

You are running a 64-bit version of the Windows operating system, and you receive the error message that is mentioned in the "Symptoms" section while you are using the 64-bit scripting components

1. Click Start, click Run, type cmd, and then click OK.
2. Type %systemroot%\system32\regsvr32 %systemroot%\system32\vbscript.dll, and then press ENTER.
3. Type %systemroot%\system32\regsvr32 %systemroot%\system32\jscript.dll, and then press ENTER.
4. Type %systemroot%\system32\regsvr32 %systemroot%\system32\dispex.dll, and then press ENTER.
5. Type %systemroot%\system32\regsvr32 %systemroot%\system32\scrobj.dll, and then press ENTER.
6. Type %systemroot%\system32\regsvr32 %systemroot%\system32\scrrun.dll, and then press ENTER.
7. Type %systemroot%\system32\regsvr32 %systemroot%\system32\wshext.dll, and then press ENTER.
8. Type %systemroot%\system32\regsvr32 %systemroot%\system32\wshom.ocx, and then press ENTER.

You are running a 64-bit version of the Windows operating system, and you receive the error message that is mentioned in the "Symptoms" section while you are using the 32-bit scripting components

1. Click Start, click Run, type cmd, and then click OK.
2. Type %systemroot%\syswow64\regsvr32 %systemroot%\syswow64\vbscript.dll, and then press ENTER.
3. Type %systemroot%\syswow64\regsvr32 %systemroot%\syswow64\jscript.dll, and then press ENTER.
4. Type %systemroot%\syswow64\regsvr32 %systemroot%\syswow64\dispex.dll, and then press ENTER.
5. Type %systemroot%\syswow64\regsvr32 %systemroot%\syswow64\scrobj.dll, and then press ENTER.
6. Type %systemroot%\syswow64\regsvr32 %systemroot%\syswow64\scrrun.dll, and then press ENTER.
7. Type %systemroot%\syswow64\regsvr32 %systemroot%\syswow64\wshext.dll, and then press ENTER.
8. Type %systemroot%\syswow64\regsvr32 %systemroot%\syswow64\wshom.ocx, and then press ENTER.

Did this fix the problem?

Check whether the problem is fixed. If the problem is fixed, you are finished with this article. If the problem is not fixed, you cancontact support.

Terminal Services Error 1075 – the dependency does not exist or has been marked for deletion

One one of Windows box I got the following error:

1075 - the dependency does not exist or has been marked for deletion

So how do You fix this error? The solution is simple, but you need to reboot the box:

To fix the 1075 error

Login to your windows box.

Open the control panel

Install MS Terminal Services and reboot the server. This make sure that all the systems files got installed and working fine.

After reboot, again open the control panel

Uninstall MS Terminal Services. For Windows Server 2003, the MS Terminal Services option is not required for remote administration.

Open up regedit and verify that the entries for "\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService" has the following entry:

DependOnService               REG_MULTI_SZ         RPCSS

If you found another "Depend" entry, just delete it.

Finally, reboot the server.

How to troubleshoot startup problems in Windows Server 2003

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

A successful Windows startup includes the following phases:

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

If a problem occurs during any of these phases, Windows may not start correctly, and you may experience the following problems:

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

If a startup problem occurs after you click Microsoft Windows Server 2003 on either the boot loader menu, or when you receive the "Please select the operating system to start" message, files that the operating system needs may be missing or damaged. Windows provides several options that you can use to troubleshoot this issue, including safe mode, the Recovery Console, and an Automated System Recovery. 

How to start the computer by using the last known good configuration

If the startup problem occurs immediately after you make a change to the computer (for example, after you install a new driver), try to start the computer by using the Last Known Good Configuration feature. 

Click here to show/hide solution 

How to start the computer in safe mode

When you start the computer in safe mode, Windows loads only the drivers and computer services that you need. You can use safe mode when you have to identify and resolve problems that are caused by faulty drivers, programs, or services that start automatically. 

Click here to show/hide solution

Use Event Viewer to identify the cause of the startup problem

View the event logs in Event Viewer for information that can help you identify and diagnose the cause of the startup problem. To view events that are recorded in the event logs, follow these steps. Click here to show/hide solution

Use System Information to identify the cause of the startup problem

The System Information tool displays a comprehensive view of the computer's hardware, the system components, and the software environment. Use this tool to help identify possible problem devices and device conflicts. To do this, follow these steps. Click here to show/hide solution

View the safe mode boot log file

To troubleshoot startup issues, view the Ntbtlog.txt boot log file, and then make a note of the drivers and services that did not load when you started your computer in safe mode. Click here to show/hide solution 

Use Device Manager to identify the cause of the startup problem

Device Manager displays a graphical view of the hardware that is installed on your computer. Use this tool to resolve any possible device conflicts or to identify incompatible devices that may be the cause of the startup problem. 

To start Device Manager, follow these steps. Click here to show/hide solution

How to use System Configuration Utility

System Configuration Utility (Msconfig.exe) automates the routine troubleshooting steps that Microsoft Support technicians use when they diagnose Windows configuration issues. You can use this tool to change the system configuration and troubleshoot the problem by using a process-of-elimination method. Click here to show/hide solution 

Create a clean environment for troubleshooting

To create a clean environment for troubleshooting, follow these steps. Click here to show/hide solution

Isolate problems by using system startup options

To isolate problems by using System Startup options, follow these steps. Click here to show/hide solution

Isolate problems by using Selective Startup options

To isolate problems by using the Selective Startup options, follow these steps. Click here to show/hide solution

Isolate problems by using the Startup tab

The Startup tab lists items that load at startup from the Startup group, Win.ini load= and run=, and the registry. To isolate problems by using the Startup tab, follow these steps. Click here to show/hide solution

Troubleshoot System Services

To troubleshoot System Services, follow these steps. Click here to show/hide solution

Troubleshoot the System.ini file

To troubleshoot the System.ini file, follow these steps. Click here to show/hide solution

Troubleshoot the Win.ini file

To troubleshoot the Win.ini file, follow these steps. Click here to show/hide solution

Troubleshoot the Boot.ini file

Only system administrators and advanced users should try to change the Boot.ini file. Steps for troubleshooting Boot.ini are beyond the scope of this article. 

For more information, search the Microsoft Knowledge Base. To do this, go to the Microsoft Support website.

Reset System Configuration Utility to normal startup

 To reset System Configuration Utility to normal startup, follow these steps. Click here to show/hide solution

Use the Windows Recovery Console

The Recovery Console is a command-line tool that you can use to repair Windows if the computer does not start correctly. You can start the Recovery Console from the Windows Server 2003 CD or at startup if the Recovery Console was previously installed on your computer. Use the Recovery Console if the Last Known Good Configuration startup option was not successful, and you can't start the computer in safe mode. We recommend that you use the Recovery Console method only if you are an advanced user who can use basic commands to identify and locate problem drivers and files. 
To use Recovery Console, follow these steps. Click here to show/hide solution

Confirm that your hard disk or file system is not damaged

To confirm that your hard disk or file system is not damaged, start your computer from the Windows Server 2003 CD, start the Recovery Console, and then use the Chkdsk command prompt utility. This may resolve your problem. Click here to show/hide solution

How to use Automated System Recovery

 To recover from a system failure by using Automated System Recovery (ASR), follow these steps. Click here to show/hide solution

Create an ASR disk set by using Backup

 To use ASR, you must have an ASR disk set. To create an ASR disk set, follow these steps. Click here to show/hide solution

How to repair your installation of Windows

You may be able to repair a damaged Windows Server 2003 installation by running Windows Setup from the Windows CD.

To repair your installation of Windows, follow these steps. Click here to show/hide solution

How to use the Microsoft Support website to find a solution

If you cannot resolve the problem by following the steps in this article, you can use the Microsoft Support website to find a solution to your problem. The following list describes some of the services that the Microsoft Support website provides:

• Searchable Knowledge Base - Search technical support information and self-help tools for Microsoft products.
• Frequently Asked Questions - View product-specific frequently asked questions and support highlights.
• Software and Updates - Find software and updates on the Download Center.
• Other Support Options - Ask a support question by using the web or telephone Microsoft Support.

How To Troubleshoot Shutdown Problems in Windows Server 2003

This article describes general procedures that you can use to troubleshoot shutdown problems in Windows Server 2003. 

When Windows shuts down, messages are sent to the devices, system services, and programs that are installed on the computer. These messages announce that Windows is preparing to shut down. The operating system waits for responses from programs that are running to make sure that the programs save unsaved data to the hard disk and shut down correctly. Each device, service, and program that is running typically responds to the shutdown message with a message that states that the program can be closed. 

You may experience one or more of the following symptoms when you try to turn off the computer:

• The computer stops responding (hangs). When this symptom occurs, a black screen may be displayed.
• The computer does not turn off when you receive the message that states that it is safe to turn off your computer.
• You receive an error message.

Typical causes of shutdown problems include the following:

• Faulty or incompatible device drivers.
• System services that either do not respond correctly or send busy request messages to the system.
• Faulty or incompatible programs.

How to Troubleshoot Shutdown Problems in Windows Server 2003

To troubleshoot shutdown problems and to isolate the cause of the incorrect shutdown behavior, use the following methods:

• Use Task Manager to identify the cause of the shutdown behavior.
• Undo any recent changes to the computer.
• Use safe mode to identify the cause of the shutdown behavior.
• Confirm that the computer's complementary metal oxide semiconductor (CMOS) and basic input/output system (BIOS) settings are correct.

How to Use Task Manager to Identify the Cause of the Shutdown Behavior

Use Task Manager to determine the programs that are currently running on the computer. For each program that is listed in Task Manager, manually quit the program, and then shut down and restart the computer to test if the shutdown problem is resolved. To do this, follow the procedure that is described in this section. 

NOTE: It is possible that not all programs that are currently running on the computer are listed on the Applications tab of Task Manager.

1. Press CTRL+ALT+DELETE, and then click Task Manager.
2. Click the Applications tab.
3. In the Task column, click the program that you want to quit, and then click End Task.
4. Quit Task Manager.
5. Turn off the computer.

How to Undo Any Recent Changes to the Computer

If the shutdown behavior occurs immediately after you make a change to the computer (for example, you install or upgrade a program, a service, or hardware that has device drivers), undo the last change that you made. For example, remove either the last driver or the last program that you installed, and then shut down and restart the computer to test whether the computer shuts down correctly. 

How to Use Safe Mode to Identify the Cause of the Shutdown Behavior

When you start your computer in safe mode, only a minimal set of necessary drivers and services is loaded. Safe mode is a useful diagnostic tool to use when you want to identify and resolve problems that are caused by faulty drivers, programs, or services that start automatically. 

To determine if the computer shuts down correctly in safe mode:

1. Restart the computer.
2. When are prompted to select the operating system to start, press F8.
3. On the Windows Advanced Option menu, use the ARROW keys to select Safe Mode, and then press ENTER.
4. If you are using a dual-boot computer or a multiple-boot computer, select Microsoft Windows Server 2003 from the list that is displayed, and then press ENTER.
5. After the computer starts in safe mode, turn off the computer.
   
   If the computer shuts down correctly when it is in safe mode, repeat steps 1 through 4 to restart the computer in safe mode, and then go to step 6 and follow the remaining steps of this procedure to troubleshoot and identify the cause of the shutdown problem.
6. View the boot log file, Ntbtlog.txt, and then make a note of the devices and services that did not load when you started your computer in safe mode.
   
   The Ntbtlog.txt file is located in the %SystemRoot% folder (by default, this is the Windows folder). You can use Notepad to open and view the file. The Ntbtlog.txt file lists devices and services that load (and do not load) when you start your computer in safe mode.
   
   NOTE: If there are third-party drivers or services that run when your computer is in normal mode but do not run when your computer is in safe mode, the third-party drivers or services may be the cause of the incorrect shutdown behavior.
7. Restart the computer in normal mode, and then do one of the following:
   • Remove the drivers for each of the drivers and services that you identified in the Ntbtlog.txt file to be possible causes of the incorrect shutdown behavior.
   • Stop the services or disable the services one at a time.
   You can use Device Manager to remove or disable devices and their drivers.
   For additional information about how to manage devices by using Device Manager, click the article numbers below to view the articles in the Microsoft Knowledge Base:
   199276 How to Manage Devices in Windows
   244601 How to Troubleshoot Unknown Devices Listed in Device Manager
   125174 Explanation of Error Codes Generated by Device Manager
   323423 Configure Devices Using Device Manager in Windows Server 2003
8. Turn off the computer to test whether the shutdown problem is resolved.
9. After you identify the problem service or driver, either reinstall the service or the driver if you suspect that a file is damaged or contact the manufacturer to report the behavior and to obtain information about possible updates that you can use to resolve the shutdown behavior.

For additional information about how to troubleshoot shutdown problems by using safe mode, click the article number below to view the article in the Microsoft Knowledge Base:

266169 How to Troubleshoot Problems with Standby Mode, Hibernate Mode, and Shutting Down Your Computer in Windows 2000

How to Confirm that the Computer's CMOS/BIOS Settings Are Correct

WARNING: This procedure may involve changing your computer's CMOS settings and changing the BIOS. Incorrect changes to the BIOS of your computer can result in serious problems. Change the computer's CMOS settings at your own risk. 

Incorrect or damaged CMOS and BIOS settings can cause startup and shutdown problems. For information about the correct CMOS and BIOS settings for your computer and how to check and change these settings, see the computer documentation or contact the manufacturer of your computer. To confirm that the computer's BIOS is current, contact the computer manufacturer to inquire about the latest BIOS update available for your computer. 

How to Use a Parallel Installation to Identify the Cause of the Shutdown Behavior

To use a parallel installation to troubleshoot shutdown behavior:

1. Install a new copy of Windows Server 2003 to a separate partition on the computer (create a parallel installation), and then install drivers and programs one at a time on the parallel installation.
2. Shut down and restart the computer between each program installation and note if the incorrect shutdown behavior occurs.
   
   If the behavior occurs, the last driver or the program that you installed may be the cause of the incorrect shutdown behavior.
3. Either remove or update the driver or the program from the original installation, and then test Windows for correct shutdown.
   
   If the problem is resolved, remove the parallel Windows installation.

The logon screen turns black after you press CTRL+ALT+DELETE to log on to a Microsoft Windows Server 2003-based computer

SYMPTOMS

After you press CTRL+ALT+DELETE to log on to a Microsoft Windows Server 2003-based computer, the logon screen turns black. Although you cannot see what you are typing, you can successfully log on to the Windows Server 2003-based computer. Then, after you successfully log on, the screen becomes visible.

Note This symptom may occur on both the terminal server sessions and the local console. Additionally, this symptom occurs even if you start the computer in Safe mode.

CAUSE

This issue occurs if all the values under the following registry subkey are set to "0 0 0":

HKEY_USERS\.Default\Control Panel\Colors

Note The value data "0 0 0" means black.

WORKAROUND

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 How to back up and restore the registry in Windows

To work around this issue, perform the following procedures.

Export the registry subkey from another Windows Server 2003-based computer

1.       Click Start, point to Run, type regedit in the Open box, and then click OK.

2.       Locate the following registry subkey:

HKEY_USERS\.Default\Control Panel\Colors

3.       Right-click the Colors registry subkey, and then click Export.

4.       In the File name box, type a name for the file.

5.       Note the location where you will save the file, and then click Save.

Import the registry subkey into the affected computer

1.       Click Start, point to Run, type regedit in the Open box, and then click OK.

2.       On the File menu, click Import.

3.       Double-click the .reg file that you want to import.

4.       Quit Registry Editor, and then restart the computer.

MORE INFORMATION

The value data for color registry values are in the xxx yyy zzz format, where xxx yyy zzz represents the red-green-blue (RGB) values for a color. For example, 0 0 0 is solid black and 255 255 255 is solid white. The following table lists the default values for the HKEY_USERS\.Default\Control Panel\Colors registry subkey.

Value name	Value data
ActiveBorder	212 208 200
ActiveTitle	10 36 106
AppWorkSpace	128 128 128
Background	102 111 116
ButtonAlternateFace	181 181 181
ButtonDkShadow	64 64 64
ButtonFace	212 208 200
ButtonHilight	255 255 255
ButtonLight	212 208 200
ButtonShadow	128 128 128
ButtonText	0 0 0
GradientActiveTitle	166 202 240
GradientInactiveTitle	192 192 192
GrayText	128 128 128
Hilight	10 36 106
HilightText	255 255 255
HotTrackingColor	0 0 128
InactiveBorder	212 208 200
InactiveTitle	128 128 128
InactiveTitleText	212 208 200
InfoText	0 0 0
InfoWindow	255 255 225
Menu	212 208 200
Menubar	212 208 200
MenuHilight	210 210 255
MenuText	0 0 0
Scrollbar	212 208 200
TitleText	255 255 255
Window	255 255 255
WindowFrame	0 0 0
WindowText	0 0 0

Note:- Second solution :- Install VGA Drivers If VGA already install in your pc then again install it.