registry file failure

Toshiba / SATELLITE A 105
June 28, 2011 at 17:38:08
Specs: Vista, 1.6/1gig
Don't know anything about this laptop. Was bought at a garage sale. HP Pavilon ze 4500 with XP loaded. Stop: c0000218 registry file failure The registry cannot load the hive file \systemroot\system32\config\software or its log or alternate.

Can this be fix and if so how? thanks to all.

See More: registry file failure

Report •

June 28, 2011 at 17:55:03
Boot to Vista dvd and use repair tools.

The laptop may have a way to recover to OEM state. Get and read owners manual for exactly how to do that if possible.

1/3 of highway deaths are caused by drunks. The rest are by people who can't drive any better than a drunk.

Report •

June 28, 2011 at 18:02:47
Sometimes registry error reports turn out to be bad RAM. If you can get inside try cleaning the RAM edge connectors with a pencil eraser, then pop the sticks in and out a few times to clear any oxide off the edge connectors. There are also free RAM checkers around which can run from CD or flash drive.

If that doesn't help then you could get some further idea about the hardware situation by booting with a Linux Live CD (assuming it has a CD drive). I use Puppy Linux for this. You would have to download it on another computer then create a CD from the image (iso) file - most burner software has a facility for this. You then go to BIOS on your garage sale computer and ensure the CD drive is ahead of the HDD when booting. Pop in the CD and see if it boots to Linux. This only uses the RAM and the CD, leaving your Windows operating system intact.

It will tell you if the RAM is useable and you can look at the HDD via Linux to see what is on there. It will help determine whether this is a hardware or software issue, which at this stage is not 100% certain.

I overlapped with response #1 due to slow typing LOL.

Please do not post then vanish - let us know the outcome

Report •

July 7, 2011 at 03:32:02
thank you all for your help. i'm so sorry it has been so long in replying. the problem turned out to be bad ram. once that was fixed everything was fine. thank you all once again.

Report •

Related Solutions

July 7, 2011 at 10:35:44
Glad to hear you got it sorted and thanks for popping back to let us know what it was.

Report •

Ask Question