win7引导修复（Win7 boot repair）

win7引导修复（Win7 boot repair） win7引导修复(Win7 boot repair) Windows7 boot repair I. overview of the Windows7 boot (a) terminology description Bootmgr (Windows, Boot, Manager):Windows Startup Manager BCD (Boot, Configuration, Data): start configuration data storage (two) dual partition Windows7 and single partition Windows7 1, double partition Windows7:Win7 after the installation of default occupied two primary partitions, a C (Windows folder where the disc, the first partition, the hard disk is not active) and a hidden partition (boot file where the hard disk, second partitions, real active partition). 2, Windows7: a single partition can be two Win7 partitions installed by default the merge method is: be made one, the two partition file merge to C (i.e. the first hard disk partition); the C set active partition; the implementation of the "bootsect /nt60 c:" to write the C BOOTMGR compatible boot code; the computer starts with Windows7's installation CD into the CD-ROM, select "repair computer" CD "system recovery options" began to work, and wait that completed, restart OK. (three) Windows7 boot process 1, BIOS, according to the set of storage medium order polling to the hard disk, first looking for the hard disk MBR (master boot record) and DPT (partition table), and then in accordance with the MBR and DPT information to find the system partition. 2, there are two important information in the hard disk MBR (boot code): one is the target partition, and the other is the system type". The bootsect with the /MBR parameter writes both the active tag and the system type to the MBR". 3, DPT is like a map, MBR in the "target partition" is the destination names, general partitioning tools will be the name as "active", but some software will carry out special adaptations of the names, such as a wizard will rewrite the names for their "backup / restore partition". This "backup / recovery partition is not active. 4, the active partition PBR (partition boot record, also known as OBR or DBR) also has an important message (boot code), that is, the boot file name". For WinXP, the boot file name is ntldr". For Win7, the boot file name is bootmgr". According to the BIOS MBR and DPT to find the active partition, press PBR "boot file name" for NTLDR in the root directory (BOOTMGR) file, if found will control to NTLDR (BOOTMGR), if they can not find that NTLDR (BOOTMGR) lost end guide. Bootsect with different parameters can write different boot file names to PBR". After 5 and NTLDR (BOOTMGR) take over control, search and load the startup environment file (font, file, etc.) and start the configuration file in the root directory, and then follow the instructions in the startup configuration file to proceed to the next boot. For WinXP, the startup configuration file is boot.ini in the active partition root directory, and the boot.ini is single in content. It instructs NTLDR to load the system kernel directly. For Win7, the startup configuration file is boot\BCD in the active partition root, and the BCD content is complex. It will instruct the BOOTMGR to do a number of validation of the system configuration, First, verify that the MBR in the hard disk is compatible with BOOTMGR's "system type" information, verify the consistency, then boot, verify inconsistencies, give hints, and terminate the boot. 6, Win7 failed to start, will usually have five tips: looking for equipment - active partition PBR blank, the boot process did not loaded into the BOOTMGR format by the active partition; no operating system -- not compatible with BOOTMGR MBR in the "system type" information - FDISK by /MBR 3; boot automatically start the Windows startup repair "- no problem, but the partition table is local disorder recovery caused by the wrong GHOST. The Windows boot manager 0xc000000f error - pop up no other problems, but the partition table GHOST does not restore local disorder caused by /Recovery + delete directory; the Windows boot manager 0xc000000e BOOTMGR popup error can not find the dvice option is specified in the BCD partition -- cause see "four, manual fix 0xc000000e error". 7, about GHOST: GHOST objects include the entire PBR, file systems and user data. GHOST will not change the size of the target partition, but it will cause partial disorder of the partition table. Two, Windows7 boot code maintenance (1) overview of Windows7 boot code maintenance The purpose of the maintenance of the boot code is to update the MBR of the hard disk (master boot record) and the partition's PBR (partition boot record) to switch between identifying BOOTMGR and identifying ntldr. The most convenient, versatile and professional tool for updating MBR and PBR is Bootsect. Bootsect.exe is a single file program (attached to the boot directory of the Windows vista/7 installation CD) that supports the Windows command line running (including the WinPE command line). It is recommended to start WinPE on disk, execute bootsect.exe, execute bootsect.exe under hard disk operating system, and sometimes cause PBR update to fail because of unable to lock target volume. Also note that the Vista's bootsect.exe does not have a /mbr parameter, so it can only update the PBR and not update the MBR. (two) Bootsect command parameter Bootsect.exe {/help /nt52 /nt60} {SYS ALL | | | | }[/force] /mbr Parameter description /help display instructions. /nt52 applies the NTLDR compatible master boot code to SYS, ALL, or . The operating system installed on SYS, ALL, or must be Windows (R) XP. /nt60 applies the Bootmgr compatible master boot code to SYS, ALL, or . The operating system installed on SYS, ALL, or must be Windows Vista?. SYS updates the main boot code on the system partition used to start Windows. ALL updates the main boot code on all partitions. The ALL option does not have to update the startup code for each volume. Instead, this option updates startup code that can be used as a Windows boot volume (excluding dynamic volumes that do not have a connection to the underlying disk partition). This limitation exists because the boot code must be at the beginning of the disk partition. updates the main startup code on the volume associated with this drive letter. In the following two cases, the boot code is not updated: is not associated with the volume is associated with a volume that is not connected to the underlying disk partition. /force forcibly dismount the volume during startup code updates. This option must be used with care. If Bootsect.exe cannot obtain exclusive volume access, the filesystem may overwrite the boot code before the next restart. Bootsect.exe always attempts to lock and dismount volumes before each update. When a /force is specified, the attempt is forced to dismount if the initial lock attempt fails. For example, if the file on the target volume has now been opened by another program, the lock may fail. If the lock is successful, forced dismount will enable exclusive volume access and reliable startup code updates, even if the initial lock fails. At the same time, forced dismount will render all open handles to files on the target volume invalid. This can cause unexpected behavior from programs that open these files. Therefore, be careful to use this option. /mbr updates the master start record without changing the partition table on the disk sector 0 that contains the partitions specified by SYS, ALL, or . When used with the /nt52 option, the master boot record is compatible with the operating system of the previous version of Windows Vista. When used with the /nt60 option, the master boot record will be compatible with Windows, 7, Windows, Vista, Windows, Server, 2008, or Windows Server 2008 R2. (three) Bootsect application example Bootsect /nt52 E: writes the PBR compatible WindowsXP to the E disk. The bootsect /nt60 sys /mbr writes Windows7 and Vista MBR to the hard disk and writes Windows7 and Vista PBR to the active partition for the active partition. The bootsect /nt52 sys /mbr writes the WindowsXP compatible MBR to the hard disk and writes the WindowsXP compatible PBR to the active partition. (four) Bootsect returns the information definition The following is the Win7 returned to the dual partition WinPE rewrite PBR and MBR success after the return of information. Target, volumes, will, be, updated,, with, NTLDR, compatible, bootcode (the target volume will be updated with the NTLDR compatible boot code) 2, X: \Volume{,}> <\\? (local computer identifier {-} the volume (partition), X: is the volume of the letter, do not display the X: and < > when not allocated. Special attention should be paid here to the fact that the identifiers identified by Bootsect are mostly wrong 3, Successfully, updated, NTFS, filesystem, bootcode (successfully updated the NTFS filesystem boot code) 4, Updated, NTFS, filesystem, bootcode. The, update, may, be, unreliable, the, volume, since, could, not, be,, locked, during, the, update (update the NTFS file system boot code. The update may not be valid because the volume cannot be locked when it is updated Bootcode, was, successfully, updated, on,, all, targeted, volumes The boot code on all target volumes has been successfully updated 6? \?? \PhysicalDrive0? (local computer \ physical drive 0, generally refers to the main hard disk) 7, \Device\Harddisk0\DR0 (device / hard disk 0\ data logger 0) 8, Successfully, updated, disk, bootcode (successfully updated disk boot code) Three, Windows7 boot file maintenance (1) overview of Windows7 boot file maintenance The Windows7 boot file includes the BOOTMGR and the entire boot directory (containing BCD, etc.), and if one of the files is missing or corrupted, Windows7 will not start. There are three ways to guide document maintenance: 1, full backup method: that is, a copy of the boot file to save, and if necessary, then copy back. 2, Bcdedit editing method can only be used for maintenance: BCD, because BCD does not like XP boot.ini that directly use Notepad to open the edit boot options, and it is not a simple third party editing tools, so in BCD can only use Bcdedit custom startup options. Bcdedit is a command line tool that edits BCD (starting configuration data). It has several functions, including creating new BCD, modifying existing BCD, and adding Startup menu options. The tool is included with the distribution in the%WINDIR%\System32 folder. You need administrator privileges to use Bcdedit. Note that Bcdedit is the default operating activities under the partition of \boot\BCD, even if no active partition drive or hidden partition, operations are still valid. To manipulate BCD for other paths, specify with the Bcdedit /store parameter. 3, create method: you must use Bcdboot.exe, the tools included in the%WINDIR%\System32 folder and distribution, it can be used from the Windows image (%WINDIR%\boot and%WINDIR%\System32) to create a startup environment file (the whole boot directory contains BCD, etc.) to the system partition, Windows7 installation disc in the "startup repair" is with this tool as the kernel, but due to the "startup repair" automatically, not according to regional settings, so by default the United States created automatically after the repair after the start menu is English. As far as manual operation is concerned, it is too complicated to master. (two) items and elements in BCD There are only two items in BCD, that is, the startup manager and startup loader entries. The startup manager entry must have one and only one. The startup loader entry can have several (each startup loader entry corresponds to an operating system). The boot manager tab commands all startup loader entries. The subkey of an item is the element, also known as the item option. (three) identifiers in BCD Each entry and key element in BCD has a globally unique identifier for identifying and managing them. The identifier uses the GUID format ({xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}), where the X is sixteen decimal. The GUID identifier can be viewed by the Bcdedit /v command. To facilitate memory, Microsoft uses abbreviated forms to represent GUID identifiers for several specific items and elements. Execute Bcdedit (without arguments) if the following characters are displayed, It indicates that the corresponding item or element is displaying the GUID identifier in an abbreviated form. {bootmgr} Windows startup manager entries {default} defaults to start loader items {ntldr} started the loader entry earlier than Vista's Windows {current} startup loader items currently running {globalsettings} verifies global settings (including verifying whether MBR has compatible BOOTMGR boot code) {memdiag} memory diagnostics {badmemory} RAM fault list {dbgsettings} verifies the debugger running environment {emssettings} verifies the running environment of emergency management services {ramdiskoptions} verifies the RAM environment in which the startup manager runs {bootloadersettings} verify boot loader runtime {resumeloadersettings} verifies sleep recovery environment {fwbootmgr} firmware startup manager entry (computer only for EFI specifications) Below is the double zone (active partition without letter) with executive mode Bcdedit /v display Win7 BCD. In figure, BCD has two entries, a startup manager entry and a startup loader entry, note that three identifiers are enclosed in a box, and all computers that have the same value are the same. Below is the double zone (active partition without letter) Win7 Bcdedit (with no parameters) for display mode BCD. The BCD in the diagram has two entries, a startup manager entry and a startup loader entry, note the three identifiers that are enclosed in a box, and all computers that have Win7 are the same value. (four) Bcdedit command parameter Routine parameter Parameter description / displays the BCDEdit command list. Running this command (without arguments) will display a summary of the available commands. To display detailed help for a specific command, run the Bcdedit / command, where the command is the name of the command that is searching for its details. For example, Bcdedit / createstore displays detailed help for the Createstore command. The parameters used for the file Parameter description /createstore creates an empty BCD. The created BCD is not system BCD. /export exports the contents of the system BCD to the file. This file can later be used to restore the status of the system BCD. This command is valid only for system BCD. /import uses the backup data file generated from the previous /export option to restore the status of the system BCD. This command will delete all existing items before the import of the system BCD occurs. This command is valid only for system BCD. /store this option can be used with most BCDedit commands to specify the BCD to use. If this option is not specified, BCDEdit will operate on the system BCD. Running the Bcdedit /store command yourself is equivalent to running the Bcdedit /enum active command. Such as: 1. create a BCD file named newstroe in the D disk Bcdedit /createstore d:\newstroe 2. backup system BCD to d:\bcdbake file Bcdedit /export d:\bcdbake 3. restore the d:\bcdbake file to system BCD Bcdedit /import d:\bcdbake Arguments for an item Parameter description /copy copies the startup loader entries specified in the same BCD. The boot manager entry cannot be copied. /create creates a new null entry in BCD. If you are specifying an identifier that is currently in use, you cannot specify the /application, /inherit, and /device options. If the identifier is not specified or the specified identifier is not used, then the /application, /inherit, and /device options must be specified. Syntax: Bcdedit /create [{}] /d [-application /inherit []|/inherit DEVICE /device] | | The specifies the new item to be used to specify a new identifier to use the description of , /application must specify a new application, specifies the type of application, the value can be BOOTSECTOR, OSLOADER, RESUME, STARTUP. /delete deletes the specified item in BCD. Such as: 1. create a startup loader item based on NTLDR "Bcdedit /create {ntldr} /d" "Earlier Windows OS Loader"" 2. create a new startup loader item Bcdedit, /create, /d, Windows, Vista, /application, osloader 3. copy the boot loader entry for the current system "Bcdedit /copy {current} /d" "copy of osloader"" 4. remove the startup loader item with GUID as {9f62d3dc-3054-11dd-95a5-001e3d8b719b} Bcdedit /delete {9f62d3dc-3054-11dd-95a5-001e3d8b719b} Arguments for item options Parameter description /deletevalue removes an element from the specified item. Syntax: Bcdedit, [/store, ], /deletevalue, [], /set sets an item option value. Syntax: Bcdedit, [/store, ], /set, [{}], , Where filename is the name of the BCD, and is the identifier of the item (if not specified, defaults to {current}), is the name of the option, and value is the value to be set. Such as: 1. delete the resumeobject option in the {current} entry Bcdedit /deletevale {current} resumeobject 2. set the current system startup menu described as "32bit Vista"" Bcdedit /set {current} description "32bit Vista"" Parameters that control output Parameter description /enum lists items in BCD. The /enum option is the default value for BCDEdit, so running the Bcdedit command (without arguments) is equivalent to running the Bcdedit /enum active command. /v detailed mode. To facilitate memory, Microsoft uses abbreviations to represent identifiers for several specific items and elements. Specifying /v as the command line option will fully display all identifiers. Running the Bcdedit /v command itself is equivalent to running the Bcdedit /enum active /v command. Controls the parameters of the boot manager Parameter description /bootsequence specifies the one-time display order for the next boot. This command is similar to the /displayorder option, Except that it is only used at the next computer startup. The computer will revert to the original display order. /default specifies the default option that the manager selects when the timeout expires. /displayorder specifies the display order used by the manager when the startup options are specified to the user. /timeout specifies the time to wait before the startup manager selects the default item, in seconds. /toolsdisplayorder specifies the display order of each maintenance tool at the tool menu interface. Such as: 1. set the default boot {cbd971bf-b7b8-4885-951a-fa03044f5d71} corresponding system loader Bcdedit /default {cbd971bf-b7b8-4885-951a-fa03044f5d71} 2. set up two operating systems in the boot menu displayed in the order of: {current} {ntldr} Bcdedit /displayorder {current} {ntldr} Parameters that control emergency management services Parameter description /bootems enables or disables the emergency management service (EMS) of the specified item. /ems enables or disables the EMS of the specified operating system startup item. /emssettings sets the global EMS settings for your computer. /emssettings does not enable or disable any particular startup item's EMS. Control debug parameters Parameter description /bootdebug enables or disables the startup debugger that specifies the startup item. Although this command works for any startup item, it is only valid for starting applications. /dbgsettings specifies or displays the global debugger settings for the system. This command does not enable or disable the kernel debugger; use the /debug option to accomplish this. To set a single global debugger setting, use the Bcdedit /setdbgsettings type value command. /debug enables or disables the kernel debugger that specifies the startup item. Four, manually solve 0xc000000e errors Problem Description: Win7 failed to start the Windows boot manager gives 0xc000000e error (sometimes English, sometimes is the Chinese), starting with "repair" system and the Bootsect command can not be resolved, if the installation CD prompted to insert Windows7 repair, can start is no problem, but the Windows boot manager will become English interface. Problem analysis: the Windows startup manager has been loaded successfully, but BOOTMGR cannot find the partition specified in the dvice option in BCD. If the error hint is in English, the locale option for the Windows startup manager entry in BCD is not loaded. BOOTMGR cannot find the partition specified by the dvice option of the Windows startup manager entry in BCD. If the error hint is in Chinese, the locale option for the Windows startup manager entry in BCD has been loaded, but BOOTMGR cannot find the partition specified in the dvice option of the Windows startup loader entry in BCD. Common causes: first, double partition Win7 is adjusted to single partition Win7; secondly, the FDISK /MBR is executed on the hard disk of the single partition Win7; and other operations related to the single partition are carried out for the dual partition Win7. Solution: under WinPE, open the Windows command line tool, go to the Win7 directory of Windows\system32, and execute "Bcdedit /v"", Show that the current BCD reads as follows: Notice the "unknown" in the picture. They're just mistakes. If it is a single partition of Win7, as long as the "unknown" to "partition=C" can be resolved perfectly. If it is double partition Win7, please press the letter of the discretion of the active partition, a word can not have changed to partition=C". Single partition Win7, execute the following commands: Bcdedit, /set, {bootmgr}, device,, partition=C: Bcdedit, /set, {default}, device, partition=C: Bcdedit, /set, {default}, osdevice, partition=C: For single partition Win7, these three commands can also be implemented. After fdisk /mbr, the bootsect /nt60 c: /mbr is avoided. This is strange, so far, no reason has been understood. Five, Windows7 and WindowsXP dual system boot repair (1) boot XP with Win7 1. C Win7 installed first, D disk with XP installed after the installation, after loading the XP into the normal, Win7 can not enter. This installation of XP is its core file in the D disk, but NTLDR, NTDETECT.COM, boot.ini, bootfont.bin, the boot files are in the C drive, because the C drive is the only activity on the hard disk partition. The repair method is as follows. The following commands are executed under cmd: Bootsect, /nt60, c:, /mbr, or bootsect /nt60 sys /mbr "Bcdedit /create {ntldr} /d" "Windows XP Professional"" Bcdedit, /set, {ntldr}, device, partition=c:, or Bcdedit /set {ntldr} device boot Bcdedit, /set, {ntldr}, path, \ntldr Bcdedit /displayorder {ntldr} /addlast Bcdedit /timeout 5 2. C Win7 installed first, D disk XP with GHOST after loading, after loading the Win7 into the normal, XP can not enter. The repair method is as follows. The D under the root directory of the NTLDR, NTDETECT.COM, boot.ini three files are copied to the root directory of C (bootfont.bin does not have to copy, because the guide menu font with Win7). Modify the contents of the boot.ini file, modify the D: by C:, and specify the correct path for the boot XP. The following commands are executed under CMD (Win7, CMD must run as administrator): "Bcdedit /create {ntldr} /d" "Windows XP Professional"" Bcdedit, /set, {ntldr}, device, partition=c:, or Bcdedit /set {ntldr} device boot Bcdedit, /set, {ntldr}, path, \ntldr Bcdedit /displayorder {ntldr} /addlast Bcdedit /timeout 5 3. C XP installation disk installed first, D disk Win7 with GHOST after loading, after loading the XP into the normal, Win7 can not enter. Repair methods are as follows. The following commands are executed under cmd: Bcdboot d:\windows /l zh-cn /s c: (generated \boot and BOOTMGR files folder in the root directory of C) Bootsect, /nt60, c:, /mbr, or bootsect /nt60 sys /mbr BCDEdit /创建{ NTLDR } / D“Windows XP专业版” NTLDR BCDEdit /套{ }设备分区= C:或者BCDEdit /套} { NTLDR开 机装置 BCDEdit /套{意思}路径\文件 BCDEdit /显示顺序{ } / addlast NTLDR BCDEdit /超时5 (二)用XP WIN7问题

