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

我们这里介绍的方法在原理上来说格外简洁，即首先将文件删除，然后通过“BootCfg/Rebuild”命令将其重建，在重建的过程中，BootCfg同时也会修复在本文开篇所列出的多FixBoot8Windows下面我们分步骤具体解释。删除文件首先，上面我们说过，进入系统掌握台后，默认工作名目为系统名目，假设Windows安装在C:盘时，即“c:windows”，而文件在根名目上，此时我们需要进入上一级名目：1:cd..进展删除操作的。要做到这一点，需要运行三条命令，依次解除其隐含、只读和隐含属性，这样才能最终将其删除。2:ATTRIB–HC:3:ATTRIB–RC:4:ATTRIB–SC:5:DEL删除的步骤BootCfg现在到了最重要的步骤，运行：5:BOOTCFG/REBUILDWindows不能正常启动的一系列错误，并重建文件。在重建完毕后，将消灭“EnterOSLoadOptions:”输入栏，这时，为保证系统的正常启动，需要留意的是：1、对WindowsXP用户而言，必需添加/FASTDETECT选项。2CPU支持IntelXD或AMDNX/NOEXECUTE=OPTIN选项。在下面图示的例子中，为说明便利，同时添加了上面两个开关选项，不过，切记，假设CPUNOEXECUTE选项，不然，会造成系统启动的故障。而“EnterLoadIdentifier”局部，则相对关系不大，输错也没有太大的影响。固然，假设您是一个完善主义者，则可如图例中输入完整的如“MicrosoftWindowsXPHomeEdition”之类，显得比较标准。BootCfg/Rebuild进展磁盘检查Windows系统长期安全的必要手段。命令很简洁：7:CHKDSK/R/F该命令的运行时间依据机器配置的不同而变化，在某些较为古老的PC的甚至可能会超过半个小时。写入的引导扇区8:FIXBOOT“SureyouwanttowriteanewbootsectortothepartitionC:“Y”确认即可。“EXIT”会惊异地觉察WindowsDLL、注册表项、或NTLDRWindows间。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\WindowsNTcouldnotstartbecausethebelowfileismissingorcorrupt:X:\WINNT\System32\NTLDRisMissingPressanykeytorestartInvalidPressanykeytorestartAllowmetobuildtensionbyprefacingtheend-all/be-allsolutionwithmybackground:Havingworkedforthenow-incorporatedGeekSquadbranchofBestBuyCorporationforthebetterpartofeightmonths,Ihaveseendozensupondozensofsystemscomethroughourdepartmentwithanyoneoftheseerrors,broughtinbycustomerswhoareafraidtheydidsomething,haveavirus,orareinjeopardyoflosingtheirdata.Priortomydiscoveryofaninvaluablesequenceofcommands,ourstandardprocedurewastohookacustomer’sdataandthenrestorethePCwiththecustomer’srestorediscsoranidenticalcopyofWindowswiththecustomer’sOEMlicensekey.Ifthecustomerwasn’tkeenontheapplicablechargesforthedatabackup,weinformedthemofthepotentialrisksforaWindowsrepairinstallation(Let’sfaceit,theydon’talwaysworkright),hadthemsignawaiver,andwedidourbest.NeitheroftheseproceduresarecheapintherealmofcommercialPCrepair,nordotheyinspireatremendouslevelofconfidenceinthetechnicianorthehopefulclient.andothertechnicians,IreceivedpermissiontoundertakeacasestudyonavarietyofPCscurrentlyinservicethatexhibitedanyoftheaforementionedsymptoms,andItookituponmyselftofindabettersolution.AftercrawlingthroughtheMSKB,ExpertsExchange,MSDNandsundrywebsitesallextollingthevirtuesofasolutiontotheseproblems,Ionlyfoundonethatworked,andithasbeenreliablyservingmeforthebetterpartoftwoweeksonseventeenPCstodate.Theprocessissimple:GettotheWindowsRecoveryConsoleforyourparticularWindowsinstallation,navigatetotherootletterofyourinstallation(C:inmostcases),issueeightcommands,andreboot.Thecornerstoneofthisprocessisacommandcalled“BOOTCFG/Rebuild”whichisacompletediagnosticoftheoperatingsystemloadedintotherecoveryconsole;thepurposeofthecommandistoremove/replace/repairanysystemfilesthatwerepreventingtheoperatingsystemfromloadingcorrectly.Amongstthefilesitfixesare:WindowsHardwareAbstractionLayer(HAL)Corruptregistryhives(\WINDOWS\SYSTEM32\CONFIG\xxxxxx)InvalidfilesAcorruptAmissingNTLoader(NTLDR)ThecommandprocessmayapplytoothertypesofbluescreensorHive/HAL/INI/EXE/DLL-relatedstoperrors,butIhavenothadtheluxuryofcomputersinthistypeofdisrepair.TheprocessIamabouttooutlineisvirtuallyharmless,andifyoufeelyoumaybeabletocorrectyourboot-timebluescreensandstoperrorswiththesequence,feelfreetotry.Letusnowbeginwithastep-by-stepinstructionforcorrectingtheseissues.GettingtotheWindowsRecoveryConsoleInsertyourWindowsXPCDintoyourCDandassurethatyourCD-ROMdriveiscapableofbootingtheCD.ConfiguringyourcomputertobootfromCDisoutsideofthescopeofthisdocument,butifyouarehavingtrouble,consultGoogleforassistance.OnceyouhavebootedfromCD,donotselecttheoptionthatstates:“PressF2toinitiatetheAutomatedSystemRecovery(ASR)tool.”You’regoingtoproceeduntilyouseethefollowingscreen,atwhichpointyouwillpressthe“R”keytoentertherecoveryconsole:Afteryouhaveselectedtheappropriateoptionfromsteptwo,youwillbepromptedtoselectavalidWindowsinstallation(Typicallynumber1”).Selecttheinstallationnumber,(Asmentioned,“1”inmostcases),andhitenter.Ifthereisanadministratorpasswordfortheadministratoraccount,enteritandhitenter.Youwillbegreetedwiththisscreen,whichindicatesarecoveryconsoleattheready:Continueto2toproceedwiththerepairfunctions.[new]ProceedingWiththeRepairFunctionsThereareeightcommandsyoumustenterinsequencetorepairanyoftheissuesInotedintheopeningofthisguide.Iwillintroducethemhere,andthenshowtheresultsgraphicallyinthenextsixsteps.Thesecommandsareasfollows:C:CD..C:ATTRIB–HC:\C:ATTRIB–SC:\C:ATRIB–RC:\C:delC:BOOTCFG/RebuildC:CHKDSK/R/FC:FIXBOOTTo“Goupadirectory”incomputingistorevertbacktothedirectoryabovethecurrentfolderyou’reoperatingin.If,forexample,I’mintheC:WINDOWSSYSTEM32directory,andIwanttogetatafileintheWINDOWSdirectory,IwouldmerelytypeCD..andIwouldbetakenoutoftheSYSTEM32folderanduponeleveltoWINDOWS.We’regoingtodothesamethingherefromtheWINDOWSfoldertogettothebasicrootofC:NowthatweareatC:wecanbegintheprocessofrepairingtheoperatingsystemandthatbeginswithmodifyingtheattributesofthe file.Briefly,controlswhatoperatingsystemstheWindowsbootprocesscansee,howtoloadthem,andwherethey’relocatedonyourdisk.We’regoingtomakesurethefileisnolongerhiddenfromourpryingeyes,removetheflagthatsetsitasanundeletablesystemfile,andremovetheflagthatsetsitasafilewecanonlyread,butnotwriteto.Todothis,wewillissuethreecommandsinthisstep:C:ATTRIB–HC:\C:ATTRIB–RC:\C:ATTRIB–SC:\toremovetheHidden,SystemandReadOnlyflags.Nowthatwe’vemodifiedtheattributesforthefile,it’supfordeletion.thesyntaxforitissimple:{DEL|FILENAME},.,C:DEL deletesthefile.Nowforthemostimportantstepofourprocess,theBOOTCFG/REBUILDcommandwhichsearchesforpre-existinginstallationsofWindowsXPandrebuildssundryessentialcomponentsoftheWindowsoperatingsystem,recompilesthe fileandcorrectsalitanyofcommonWindowserrors.Itisveryimportantthatyoudooneorbothofthefollowingtwothings:First,everyWindowsXPownermustuse/FASTDETECTasanOSLoadOptionwhentherebuildprocessisfinalizing.Secondly,ifyouaretheownerofaCPUfeaturingIntel’sXDorAMD’sNXbufferoverflowprotection,youmustalsouse/NOEXECUTE=OPTINasanOSLoadOption.Iwilldemonstratebothcommandsforthepurposeofthisguide,budonotsetNOEXECUTEasaloadoptionifyoudonotownoneoftheseCPUs.Forthe“EnterLoadIdentifier”portionofthiscommand,youshouldenterthenameoftheoperatingsystemyouhaveinstalled.If,forexample,youareusingWindowsXPHome,youcouldtype“MicrosoftWindowsXPHomeEdition”fortheidentifier.Thisgivestheprocesssomeauthenticity,ifyou’rekeenonbeingaperfectionist.ThisstepverifiestheintegrityoftheharddrivecontainingtheWindowsXPinstallation.Whilethisstepisnotanessential functioninourprocess,it’sstillgoodtobesurethatthedriveisphysicallycapableofrunningwindows,inthatitcontainsnobadsectorsorothercorruptionsthatmightbetheculprit.Noscreenshotnecessaryhere!JusttypeCHKDSK/R/FattheC:>prompt.Letitproceed;itcouldtakeinexcessof30minutesonslowercomputers,whenthisisfinishedmoveontotheseventhandfinalstep.Thislaststepalsorequiresnoscreenshot.Whenyouareatt:>prompt,simplytypeFIXBOOT.Thiswritesanewbootsectortotheharddriveandcleansupallthelooseendswecreatedbyrebuildingthe fileandthesystemfiles.WhentheWindowsRecoveryConsoleasksyouifyouare“SureyouwanttowriteanewbootsectortothepartitionC:?”just