When I booted up my Dimension XPS Gen 3 computer this morning it went to the XP login screen but there were a bunch of sidways equals sign running vertically on the screen and my username did not appear.
I turned off the computer and now when I boot up, I get a blue screen of death that says:
STOP: c0000218 (Registry File Failure)
Registry cannot load the hive (file):
\SystemRoot\System32\Config\SOFTWARE
or its log or alternate. It is corrupt, absent, or not writeable.
Booting into safe mode causes the same problem (can't get into Windows). I don't mind formating after I get this resolved, but I want to try and back up my data files to a dvd first.
I've accessed the Microsoft KB article # 307545 which gives instructions on how to fix the damaged registry files. However the instructions say that a problem may arise if using an OEM installed version of XP (Dell XP recovery cd) because "The system hive on OEM installations creates passwords and user accounts that did not exist previously. If you use the procedure that is described in this article, you may not be able to log back into the recovery console to restore the original registry hives." Will I encounter this problem? I created an administrator password and know what it is, but I don't know if this is what they are talking about.
The article is referring to the System Administrator password (not the password on your named administrator account). By default, the System Administrator password should be null (blank) but system which are set up using Sysprep (which Dell uses) can have an unknown password, which means that you will be unable to log onto Recovery Console. If you can enter Recovery Console you should not have the problem referred to, although the repair procedures given in the MSKB article is less than 100% efficient in recovering from the problem.
I never did the 'control setpasswords2' command, but it's possible that I set it inadvertantly at some point in the year I've had the computer. Is the C:\Windows\ prompt the recovery tool? or is the recovery tool a dos program? Sorry, this is the first time I've ever had something this big happen to my computer and am unfamiliar with all of the utilities. Your help is greatly appreciated!
I'm astounded. It sounds as though you are in Recovery Console which should only happen if your administrator password is the same as the System Admin password. By any chance did you change the System Administrator password usinf the procedure
here to match your personal password?
Thanks for the help Denny. Is there a way to test whether I can enter the Recovery Tool before moving the registry files around? I'm not at my computer right now, but earlier today I inserted the xp cd and tried to run the xp recovery. it asked me for an administrator password. is the system administrator password you refer to? I entered in my personal admin password and it ended up taking me to a c:\windows\ prompt. I'm guessing this is not where I want to be?
If the system had not accepted the password you would not have gotten any prompt. See
this for a description of what you should have seen (and be seeing).
I faced the same problem after updating my Windows Microsoft Antispyware. STOP: 0000218 bla bla bla. I have tried the repair reinstall you mentioned somewhere, but there is no R (repair) option, after I click ENTER (I have Windows xp professional). You also mentioned that the solution to this problem offerred by Microsoft do not help properly and here you gave another solution. So, I am wondering if this is the ultimate answer to my problem?
Denny Denham
2 Intern
•
18798 Posts
1559
0
Posted October 26th, 2005 20:00
The article is referring to the System Administrator password (not the password on your named administrator account). By default, the System Administrator password should be null (blank) but system which are set up using Sysprep (which Dell uses) can have an unknown password, which means that you will be unable to log onto Recovery Console. If you can enter Recovery Console you should not have the problem referred to, although the repair procedures given in the MSKB article is less than 100% efficient in recovering from the problem.