mcts training kit 70 - 685 Windows 7 Enterprise Desktop Support Technician phần 8 pps

452 APPENDIX C Confi guring Startup and Troubleshooting Startup Issues The Windows Boot Loader uses the control set identifi ed by the \Select\Default value unless you choose the Last Known Good Confi guration from the Advanced Boot Options menu. The kernel creates the registry key HKEY_LOCAL_MACHINE\HARDWARE, which contains the hardware data collected at system startup. Windows supports an extensive set of devices, with additional drivers not on the Windows operating system DVD provided by hardware manufacturers. Drivers are kernel-mode features required by devices to function within an operating system. Services are features that support operating system and application functions and act as network servers. Services can run in a different context than user applications and typically do not offer many user-confi gurable options. For example, the Print Spooler service does not require a user to be logged on to run and functions independently of the user who is logged on to the system. Drivers generally communicate directly with hardware devices, whereas services usually communicate with hardware through drivers. Driver and service fi les are typically stored in the %SystemRoot%\ System32 and %SystemRoot%\System32\Drivers folders and use .exe, .sys, or .dll fi le name extensions. Drivers are also services. Therefore, during kernel initialization, the Windows Boot Loader and Ntoskrnl use the information stored in the HKEY_LOCAL_MACHINE\SYSTEM\ CurrentControlSet\Services\Servicename registry subkeys to determine both the drivers and services to load. In the Servicename subkeys, the Start entry specifi es when to start the service. For example, the Windows Boot Loader loads all drivers for which Start is 0, such as device drivers for hard disk controllers. After execution is transferred to the kernel, the kernel loads drivers and services for which Start is 1. Table C-1 lists the values (in decimal) for the registry entry Start. Boot drivers (those for which Start is 0) and fi le system drivers are always loaded regardless of the value of Start because they are required to start Windows. TABLE C-1 Values for the Start Registry Entry VALUE START TYPE VALUE DESCRIPTIONS FOR START ENTRIES 0Boot Specifi es a driver that is loaded (but not started) by the boot loader. If no errors occur, the driver is started during kernel initialization prior to any non-boot drivers being loaded. 1SystemSpecifi es a driver that loads and starts during kernel initialization after drivers with a Start value of 0 have been started. 2Auto loadSpecifi es a driver or service that is initialized at system startup by Session Manager (Smss.exe) or the Services Controller (Services.exe). 3 Load on demand Specifi es a driver or service that the Service Control Manager (SCM) will start only on demand. These drivers have to be started manually by calling a Win32 SCM application programming interface (API), such as the Services snap-in. Z03A627093.indd 452Z03A627093.indd 452 2/4/2010 11:04:58 AM2/4/2010 11:04:58 AM Understanding the Startup Process APPENDIX C 453 VALUE START TYPE VALUE DESCRIPTIONS FOR START ENTRIES 4DisabledSpecifi es a disabled (not started) driver or service. 5Delayed start Specifi es that less-critical services will start shortly after startup to allow the operating system to be responsive to the user sooner. This start type was fi rst introduced in Windows Vista. Table C-2 lists some of the values (in decimal) for the Type registry entry. TABLE C-2 Type Registry Values VALUE VALUE DESCRIPTIONS FOR TYPE ENTRIES 1Specifi es a kernel device driver 2Specifi es a kernel-mode fi le system driver (also a kernel device driver) 4Specifi es arguments passed to an adapter 8Specifi es a fi le system driver, such as a fi le system recognizer driver 16 Specifi es a service that obeys the service control protocol, runs within a process that hosts only one service, and can be started by the Services Controller 32 Specifi es a service that runs in a process that hosts multiple services 256 Specifi es a service that is allowed to display windows on the console and receive user input Some drivers and services require that conditions, also known as dependencies, be met. You can fi nd dependencies listed under the DependOnGroup and DependOnService entries in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Servicename subkey for each service or driver. For more information about using dependencies to prevent or delay a driver or service from starting, see the section titled “How to Temporarily Disable a Service” later in this appendix. The Services subkey also contains information that affects how drivers and services are loaded. Table C-3 lists some of these other entries. TABLE C-3 Other Registry Entries in the Servicename Subkeys ENTRY DESCRIPTION DependOnGroup At least one item from this group must start before this service is loaded. DependOnService Lists the specifi c services that must load before this service loads. DisplayName Describes the feature. Z03A627093.indd 453Z03A627093.indd 453 2/4/2010 11:04:58 AM2/4/2010 11:04:58 AM 454 APPENDIX C Confi guring Startup and Troubleshooting Startup Issues ENTRY DESCRIPTION ErrorControl Controls whether a driver error requires the system to use the LastKnownGood control set or to display a Stop message. If the value is 0x0 (Ignore, No Error Is Reported), it does not display a warning and proceeds with startup. If the value is 0x1 (Normal, Error Reported), it records the event to the System Event Log and displays a warning message but proceeds with startup. If the value is 0x2 (Severe), it records the event to the System Event Log, uses the LastKnownGood settings, restarts the system, and proceeds with startup. If the value is 0x3 (Critical), it records the event to the System Event Log, uses the LastKnownGood settings, and restarts the system. If the LastKnownGood settings are already in use, it displays a Stop message. Group Designates the group that the driver or service belongs to. This allows related drivers or services to start together (for example, fi le system drivers). The registry entry List in the subkey HKEY_LOCAL_MACHINE\ SYSTEM \CurrentControlSet\Control\ServiceGroupOrder specifi es the group startup order. ImagePath Identifi es the path and fi le name of the driver or service if the ImagePath entry is present. ObjectName Specifi es an object name. If the Type entry specifi es a service, it represents the account name that the service uses to log on when it runs. Tag Designates the order in which a driver starts within a driver group. Session Manager After all entries that have Boot and Startup data types are processed, the kernel starts the Session Manager (Smss.exe), a user process that continues to run until the operating system is shut down. The Session Manager performs important initialization functions, such as: ■ Creating system environment variables. ■ Starting the kernel-mode portion of the Win32 subsystem (implemented by %SystemRoot%\System32\Win32k.sys), which causes Windows to switch from text mode (used to display the Windows Boot Manager menu) to graphics mode (used to display the Starting Windows logo). Windows-based applications run in the Windows subsystem. This environment allows applications to access operating system functions, such as displaying information to the screen. Z03A627093.indd 454Z03A627093.indd 454 2/4/2010 11:04:58 AM2/4/2010 11:04:58 AM Understanding the Startup Process APPENDIX C 455 ■ Starting the user-mode portion of the Win32 subsystem (implemented by %SystemRoot%\System32\Csrss.exe). The applications that use the Windows subsystem are user-mode processes; they do not have direct access to hardware or device drivers. Instead, they have to access Windows APIs to gain indirect access to hardware. This allows Windows to control direct hardware access, improving security and reliability. User-mode processes run at a lower priority than kernel-mode processes. When the operating system needs more memory, it can page to disk the memory used by user-mode processes. ■ Starting the Logon Manager (%SystemRoot%\System32\Winlogon.exe). ■ Creating additional virtual memory paging fi les. ■ Performing delayed rename operations for fi les specifi ed by the registry entry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\ PendingFileRenameOperations. For example, you might be prompted to restart the computer after installing a new driver or application so that Windows can replace fi les that are currently in use. Session Manager searches the registry for service information contained in the following subkeys: ■ HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager contains a list of commands to run before loading services. The Autochk.exe tool is specifi ed by the value of the registry entry BootExecute and virtual memory (paging fi le) settings stored in the Memory Management subkey. Autochk, which is a version of the Chkdsk tool, runs at startup if the operating system detects a fi le system problem that requires repair before completing the startup process. ■ HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\ SubSystems stores a list of available subsystems. For example, Csrss.exe contains the user-mode portion of the Windows subsystem. If startup fails during the kernel loading phase after another operating system was installed on the computer, the cause of the problem is likely an incompatible boot loader. Boot loaders installed by versions of Windows prior to Windows Vista cannot be used to start Windows Vista or Windows 7. Use System Recovery to replace startup fi les with Windows startup fi les. Otherwise, if startup fails during the kernel loading phase, use boot logging to isolate the failing feature. Then use safe mode to disable problematic features (if possible) or use System Recovery to replace problematic fi les. For more information, see the section titled “Startup Troubleshooting Before the Starting Windows Logo Appears” later in this appendix. If you experience a Stop error during this phase, use the information provided by the Stop message to isolate the failing feature. For more information about troubleshooting Stop errors, see Appendix F, “Troubleshooting Stop Messages.” Z03A627093.indd 455Z03A627093.indd 455 2/4/2010 11:04:58 AM2/4/2010 11:04:58 AM 456 APPENDIX C Confi guring Startup and Troubleshooting Startup Issues Logon Phase The Windows subsystem starts Winlogon.exe, a system service that enables you to log on and log off. Winlogon.exe then does the following: ■ Starts the Services subsystem (Services.exe), also known as the SCM. The SCM initializes services that the registry entry Start designates as Autoload in the registry subkey HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Servicename. ■ Starts the Local Security Authority (LSA) process (Lsass.exe). ■ Parses the Ctrl+Alt+Delete key combination at the Begin Logon prompt (if the computer is part of an AD DS domain). The logon user interface (LogonUI) feature and the credential provider (which can be the standard credential provider or a third-party credential provider) collect the user name and password (or other credentials) and pass this information securely to the LSA for authentication. If the user supplied valid credentials, access is granted by using either the default Kerberos V 5 authentication protocol or Windows NT LAN Manager (NTLM). Winlogon initializes security and authentication features while PnP initializes auto-load services and drivers. After the user logs on, the control set referenced by the registry entry LastKnownGood (located in HKLM\SYSTEM\Select) is updated with the contents in the CurrentControlSet subkey. By default, Winlogon then starts Userinit.exe and the Windows Explorer shell. Userinit may then start other processes, including: ■ Group Policy settings take effect Group Policy settings that apply to the user and computer take effect. ■ Startup programs run When not overridden by Group Policy settings, Windows starts logon scripts, startup programs, and services referenced in the following registry subkeys and fi le system folders: •• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Runonce •• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\ Explorer\Run •• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run •• HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\ Windows\Run •• HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run •• HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\RunOnce •• SystemDrive\Documents and Settings\All Users\Start Menu\Programs\Startup •• SystemDrive\Documents and Settings\username\Start Menu\Programs\Startup Several applications might be confi gured to start by default after you install Windows, including Windows Defender. Computer manufacturers or IT departments might confi gure other startup applications. Windows startup is not complete until a user successfully logs on to the computer. If startup fails during the logon phase, you have a problem with a service or application Z03A627093.indd 456Z03A627093.indd 456 2/4/2010 11:04:58 AM2/4/2010 11:04:58 AM Important Startup Files APPENDIX C 457 confi gured to start automatically. For troubleshooting information, see the section titled “How to Temporarily Disable Startup Applications and Processes” later in this appendix. If you experience a Stop error during this phase, use the information provided by the Stop message to isolate the failing feature. For more information about troubleshooting Stop errors, see Appendix F. Important Startup Files For Windows to start, the system and boot partitions must contain the fi les listed in Table C-4. TABLE C-4 Windows Startup Files FILE NAME DISK LOCATION DESCRIPTION BootMgr Root of the system partition The Windows Boot Manager. WinLoad %SystemRoot%\System32 The Windows Boot Loader. BCD \Boot A fi le that specifi es the paths to operating system installations and other information required for Windows to start. Ntoskrnl.exe %SystemRoot%\System32 The core (also called the kernel) of the Windows operating system. Code that runs as part of the kernel does so in privileged processor mode and has direct access to system data and hardware. Hal.dll %SystemRoot%\System32 The HAL dynamic-link library (DLL) fi le. The HAL abstracts low-level hardware details from the operating system and provides a common programming interface to devices of the same type (such as video adapters). Smss.exe %SystemRoot%\System32 The Session Manager fi le. Session Manager is a user-mode process created by the kernel during startup. It handles critical startup tasks including creating page fi les and performing delayed fi le rename and delete operations. Csrss.exe %SystemRoot%\System32 The Win32 Subsystem fi le. The Win32 Subsystem is started by Session Manager and is required by Windows to function. Winlogon.exe %SystemRoot%\System32 The Logon Process fi le, which handles user logon requests and intercepts the Ctrl+Alt+Delete logon key sequence. The Logon Process is started by Session Manager. This is a required feature. Z03A627093.indd 457Z03A627093.indd 457 2/4/2010 11:04:59 AM2/4/2010 11:04:59 AM 458 APPENDIX C Confi guring Startup and Troubleshooting Startup Issues FILE NAME DISK LOCATION DESCRIPTION Services.exe %SystemRoot%\System32 The Service Control Manager is responsible for starting and stopping services and is a required feature of Windows. Lsass.exe %SystemRoot%\System32 The Local Security Authentication Server process is called by the Logon Process when authenticating users and is a required feature. System registry fi le %SystemRoot%\System32\ Confi g\System The fi le that contains data used to create the registry key HKEY_LOCAL_MACHINE\ SYSTEM. This key contains information that the operating system requires to start devices and system services. Device drivers %SystemRoot%\System32\ Drivers Driver fi les in this folder are for hardware devices, such as keyboard, mouse, and video. In Table C-4, the term %SystemRoot% is one of many environment variables used to associate string values, such as folder or fi le paths, to variables that Windows applications and services use. For example, by using environment variables, scripts can run without modifi cation on computers that have different confi gurations. To obtain a list of environment variables that you can use for troubleshooting, type set at the Windows command prompt. How to Confi gure Startup Settings Windows Vista and Windows 7 enable administrators to confi gure startup settings using many of the same graphical tools that Windows XP provides. Command-line tools for confi guring startup tools have been replaced with new tools, however, and you can no longer directly edit the startup confi guration fi le (formerly the Boot.ini fi le). The following sections describe several techniques for confi guring startup settings. How to Use the Startup And Recovery Dialog Box The simplest way to edit the BCD registry fi le is to use the Startup And Recovery dialog box. To use the Startup And Recovery dialog box to change the default operating system, follow these steps: 1. Click Start, right-click Computer, and then click Properties. 2. Click Advanced System Settings. 3. In Startup And Recovery, click Settings. Z03A627093.indd 458Z03A627093.indd 458 2/4/2010 11:04:59 AM2/4/2010 11:04:59 AM How to Confi gure Startup Settings APPENDIX C 459 4. Click the Default Operating System list and then click the operating system that you want to boot by default. 5. Click OK twice. The default operating system will automatically load the next time you start the computer. How to Use the System Confi guration Tool The System Confi guration tool offers more advanced control over startup settings, including some ability to confi gure the BCD registry fi le. This tool is specifi cally designed for troubleshooting, and you can use it to easily undo changes that you have made to the computer’s confi guration (even after restarting the computer). If you make changes with the System Confi guration tool, it will remind users logging on that settings have been temporarily changed—thus reducing the likelihood that settings will not be reset after the troubleshooting process has been completed. Some common tasks for the System Confi guration tool include: ■ Temporarily disabling startup applications to isolate the cause of a post-logon problem. ■ Temporarily disabling automatic services to isolate the cause of a pre-logon or post-logon problem. ■ Permanently or temporarily confi guring the BCD registry fi le. ■ Confi guring a normal, diagnostic, or selective startup for Windows Vista. To use the System Confi guration tool, click Start, type Msconfi g, and then press Enter. The System Confi guration tool provides fi ve tabs: ■ General Use this tab to change the next startup mode. Normal Startup loads all device drivers and services. Diagnostic Startup is useful for troubleshooting startup problems, and it loads only basic devices and services. Use Selective Startup to specify whether you want to load system services or startup items. ■ Boot Use this tab to confi gure the BCD registry fi le and startup settings. You can remove startup operating system options, set the default operating system, confi gure advanced settings for an operating system (including number of processors, maximum memory, and debug settings), and confi gure Windows for Safe Boot or to boot without a graphical interface. ■ Services Use this tab to change the startup settings for a service temporarily. This is an excellent way to determine whether an automatic service is causing startup problems. After you disable a service, restart your computer and determine whether the problem still exists. If it does, you have eliminated one potential cause of the problem. You can then use this tab to re-enable the service, disable another service, and repeat the process. To disable services permanently, use the Services console. Z03A627093.indd 459Z03A627093.indd 459 2/4/2010 11:04:59 AM2/4/2010 11:04:59 AM 460 APPENDIX C Confi guring Startup and Troubleshooting Startup Issues ■ Startup Lists applications that are confi gured to start automatically. This is the best way to disable applications temporarily during troubleshooting because you can easily re-enable them later using the same tool. You should not use the System Confi guration tool to permanently remove startup applications, however, because the System Confi guration tool is designed to enable you to easily undo changes. Instead, you should manually remove the application. ■ Tools Provides links to other tools that you can start. NOTE The Win.ini, System.ini, and Boot.ini tabs do not appear in the System Confi guration tool because those fi les have not been used since Windows XP. Because the System Confi guration tool is a graphical tool, it is primarily useful when Windows is booting successfully. How to Use BCDEdit The BCDEdit command-line tool provides you with almost unlimited control over the BCD registry fi le and confi guration settings. NOTE If you have a computer with both Windows XP and Windows 7 installed and you want to modify the BCD registry fi le from Windows XP, you can run BCDEdit from Windows XP by starting it directly from the Windows\System32 folder of your Windows 7 installation. Although this might be useful in some multiboot confi gurations, typically, you should run BCDEdit from the System Recovery command prompt if you cannot load Windows 7. You must use administrative credentials to run BCDEdit from within Windows 7. To do this, follow these steps: 1. Click Start, click All Programs, and then click Accessories. 2. Right-click Command Prompt and then click Run As Administrator. To view detailed information about using BCDEdit, run BCDEdit /? from a command prompt. The following sections describe how to perform specifi c tasks with BCDEdit. How to Interpret BCDEdit Output You can view settings currently defi ned in your BCD registry fi le by using the bcdedit /enum command. Optionally, you can follow the command with one of the following parameters to change which entries are displayed: ■ Active The default setting that is displayed if you run bcdedit /enum without any additional parameters. Displays all entries in the Boot Manager display order. ■ Firmware Displays all fi rmware applications. ■ Bootapp Displays all boot environment applications. NO T E The Win.ini, System.ini, and Boot.ini tabs do not appear in the System Confi guration E tool because those fi les have not been used since Windows XP. N O T E If you have a computer with both Windows XP and Windows 7 installed and E y ou want to modi f y the BCD registry fi le f rom Windows XP, you can run BCDEdit f rom Windows XP b y startin g it directl y from the Windows\S y stem32 folder of y our Windows 7 installation. Although this might be useful in some multiboot confi gurations, typically, y ou should run BCDEdit f rom the S y stem Recover y command prompt i f y ou cannot load W i ndows 7 . Z03A627093.indd 460Z03A627093.indd 460 2/4/2010 11:04:59 AM2/4/2010 11:04:59 AM How to Confi gure Startup Settings APPENDIX C 461 ■ Osloader Displays all operating system entries. ■ Resume Displays all resume from hibernation entries. ■ Inherit Displays all inherit entries. ■ All Displays all entries. For example, to view the startup entry used to resume from hibernation, run the following command at an administrative command prompt. bcdedit /enum resume Similarly, to view all startup entries, use the following command. bcdedit /enum all How to Back Up and Restore Settings Making changes to your BCD registry fi le can render your computer unbootable. Therefore, before making changes to your BCD registry fi le, you should make a backup copy, have a bootable Windows DVD available, and be prepared to restore the original BCD registry fi le. To make a backup of your current BCD registry, call the BCDEdit /export command, as shown here. bcdedit /export backupbcd.bcd Later, you can restore your original BCD registry fi le by calling the BCDEdit /import command, as shown here. bcdedit /import backupbcd.bcd NOTE The fi le name and extension you use are not signifi cant. If Windows is unbootable, follow the instructions in the section titled “The Process of Troubleshooting Startup” later in this appendix. How to Change the Default Operating System Entry To view the current default operating system entry, run the following command and look for the default line. bcdedit /enum {bootmgr} Windows Boot Manager identifier {bootmgr} device partition=\Device\HarddiskVolume1 description Windows Boot Manager locale en-US inherit {globalsettings} N OT E The fi le name and extension you use are not signifi cant. E Wi n d ows Boot Manager identifier {bootmgr} d ev i ce part i t i on= \ Dev i ce \ Har ddi s k Vo l ume1 d escription Windows Boot Mana g er locale en- US i n h er i t { g l o b a l sett i ngs } Z03A627093.indd 461Z03A627093.indd 461 2/4/2010 11:04:59 AM2/4/2010 11:04:59 AM [...]... time-out for the boot menu, use the bcdedit /timeout seconds command, as shown here bcdedit /timeout 15 How to Change the Order of Boot Manager Menu Items To change the order of Boot Manager menu items, use the bcdedit /display command, and then list the menu item identifiers in the desired sequence, as shown in the following example bcdedit /display {current} {ntldr} {cbd 971 bf-b7b 8- 4 88 5-9 51a-fa0344f5d71}... Z03A6 270 9 3.indd 473 APPENDIX C 473 2/4/2010 11:05:01 AM For detailed information, read the section titled “How to Use BCDEdit” earlier in this appendix How to Manually Replace Files If startup files are missing or become corrupted, Windows may not be able to boot successfully Often, Windows will display an error message that shows the name of the missing file, as shown in Figure C -8 FIGURE C -8 Windows. .. earlier version of Windows 2 If Windows 7 is not installed on the active partition, you can now delete or remove the partition where Windows 7 is installed NOTE E You can follow these steps in any version of Windows If you follow these steps in Windows Vista or Windows 7, run the commands from a command prompt that has elevated user rights To do this, click Start, click Accessories, right-click the command... Windows 7 Boot Loader If you want to remove Windows 7 from a dual-boot environment that includes Windows XP or an earlier version of Windows, follow these steps: 1 Use Bootsect.exe to restore the Ntldr.exe program To do this, type the following command, where D:\ is the drive containing the Windows installation media D:\Boot\Bootsect.exe –NT52 All After the computer restarts, it does not load the Windows. .. file %WinDir%\Bootstat.dat If Windows detects that the last startup attempt was unsuccessful, it automatically displays the startup recovery menu, which provides startup options similar to the Advanced Boot Options menu, without requiring you to press F8 4 78 Z03A6 270 9 3.indd 4 78 APPENDIX C Configuring Startup and Troubleshooting Startup Issues 2/4/2010 11:05:02 AM FIGURE C-11 Use Last Known Good Configuration... Logging, as shown in Figure C-12 FIGURE C-12 Enabling boot logging can help you identify the cause of startup problems Windows starts and creates a log file at %WinDir%\Ntbtlog.txt The log file starts with the time and version information and then lists every file that is successfully loaded, as shown here Microsoft (R) Windows (R) Version 6.1 (Build 71 00) 5 27 2009 17: 57: 37. 500 Loaded driver \SystemRoot\system32\ntoskrnl.exe... registry file Manually replace startup files Reinstall Windows 7 FIGURE C-5 Follow this process to troubleshoot startup problems before logon The following sections describe each of these troubleshooting steps in more detail NOTE E After you enable Windows BitLocker, a lost encryption key can result in an unbootable computer 4 68 Z03A6 270 9 3.indd 4 68 APPENDIX C Configuring Startup and Troubleshooting Startup... list volume Volume ### Ltr Label Fs Type Size Status Info - - - - - Volume 0 Win7 NTFS Partition 63 GB Healthy Volume 1 E Windows XP NTFS Partition 91 GB Healthy Volume 2 D NTFS Partition 69 GB Healthy Volume 3 I Removable 0 B No Media Volume 4 H Removable 0 B No Media Volume 5 F LR1CFRE_EN_ UDF Partition 2 584 MB Healthy Volume 6 5 C G USBDRIVE FAT32 Partition 991 MB Healthy... Use Device Manager to upgrade, roll back, or remove failing driver FIGURE C-10 Follow this process to troubleshoot startup problems after the Starting Windows logo appears but before logon The sections that follow describe each of these steps in more detail The Process of Troubleshooting Startup Z03A6 270 9 3.indd 477 APPENDIX C 477 2/4/2010 11:05:02 AM How to Run Startup Repair Startup Repair can automatically... Restart the computer and allow Windows to start normally How to Use BootRec.exe Startup Repair can automatically recover from most BCD problems If you prefer to manually analyze and repair problems, you can use the command-line tool BootRec.exe by starting the System Recovery tools and then clicking Command Prompt in the System Recovery Options dialog box 470 Z03A6 270 9 3.indd 470 APPENDIX C Configuring Startup . {ntldr} {cbd 971 bf-b7b 8- 4 88 5-9 51a-fa0344f5d71} How to Create an Entry for Another Operating System You can use BCDEdit to create an entry for an operating system other than Windows 7. You may. Windows automatically creates d e f ault {current} r esumeobject {24a500f 3-1 2ea-11db-a536-b7db70c06ac2} di sp l ayor d er { current } toolsdisplayorder {memdia g } t i meout 30 Z03A6 270 9 3.indd. command-line tool BootRec.exe by starting the System Recovery tools and then clicking Command Prompt in the System Recovery Options dialog box. Z03A6 270 9 3.indd 470 Z03A6 270 9 3.indd 470 2/4/2010