使用故障恢复控制台修复不能启动的Windows系统

使用故障恢复控制台修复不能启动的Windows系统我们这里介绍的方法在原理上来说十分简单，即首先将Boot.ini文件删除，然后通过“BootCfg/Rebuild命令”将其重建，在重建的过程中，BootCfg同时也会修复在本文开篇所列出的多种可能损坏的系统文件，最后使用FixBoot写入新的启动扇区。通过这样的方法，只需简单的8条命令，即可修复绝大多数Windows系统不能正常启动的故障。下面我们分步骤详细解释。删除Boot.ini文件首先，上面我们说过，进入系统控制台后，默认工作目录为系统目录，如果Windows安装在C:盘时，即“c:windows”而Boot.ini文件在根目录上，此时我们需要进入上一级目录：命令1:cd..Boot.ini是一个相当重要的系统文件，因此，在未解除系统对其的保护状态前，我们是不能对其进行删除操作的。要做到这一点，需要运行三条命令，依次解除其隐含、只读和隐含属性，这样才能最终将其删除。命令2:ATTRIB-HC:BOOT」NI命令3:ATTRIB-RC:BOOT.INI命令4:ATTRIB-SC:BOOT.INI命令5:DELBOOT.INIMicrosoftUindousXPCD…C：\>ATTRIB-HC：BOOT-INIC：V>ArTRIB一只CiBOOT.INIG：V>ATTRIB-SC=BOOT.INIWADELHOOT.INIHlCiHDiy.COM删除boot.ini的步骤使用BootCfg修复启动故障现在到了最重要的步骤，运行：命令5:BOOTCFG/REBUILD该命令将遍历系统的安装设置，修复其中的故障部分，纠正导致Windows不能正常启动的一系列错误，并重建Boot.ini文件。在Boot.ini重建结束后，将出现“EnterOSLoadOptions:输”栏，这时，为保证系统的正常启动，需要注意的是：1、对WindowsXP用户而言，必须添加/FASTDETECT选项。2、如果系统的CPU支持Intel的XD或AMD的NX功能，必须添加/NOEXECUTE=OPTIN选项。在下面图示的例子中，为说明方便，同时添加了上面两个开关选项，不过，切记，如果您的CPU不支持相应的功能，千万不要添加NOEXECUTE选项，不然，会造成系统启动的故障。而“EnterLoadIdentifier部分，则相对关系不大，输错也没有太大的影响。当然，如果您是一个完善主义者，则可如图例中输入完整的如“MicrosoftWindowsXPHomeEdition之类，显得比较规。c：K>B«:¥EnterLo^dIdencificr：Uxnd.o>fPWantE4iTi«DEnterOSLead(Xptions:/fastd«t^ct/nntrxecule=optLn使用BootCfg/Rebuild重建boot.ini进行磁盘检查这一步骤将检查系统分区的完整性，虽然从某种意义上说，这一步骤并不是必需的，不过，确保系统硬盘能够运转正常，没有坏扇区，也是保证Windows系统长期安全的必要手段。命令很简单：命令7:CHKDSK/R/F该命令的运行时间根据机器配置的不同而变化，在某些较为古老的PC的甚至可能会超过半个小时。写入新的引导扇区命令8:FIXBOOT该命令将清除修复过程可能造成的影响系统运行的因素，重写硬盘的引导扇区。当出现SureyouwanttowriteanewbootsectortothepartitionC:?提示时敲入“丫确认即可。这样，我们的修复过程即宣告完成。在故障恢复控制台中输入“EXIT”以重启系统，您会惊奇地发现Windows系统能够正常启动，曾经出现的如DLL、注册表项、或NTLDR之类的错误奇迹般消失了。通过这样的方法，可以避免重装Windows之类的繁琐劳动，节省您的时间。RepairingWindowsXPinEightCommandsMostofushaveseenitatonetimeoranother;perhapsonourownPC,thePCofalovedone,orperhapsaPCatyourplaceofemployment.Thesystemspendsweeksormonthsoperatinginasmoothfashion,takingyoutothefarreachesofthewide,wibblyweb,andafteroneparticularlylateeveningofbrowsingandgaming,youshutyourPCoffandgotobed.Millionsofpeopleacrosstheglobedojustthiseverynight,butafewofushaveturnedourPCsonthenextdaynottothestandardWindowsXPloadingscreen,butinsteadthisdreadederror:Windowscouldnotstartbecausethefollowingfileismissingorcorrupt:\WINDOWS\SYSTEM32\CONFIG\SYSTEMYoucanattempttorepairthisfilebystartingWindowsSetupusingtheoriginalSetupCD-ROM.Select‘R'atthefirstscreentostartrepair.WhichrendersyourPCinaccessiblefromthestandardbootproceduresofWindowsXP.Youtrysafemode,tonoavail.You'reparticularlysavvyandtryissuingtheFIXBOOTandFIXMBRcommandsintheWindowsrecoveryconsole,butaftereachreboot,you'remerelygreetedwiththesameobnoxiousandterrifyingbluescreenofdeaththat'spreventingyoufromaccessingyourpreciousdata.Perhapsyou'vealsoseentheseerrorscreens:WindowsNTcouldnotstartbecausethebelowfileismissingorcorrupt:X:\WINNT\System32\Ntoskrnl.exeWindowsNTcouldnotstartbecausethebelowfileismissingorcorrupt:X:\WINNT\System32\HAL.dllNTLDRisMissingPressanykeytorestartInvalidboot.iniPressanykeytorestartAllowmetobuildtensionbyprefacingtheend-all/be-allsolutionwithmybackground:Havingworkedforthenow-incorporatedGeekSquadbranchofBestBuyCorporationforthebetterpartofeightmonths,Ihaveseendozensupondozensofsystemscomethroughourdepartmentwithanyoneoftheseerrors,broughtinbycustomerswhoareafraidtheydidsomething,haveavirus,orareinjeopardyoflosingtheirdata.Priortomydiscoveryofaninvaluablesequenceofcommands,ourstandardprocedurewastohooktheafflicteddrivetoanexternalenclosure,backupacustomer'sdataandthenrestorethePCwiththecustomer'srestorediscsoranidenticalcopyofWindowswiththecustomer'sOEMlicensekey.Ifthecustomerwasn'tkeenontheapplicablechargesforthedatabackup,weinformedthemofthepotentialrisksforaWindowsrepairinstallation(Let'sfaceit,theydon'talwaysworkright),hadthemsignawaiver,andwedidourbest.NeitheroftheseproceduresarecheapintherealmofcommercialPCrepair,nordotheyinspireatremendouslevelofconfidenceinthetechnicianorthehopefulclient.Inanefforttoexpediteourrepairtimeandretainthesanityofmyselfandothertechnicians,IreceivedpermissiontoundertakeacasestudyonavarietyofPCscurrentlyinservicethatexhibitedanyoftheaforementionedsymptoms,andItookituponmyselftofindabettersolution.AftercrawlingthroughtheMSKB,ExpertsExchange,MSDNandsundrywebsitesallextollingthevirtuesofasolutiontotheseproblems,Ionlyfoundonethatworked,andithasbeenreliablyservingmeforthebetterpartoftwoweeksonseventeenPCstodate.Theprocessissimple:GettotheWindowsRecoveryConsoleforyourparticularWindowsinstallation,navigatetotherootletterofyourinstallation(C:inmostcases),issueeightcommands,andreboot.Thecornerstoneofthisprocessisacommandcalled“BOOTCF/GRebuild”whichisacompletediagnosticoftheoperatingsystemloadedintotherecoveryconsole;thepurposeofthecommandistoremove/replace/repairanysystemfilesthatwerepreventingtheoperatingsystemfromloadingcorrectly.Amongstthefilesitfixesare:?WindowsHardwareAbstractionLayer(HAL)?Corruptregistryhives(\WINDOWS\SYSTEM32\CONFIG\xxxxxx)?InvalidBOOT.INIfiles?AcorruptNTOSKRNL.EXE?AmissingNTLoader(NTLDR)ThecommandprocessmayapplytoothertypesofbluescreensorHive/HAL/INI/EXE/DLL-relatedstoperrors,butIhavenothadtheluxuryofcomputersinthistypeofdisrepair.TheprocessIamabouttooutlineisvirtuallyharmless,andifyoufeelyoumaybeabletocorrectyourPCsboot-timebluescreensandstoperrorswiththesequenee,feelfreetotry.Letusnowbeginwithastep-by-stepinstructionforcorrectingtheseissues.GettingtotheWindowsRecoveryConsoleInsertyourWindowsXPCDintoyourCDandassurethatyourCD-ROMdriveiscapableofbootingtheCD.ConfiguringyourcomputertobootfromCDisoutsideofthescopeofthisdocument,butifyouarehavingtrouble,consultGoogleforassistanee.OnceyouhavebootedfromCD,donotselecttheoptionthatstates:essF2toinitiPtetheAutomatedSystemRecovery(ASR)tool.”You'regoingtoproceeduntilyouseethefollowingscreen,atwhichpointyouwillpresstheR”keytoenterthe"recoveryconsole:WindowsXPPpoFesslondilSetupMici'asoFtWindowsXPbContinuetopage2toproceedwiththerepairfunctions.[newpage]ProceedingWiththeRepairFunctionsThereareeightcommandsyoumustenterinsequeneetorepairanyoftheissuesInotedintheopeningofthisguide.Iwillintroducethemhere,andthenshowtheresultsgraphicallyinthenextsixsteps.Thesecommandsareasfollows:oC:CD..oC:ATTRIB-HC:\boot.inioC:ATTRIB-SC:\boot.inioC:ATRIB-RC:\boot.inioC:delboot.inioC:BOOTCFG/RebuildoC:CHKDSK/R/FoC:FIXBOOTTo“Goupadirectory”incomputingistorevertbacktothedirectoryabovethecurrentfolderyou'reoperatingin.If,forexample,I'mintheC:WINDOWSSYSTEM32directory,andIwanttogetatafileintheWINDOWSdirectory,IwouldmerelytypeCD..andIwouldbetakenoutoftheSYSTEM32folderanduponeleveltoWINDOWS.We'regoingtodothesamethingherefromtheWINDOWSfoldertogettothebasicrootofC:Mici'asoFtWindowsXPftTrRre-hc：boot,iniC：\>ftTrRrB-RC：BOOT.INIG：\>flTrRIB-8C=BOOT-INIsupfordeletion.Nowthatwe'vemodifiedtheattributesfortheBOOT.INIfile,itthesyntaxforitissimple:{DEL|FILENAME},e.g.,C:DELBOOT.INIdeletestheBOOT.INIfile.Mici'asoFtUindol7SXP*ou£dessystemvep^aii*andcol*tryFunctiona.lityTypeEXITtoquittheRecoueryConsoleanCD「C=S>ftTrRIB-HC=BOOT.INIC：\>ftirRIB-RC：BOOI-INIC：\>ftTTRIB-8C=BOOT.IHIC：\>DELBOOT.INIC：\>?Nowforthemostimportantstepofourprocess,theBOOTCFG/REBUILDcommandwhichsearchesforpre-existinginstallationsofWindowsXPandrebuildssundryessentialcomponentsoftheWindowsoperatingsystem,recompilestheBOOT.INIfileandcorrectsalitanyofcommonWindowserrors.Itisveryimportantthatyoudooneorbothofthefollowingtwothings:First,everyWindowsXPownermustuse/FASTDETECTsanOSLoadOptionwhentherebuildprocessisfinalizing.Secondly,ifyouaretheownerofaCPUfeaturingIntel'sXDorAMDsNXbufferoverflowprotection,youmustalsouse/NOEXECUTE=OPTasanOSLoadOption.Iwilldemonstratebothcommandsforthepurposeofthisguide,butdonotsetNOEXECUTEasaloadoptionifyoudonotownoneoftheseCPUs.Forthe“EnterLoadIdentifier”portionofthiscommand,youshouldenterthenameoftheoperatingsystemyouhaveinstalled.If,forexample,youareusingWindowsXPHome,youcouldtype“MicrosoftWindowsXPHomeEdition”fortheidentifier.Thisgivestheprocesssomeauthenticity,ifyou'rekeenonbeingaperfectionist.C=\>ftTTRIB-SC：BOOT-INICz\>DELBOOT-INIC：\>BOOTCFG^REBUILD!>GanninyaIJ.£o>*UlndLcusion^.Pleasesincethisnaytakeauhile.亠.TheWindavjsinstallatiansc^nvassuccessful・Nate-Theresultsa^estoredstatzLcall^fortliis^ession-IFthediskconFiguratjjonchangesdui*in^ftliissession,intogpetanupdatedscan,^poumu^tfipstrebootthemachineandthenrescan(liedi^Jcs・IotalidentifiedWindousinstalls:1[11:C:\UindowsAddinstallationtobootlist?<¥es/Nu/All):YEritei*L(radIdentlfler-UindeusHFHoneEditionEratei'OSLo^dOptions:astdetect^noexjecu±e=0^^inC：K>?ThisstepverifiestheintegrityoftheharddrivecontainingtheWindowsXPinstallation.Whilethisstepisnotanessentialfunctioninourprocess,it'sstillgoodtobesurethatthedriveisphysicallycapableofrunningwindows,inthatitcontainsnobadsectorsorothercorruptionsthatmightbetheculprit.Noscreenshotnecessaryhere!JusttypeCHKDSK/R/FattheC:>prompt.Letitproceed;itcouldtakeinexcessof30minutesonslowercomputers,whenthisisfinishedmoveontotheseventhandfinalstep.?Thislaststepalsorequiresnoscreenshot.WhenyouareattheC:>prompt,simplytypeFIXBOOTThiswritesanewbootsectortotheharddriveandcleansupallthelooseendswecreatedbyrebuildingtheBOOT.INIfileandthesystemfiles.WhentheWindowsRecoveryConsoleasksyouifyouare“SureyouwanttowriteanewbootsectortothepartitionC:?”justhit“Y,”thenentertoconfirmyourdecision.ResultsandWrap-UpIt'stimetorebootyourPCbytypingEXITintheWindowsRecoveryConsoleandconfirmingthecommandwithastrokeoftheenterkey.Withanyluck,yourPCwillbootsuccessfullyintoWindowsXPasifyourvariousDLL,Hive,EXEandNTLDFferrorsneverexisted.You'vejustsavedyourselffrommanyhoursofwork,frustration,potentialdatalossandshellingoutyourhard-earnedgreenbacksatabrick'n'mortaroperation.Keepinmindthatthissolutionisonlydesignedtoresolvetheissuesintroducedintheprefaceifthecauseisunrelatedtospywareandviruses;whileIhavehadsignificantluckwithrebuildingheavily-infectedsystemsinthemethodIhavedescribed,itisnotguaranteed.IfyoubelieveyourPChasaffectedoneofthesesymptomsduetospywareorviruses,today'sfastest-growingPCnuisanee,pleasedostopbyourSpyware/Virus/TrojanForumtoreceivefirst-classassistaneeinquarantine,removalandrepair.BesuretoreadtheguidelinesofourSVTForumbeforeposting!Goodluckandhappyhunting,Robert“Thrax”HallockWelcon>etoSetup.ThispoptionoftheSetupppogri'ampreparesHicrosofUindovsHP匸0runonyour**Gomputer-Tos：etupVJLndousXPndu-口pessENIER_Torepftii*aJi-ndousXPinstallationusIngRecouftPyConsole.-pressR-•ToquitSetupwithoutinstallingWindousXF,pressF3.Afteryouhaveselectedtheappropriateoptionfromsteptwo,youwillbepromptedtoselectavalidWindowsinstallation(Typicallynumber1”).Selecttheinstallationnumber,(Asmentioned,1inmostcases),andhitenter.Ifthereisanadministratorpasswordfortheadministratoraccount,enteritandhitenter.Youwillbegreetedwiththisscreen,whichindicatesarecoveryconsoleattheready: