使用故障恢復(fù)控制臺(tái)修復(fù)不能啟動(dòng)的Windows系統(tǒng)

1、使用故障恢復(fù)控制臺(tái)修復(fù)不能啟動(dòng)的Windows系統(tǒng)我們這里介紹的方法在原理上來說十分簡單，即首先將Boot.ini文件刪除，然后通過“BootCfg /Rebuild”命令將其重建，在重建的過程中，BootCfg同時(shí)也會(huì)修復(fù)在本文開篇所列出的多種可能損壞的系統(tǒng)文件，最后使用FixBoot寫入新的啟動(dòng)扇區(qū)。通過這樣的方法，只需簡單的8條命令，即可修復(fù)絕大多數(shù)Windows系統(tǒng)不能正常啟動(dòng)的故障。下面我們分步驟詳細(xì)解釋。刪除Boot.ini文件首先，上面我們說過，進(jìn)入系統(tǒng)控制臺(tái)后，默認(rèn)工作目錄為系統(tǒng)目錄，如果Windows安裝在C:盤時(shí)，即“c:windows”，而Boot.ini文件在根目錄上，

2、此時(shí)我們需要進(jìn)入上一級(jí)目錄：命令1 : cd.Boot.ini是一個(gè)相當(dāng)重要的系統(tǒng)文件，因此，在未解除系統(tǒng)對(duì)其的保護(hù)狀態(tài)前，我們是不能對(duì)其進(jìn)行刪除操作的。要做到這一點(diǎn)，需要運(yùn)行三條命令，依次解除其隱含、只讀和隱含屬性，這樣才能最終將其刪除。命令2 : ATTRIB H C:BOOT.INI命令3 : ATTRIB R C:BOOT.INI命令4 : ATTRIB S C:BOOT.INI命令5 : DEL BOOT.INI刪除boot.ini的步驟使用BootCfg修復(fù)啟動(dòng)故障現(xiàn)在到了最重要的步驟，運(yùn)行：命令5 : BOOTCFG /REBUILD該命令將遍歷系統(tǒng)的安裝設(shè)置，修復(fù)其中的故障部分

3、，糾正導(dǎo)致Windows不能正常啟動(dòng)的一系列錯(cuò)誤，并重建Boot.ini文件。在Boot.ini重建結(jié)束后，將出現(xiàn)“Enter OS Load Options:”輸入欄，這時(shí)，為保證系統(tǒng)的正常啟動(dòng)，需要注意的是：1、對(duì) Windows XP 用戶而言，必須添加 /FASTDETECT 選項(xiàng)。2、如果系統(tǒng)的CPU支持Intel的 XD 或 AMD的 NX功能，必須添加 /NOEXECUTE=OPTIN 選項(xiàng)。在下面圖示的例子中，為說明方便，同時(shí)添加了上面兩個(gè)開關(guān)選項(xiàng)，不過，切記，如果您的CPU不支持相應(yīng)的功能，千萬不要添加 NOEXECUTE 選項(xiàng)，不然，會(huì)造成系統(tǒng)啟動(dòng)的故障。而 “Enter

4、Load Identifier” 部分，則相對(duì)關(guān)系不大，輸錯(cuò)也沒有太大的影響。當(dāng)然，如果您是一個(gè)完善主義者，則可如圖例中輸入完整的如 “Microsoft Windows XP Home Edition”之類，顯得比較規(guī)范。使用BootCfg /Rebuild重建boot.ini進(jìn)行磁盤檢查這一步驟將檢查系統(tǒng)分區(qū)的完整性，雖然從某種意義上說，這一步驟并不是必需的，不過，確保系統(tǒng)硬盤能夠運(yùn)轉(zhuǎn)正常，沒有壞扇區(qū)，也是保證Windows系統(tǒng)長期安全的必要手段。命令很簡單：命令7 : CHKDSK /R /F該命令的運(yùn)行時(shí)間根據(jù)機(jī)器配置的不同而變化，在某些較為古老的PC的甚至可能會(huì)超過半個(gè)小時(shí)。寫入新的

