Miss bootmgr Problem

Miss bootmgr problem bootmgr: Start manager. Bootmgr is short for Boot Manager. It is a new start Manager used in Windows Vista and Windows 7 to replace the START Manager-NTLDR in Windows xp. In Microsoft's Windows Vista, Windows Server 2008, and Windows 7 operating systems, the startup process is slightly different from the previous Windows version with NT as the kernel. Bootmgr is equivalent to the NTLDR in the Windows NT/Win 2000/Win XP era. After the computer is powered on www.2cto.com, the BIOS program is started first. After the BIOS self-check is completed, find the Master Boot Record MBR on the hard disk. The MBR reads the DPT (Partition Table) and finds the active primary partition, then, read the PBR (Partition Boot Record, also called pbr) of the active primary partition, and then search for the start manager file bootmgr in the partition. After bootmgr is found, the control is handed over to bootmgr. Bootmgr reads the \ boot \ bcd file (BCD = Boot Configuration Data, that is, "Start Configuration Data". To put it simply, the bcd file in windows7 is equivalent to the boot file in xp. if multiple operating systems exist and the wait time for selecting the operating system is not 0, the operating system selection interface is displayed on the monitor. After we choose to start Windows 7, bootmgr will go to the boot disk to find WINDOWS \ system32 \ winload.exe, and then use winload.exe to load the Windows 7 kernel to start the entire WINDOWS 7 system. This process can be summarized as follows: BIOS --> MBR --> DPT --> pbr --> Bootmgr --> bcd --> Winload.exe --> kernel loading --> the entire Windows 7 System
It can be said that bootmgr is equivalent to the NTLDR In the Win NT/Win 2000/Win XP era. NTLDR is the Boot file in win nt/win2000/WinXP and is a hidden, read-only system file located in the root directory of the system disk. It is mainly responsible for parsing Boot. INI file, used to load the operating system. One noteworthy change is that the Windows 7 startup manager is called by pressing the Space key instead of the F8 function key. However, the F8 key can still be used to retrieve the Advanced Startup option menu. To maintain a scalable firmware interface system, and to enable the highest version of the startup manager to manage all the operating systems, enable the startup manager to be backward compatible rather than backward compatible, the Windows Startup manager lists all installed operating systems as an optional menu. When you configure Windows Vista to coexist with Windows 2000/XP, bootmgr will be fully responsible for the startup management of computers, and NTLDR will be used as a substitute for bootmgr. For example, if the operating systems Windows Vista and Windows XP are configured to coexist, the bootmgr boot menu does not include Windows XP in the boot menu, instead, it is displayed as "earlier versions of Windows ".
STARTUP configuration data (BCD) is a firmware independent database used for configuration data during startup. It replaces boot. ini in NTLDR and is used by Microsoft's new Windows Startup manager. The STARTUP configuration data (BCD) Storage contains the startup configuration parameters and controls the Startup Mode of the operating system in Windows Vista and Windows Server 2008 operating systems. These parameters were previously located in the Boot. ini file (in the BIOS-based operating system) or in the stable RAM (NVRAM) item (in the Operating System Based on the extensible firmware interface ). By adding, deleting, editing, and attaching items to the BCD storage, you can use the Bcdedit.exe command line tool to affect the Windows (R) code running in the pre-operating system environment. Bcdedit.exe is located in the \ Windows \ System32 directory of the Windows Vista partition. The purpose of creating BCD is to provide an improved mechanism for describing STARTUP configuration data. With the development of the new firmware model [for example, the extensible firmware interface (EFI)], you need a scalable and interoperable interface to extract the underlying firmware. This brand-new design provides support for a variety of new features in Windows Vista, such as starting repair tools and installing shortcuts for multiple users. Www.2cto.com
Microsoft's new-generation operating system Windows 7, however, this 7 does not mean that the core version of Windows 7 has been upgraded from Windows Vista's NT 6 to NT 7, windows 7 is the 7th Generation of desktop Windows officially released by Microsoft. The true core version of Windows 7 is only NT 6.1. The relationship between Windows 7 and Windows Vista is like Windows XP (NT 5.1) and Windows 2000 (NT 5.0 ). After many years, Windows once again played a text game with us, so that some people call Windows 7 "NT 6.1 = Windows 6 + 1 = Windows 7 ". To better understand Windows 7 = NT 6 + 1, consider this issue from the perspective of Windows Startup manager. Compared with the name of a Windows official product that is easy to confuse, the start-up Manager is always differentiated strictly according to the core version of the Windows system. This is because when multiple operating systems are configured to coexist, the highest version of the Start manager must be responsible for managing all the operating systems. The start-up Manager only has downward compatibility and does not have upward compatibility. Therefore, the versions of the startup manager must be correctly arranged in the order of high and low, rather than being set randomly like the official names of Windows. Otherwise, multiple operating systems may not be correctly configured to coexist.
For example, Windows 2000/XP/Server 2003 is called NT 5.xbecause all their start managers are NTLDR and BOOT. ini. When you configure multi-system coexistence between Windows 2000, XP, and Server 2003, NTLDR and BOOT. INI are centrally managed for each operating system. Windows Vista/Server 2008, as NT 6.X, adopts the new start manager of BOOTMGR and BCD, when you configure the coexistence of Windows Vista/Server 2008 and Windows 2000/XP/Server 2003 systems, BOOTMGR is fully responsible for the startup management of the computer, and NTLDR is a substitute for BOOTMGR. For example, we have configured the coexistence of Windows Vista, Windows XP, Windows Server 2008, and Windows Server 2003 operating systems, the BOOTMGR boot menu does not list Windows XP and Windows Server 2003 in the boot menu, but displays them as "earlier versions of Windows ". Only Windows Vista and Windows Server 2008 as NT 6.X are eligible to appear in the BOOTMGR Startup menu as an independent option. We can choose whether to start Windows XP or Windows Server 2003 only when the "earlier versions of Windows" option is selected, and BOOTMGR transfers the Start Control to NTLDR and automatically switches to the NTLDR menu. In other words, the NTLDR Start Menu is like a sub menu of the BOOTMGR Start Menu. Www.2cto.com
Now let's take a look at Windows 7. When Windows 7 is installed on a computer with Windows Vista/Server 2008, Windows 7 will add itself to BCD, the BOOTMGR Startup menu will display three options, Windows 7, Windows Vista/Server 2008, and earlier Windows (if any), to coexist with the original Windows Vista/Server 2008. In other words, the start-up manager used in Windows 7 is still BOOTMGR and BCD, which is in a flat relationship with Windows Vista/Server 2008.
If the core version of Windows 7 is called NT 7, it should come up with a new start Manager version later than BOOTMGR and BCD, the new start manager takes over the work of BOOTMGR and BCD. Of course, there is no such startup manager in reality. We may assume it is Loader v7. Then, after we install the Windows NT 7 system, Loader v7 will automatically replace BOOTMGR and BCD for computer startup management, only the Windows system that meets the NT 7.X version will be eligible to appear in the Loader v7 menu as an independent option, windows Vista/Server 2008 will be uniformly displayed as "earlier versions of Windows", Windows XP/Server 2003 will be displayed as "earlier versions of Windows" (of course, if Loader v7 exists a few years later, it will be hard to say whether it is compatible with Windows XP/Server 2003 ).
Although Windows 7 is officially named 7, it does not come up with such a more advanced Loader v7 startup manager, we can only rely on BOOTMGR, BCD, and Windows Vista/Server 2008. Therefore, the core version number of Windows 7 is not qualified to be upgraded to the height of NT 7. It can only be called NT 6.1 at most. Although Windows 7 only releases a preview version, it is hard to say that there will be any changes before the official release, but the current core version number has been determined to be NT 6.1, I believe that Windows 7 startup manager will not change much. It is foreseeable that our computers will be using BOOTMGR and BCD for a long time in year 35. Just as Windows 2000/XP/Server 2003 can be tied together to become the NT 5.X series, Windows Vista/Server 2008 (including future R2) /Windows 7 can also be combined to form a relatively complete NT 6.X family.
In fact, before determining the core version number of Windows 7, I personally hope that Windows 7 can design a new startup manager to replace BOOTMGR and BCD, and truly become NT 7. Although the existing BOOTMGR and BCD are very useful, the biggest drawback is that they are still based on the character-only interface, rather than a GUI that supports mouse operations, windows does not have to be named. Other operating systems have long been able to launch the manager in graphical mode, which is a pity. Imagine how nice it would be to display a graphical startup interface after self-check. You can click the button to select options such as the operating system and security mode. We hope that NT 7 will be implemented in the future. Currently, only third-party start Manager software such as ERD Commander can be used to achieve this purpose. www.2cto.com bootmgr solves the following two problems after the following two problems occur: 1, solution when the error message "Bootmgr is missing, please press Ctrl + Alt + Del to restart" appears, bootmgr is lost, and press Ctrl + Alt + DEL to restart. Errors may occur when you accidentally or intentionally delete some important Vista system files, or the files are damaged or destroyed by viruses or malware, you may also use an improper BIOS simulation or other Vista activation methods to prevent you from accessing the Vista desktop environment. Therefore, this is a system problem. If you want to fix the bootmgr loss error, and you do not want to reinstall Windows Vista, most people choose to use the Vista DVD installation disc to boot, there is a permanent way to eradicate this error. It's easy to follow the steps outlined in. 1. Insert a Windows Vista DVD installation disc and use it to start the computer. If the boot is not started properly, set the boot sequence in the BIOS and start the computer first by the DVD drive. 2. In the window where Winows is installed, select the appropriate system language, time zone, and keyboard mode, and then click Next. 3. In the lower left corner of the screen in the next step, click the "repair your computer" link. 4. If you have many hard disk partitions in Windows, select the partition you want to fix first. If you only have one Windows installation, the selection is obvious.
5. In the "System Recovery options" window, click "start repair" to prevent Windows from being started and solve the problem of losing the bootmgr error message. The same is true for my current version. Later I found that the VISTA system is like that, and then I don't need it. Now I still use XP SP3, which is stable for www.2cto.com 2, solution 1 when the error message "BOOTMGR is compressed Press Ctrl + Alt + Del to restart" appears, the simplest method is to find a winpe disc, use it to boot into the Win PE system, open my computer, right-click drive C, select Properties, remove the "compress this drive to save disk space" check box, and then confirm, if bootmgr is a read-only file, whether to ignore it or not, you can ignore it all. Well, it's done. After restarting, everything works normally. method 2. After Windows 7 compresses the C drive, the nightmare begins. "BOOTMGR is compressed Press Ctrl + Alt + Del to restart" is displayed after restart ". I am using the following methods:
1. Start with vista and select repair. 2. Run “bootrec.exe/fixmbr, Bootrec/fixboot "and restart .. And then appeared in front of the gorgeous, the original success is so simple. Of course, I have tried both methods on the Internet and decompressed the C drive before running this command. The common methods on the Internet are as follows: 1. Boot the vista dvd to get to the command line. expand bootmgr temp attrib bootmgr-s-r-h del bootmgr ren temp bootmgr attrib bootmgr-a + s + r + h 2. Start the Vista installation disk, open the command prompt, go to your Vista system32 (such as c: \ windows \ system32), and then "compact/u c: \ bootmgr" it is best to run "compact/u/a/f/s: c: \ ", decompress the entire c: partition. Author: niemeiquan