分析

定性数据统计分析pdf销售业绩分析模板建筑结构震害分析销售进度分析表京东商城竞争战略分析

引导 我现在安装的是XP+Win7双系统，XP先装在C盘(主分区、活动分 区)，win7在非活动D盘(逻辑分区、非活动分区)，用win7的启动 器来引导XP，一切使用正常。由于想折腾一下用XP的启动器来引导 win7，所以尝试用XP启动器+ GRUB4DOS来启动win7，启动顺序是: NTLDR -> GRLDR bootmgr。我的步骤如下:1、把C盘中的和win7启 动有关的\ bootmgr文件和\启动\整个目录移到D盘，然后把D: \ 启动\ BCD码文件中的bootmgr } {项中的“C:”改成“D”;2、GRLDR 放在C盘，修改C:\启动INI，增加通过NTLDR引导GRLDR的菜单项; 3、修改GRLDR的菜单。1，增加引导D: \ bootmgr的菜单项这样C。 盘就是纯净的XP + GRUB4DOS，D盘就是包括启动器的完整赢7了。按此设置后，成功引导win7，其它使用一切正常。只是存在一个问题，就是进入win7系统后，在”计算机”->属性->“高级系统设置”->“启动和故障恢复设置”中颜色是灰色的，也没有任何启动项，直接使用BCDEdit也提示找不到文件。很明显是win7和BCDEdit都没有找到BCD文件。据此，我分析:1、bootmgr寻找的是与其同一分区下的\启动\ BCD码，所以能够顺利启动win7;2、而进入win7后系统找不到BCD，原因是win7和BCDEdit只寻找活动分区下的\启动\ BCD码，而D盘不是活动分区，所以没找到。