5、引導(dǎo)扇區(qū)命令8 : FIXBOOT該命令將清除修復(fù)過程可能造成的影響系統(tǒng)運(yùn)行的因素，重寫硬盤的引導(dǎo)扇區(qū)。當(dāng)出現(xiàn) “Sure you want to write a new bootsector to the partition C: ?” 提示時(shí)敲入 “Y”確認(rèn)即可。這樣，我們的修復(fù)過程即宣告完成。在故障恢復(fù)控制臺(tái)中輸入“EXIT”以重啟系統(tǒng)，您會(huì)驚奇地發(fā)現(xiàn)Windows系統(tǒng)能夠正常啟動(dòng)，曾經(jīng)出現(xiàn)的如DLL、注冊表項(xiàng)、或 NTLDR之類的錯(cuò)誤奇跡般消失了。通過這樣的方法，可以避免重裝Windows之類的繁瑣勞動(dòng)，節(jié)省您的時(shí)間。Repairing Windows XP in Eight Comm

6、andsMost of us have seen it at one time or another; perhaps on our own PC, the PC of a loved one, or perhaps a PC at your place of employment. The system spends weeks or months operating in a smooth fashion, taking you to the far reaches of the wide, wibbly web, and after one particularly late eveni

7、ng of browsing and gaming, you shut your PC off and go to bed. Millions of people across the globe do just this every night, but a few of us have turned our PCs on the next day not to the standard Windows XP loading screen, but instead this dreaded error:Windows could not start because the following

8、 file is missing or corrupt: WINDOWSSYSTEM32CONFIGSYSTEMYou can attempt to repair this file by starting Windows Setupusing the original Setup CD-ROM.Select R at the first screen to start repair. Which renders your PC inaccessible from the standard boot procedures of Windows XP. You try safe mode, to

9、 no avail. Youre particularly savvy and try issuing the FIXBOOT and FIXMBR commands in the Windows recovery console, but after each reboot, youre merely greeted with the same obnoxious and terrifying blue screen of death thats preventing you from accessing your precious data.Perhaps youve also seen

10、these error screens:Windows NT could not start because the below file is missing or corrupt: X:WINNTSystem32Ntoskrnl.exe _ Windows NT could not start because the below file is missing or corrupt: X:WINNTSystem32HAL.dll _ NTLDR is MissingPress any key to restart _ Invalid boot.iniPress any key to res

11、tart Allow me to build tension by prefacing the end-all/be-all solution with my background: Having worked for the now-incorporated Geek Squad branch of Best Buy Corporation for the better part of eight months, I have seen dozens upon dozens of systems come through our department with any one of thes

12、e errors, brought in by customers who are afraid they did something, have a virus, or are in jeopardy of losing their data. Prior to my discovery of an invaluable sequence of commands, our standard procedure was to hook the afflicted drive to an external enclosure, back up a customers data and then

13、restore the PC with the customers restore discs or an identical copy of Windows with the customers OEM license key. If the customer wasnt keen on the applicable charges for the data backup, we informed them of the potential risks for a Windows repair installation (Lets face it, they dont always work

14、 right), had them sign a waiver, and we did our best.Neither of these procedures are cheap in the realm of commercial PC repair, nor do they inspire a tremendous level of confidence in the technician or the hopeful client. In an effort to expedite our repair time and retain the sanity of myself and

15、other technicians, I received permission to undertake a case study on a variety of PCs currently in service that exhibited any of the aforementioned symptoms, and I took it upon myself to find a better solution. After crawling through the MSKB, Experts Exchange, MSDN and sundry websites all extollin

16、g the virtues of a solution to these problems, I only found one that worked, and it has been reliably serving me for the better part of two weeks on seventeen PCs to date.The process is simple: Get to the Windows Recovery Console for your particular Windows installation, navigate to the root letter

17、of your installation (C: in most cases), issue eight commands, and reboot. The cornerstone of this process is a command called “BOOTCFG /Rebuild” which is a complete diagnostic of the operating system loaded into the recovery console; the purpose of the command is to remove/replace/repair any system

18、 files that were preventing the operating system from loading correctly. Amongst the files it fixes are: · Windows Hardware Abstraction Layer (HAL) · Corrupt registry hives (WINDOWSSYSTEM32CONFIGxxxxxx) · Invalid BOOT.INI files · A corrupt NTOSKRNL.EXE · A missing NT Loader

19、(NTLDR) The command process may apply to other types of blue screens or Hive/HAL/INI/EXE/DLL-related stop errors, but I have not had the luxury of computers in this type of disrepair. The process I am about to outline is virtually harmless, and if you feel you may be able to correct your PCs boot-ti

20、me blue screens and stop errors with the sequence, feel free to try.Let us now begin with a step-by-step instruction for correcting these issues. Getting to the Windows Recovery Console 1. Insert your Windows XP CD into your CD and assure that your CD-ROM drive is capable of booting the CD. Configur

21、ing your computer to boot from CD is outside of the scope of this document, but if you are having trouble, consult Google for assistance. 2. Once you have booted from CD, do not select the option that states: “Press F2 to initiate the Automated System Recovery (ASR) tool.” Youre going to proceed unt

22、il you see the following screen, at which point you will press the “R” key to enter the recovery console: · After you have selected the appropriate option from step two, you will be prompted to select a valid Windows installation (Typically number “1”). Select the installation number, (As menti

23、oned, “1” in most cases), and hit enter. If there is an administrator password for the administrator account, enter it and hit enter. You will be greeted with this screen, which indicates a recovery console at the ready: Continue to page 2 to proceed with the repair functions. newpageProceeding With

24、 the Repair Functions · There are eight commands you must enter in sequence to repair any of the issues I noted in the opening of this guide. I will introduce them here, and then show the results graphically in the next six steps. These commands are as follows: o C: CD . o C: ATTRIB H C:boot.in

25、i o C:ATTRIB S C:boot.ini o C:ATRIB R C:boot.ini o C: del boot.ini o C: BOOTCFG /Rebuild o C: CHKDSK /R /F o C: FIXBOOT · To “Go up a directory” in computing is to revert back to the directory above the current folder youre operating in. If, for example, Im in the C:WINDOWSSYSTEM32 directory, a

26、nd I want to get at a file in the WINDOWS directory, I would merely type CD . and I would be taken out of the SYSTEM32 folder and up one level to WINDOWS. Were going to do the same thing here from the WINDOWS folder to get to the basic root of C: · Now that we are at C: we can begin the process

27、 of repairing the operating system and that begins with modifying the attributes of the BOOT.INI file. Briefly, BOOT.INI controls what operating systems the Windows boot process can see, how to load them, and where theyre located on your disk. Were going to make sure the file is no longer hidden fro

28、m our prying eyes, remove the flag that sets it as an undeletable system file, and remove the flag that sets it as a file we can only read, but not write to. To do this, we will issue three commands in this step:· C:ATTRIB H C:BOOT.INI · C:ATTRIB R C:BOOT.INI · C:ATTRIB S C:BOOT.INI t

29、o remove the Hidden, System and Read Only flags.· Now that weve modified the attributes for the BOOT.INI file, its up for deletion. the syntax for it is simple: DEL | FILE NAME , e.g., C:DEL BOOT.INI deletes the BOOT.INI file.· Now for the most important step of our process, the BOOTCFG /R

30、EBUILD command which searches for pre-existing installations of Windows XP and rebuilds sundry essential components of the Windows operating system, recompiles the BOOT.INI file and corrects a litany of common Windows errors. It is very important that you do one or both of the following two things:

31、First, every Windows XP owner must use /FASTDETECT as an OS Load Option when the rebuild process is finalizing. Secondly, if you are the owner of a CPU featuring Intels XD or AMDs NX buffer overflow protection, you must also use /NOEXECUTE=OPTIN as an OS Load Option. I will demonstrate both commands

32、 for the purpose of this guide, but do not set NOEXECUTE as a load option if you do not own one of these CPUs. For the “Enter Load Identifier” portion of this command, you should enter the name of the operating system you have installed. If, for example, you are using Windows XP Home, you could type

33、 “Microsoft Windows XP Home Edition” for the identifier. This gives the process some authenticity, if youre keen on being a perfectionist.· This step verifies the integrity of the hard drive containing the Windows XP installation. While this step is not an essential function in our process, its

34、 still good to be sure that the drive is physically capable of running windows, in that it contains no bad sectors or other corruptions that might be the culprit. No screenshot necessary here! Just type CHKDSK /R /F at the C:> prompt. Let it proceed; it could take in excess of 30 minutes on slowe

35、r computers, when this is finished move on to the seventh and final step.· This last step also requires no screenshot. When you are at the C:> prompt, simply type FIXBOOT. This writes a new boot sector to the hard drive and cleans up all the loose ends we created by rebuilding the BOOT.INI file and the system files. When the Windows Recovery Console asks you if you are “Sure