grnow
asked on
windows could not start because the following file is missing or corrupt \windows\system32\config\system
has a machine with this error.. tried to retrieve the contents 1st by connecting as an external drive but then is not detectable in computer management.. could it be a hard disk failure or there is still a chance of retrieving the data?
Did you try booting to last known good config?
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
tried still same error message.. boot to safe mode also the same error message...
ok, the best thing to do is try to boot a linux recovery disk or something like ERD or UBCD. those also have disk saving utlities on those.
once done scanning or fixing, if not successful you can put the system files on a pen drive, and then place those in the dir and overwite those with known good files.
once done scanning or fixing, if not successful you can put the system files on a pen drive, and then place those in the dir and overwite those with known good files.
u don't confused, when u install windows, windows automatically backup these file, first u boot your system form windows xp cd Go to recovery Console then go to C:\windows\repair then copy system file to C:\windows\System32\config
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
run the diagnostics test from HP bios.. it says read write failure.. does that mean the hard disk is not recoverable? willcomp, i will try out your method.. the a43 file manager is loaded from the ultimate boot cd for windows?
yeah it might have problems, so try to recover data with UBCD.
ASKER
when try to run the a43 file management utility, it doesn't seem to load... shall try again
does anything read the files?
ASKER
when click on c drive.. it gives error c:\not accessible
error performing inpage operation
error performing inpage operation
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
does BIOS detect it?
ASKER
apparently no.. guess the hard disk is gone?
If this a raid setup because that could the reason why you cannot access C drive.
Ded9
Ded9
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
now trying out HDD regenerator still scanning... so far only delays detected.. no bad sectors found.. is this good or bad news?
ASKER
its just found 2 delays.. sigh... no bad sectors found at all..
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
no bad sectors found ? then the disk surface is ok = good news
do you have any more info on the delays? never had that myself; it can come from the disk logic board, o rfrom the disk controller
do you have any more info on the delays? never had that myself; it can come from the disk logic board, o rfrom the disk controller
ASKER
on booting up with UBCD 4 windows, it shows C:\fixed disk <unknown>
total size - 1 MB
free space - 1 MB
is this noramal for hard disk having issues?
when try to run start -> programs -> registry tools -> registry restore wizard, it gives error run time error '52', bad file name or number
not much info was given on the delays detected using HDD regenerator
total size - 1 MB
free space - 1 MB
is this noramal for hard disk having issues?
when try to run start -> programs -> registry tools -> registry restore wizard, it gives error run time error '52', bad file name or number
not much info was given on the delays detected using HDD regenerator
have you tried to load it with linux? then try mounting it. you can run a live recovery distro for this. it might give us a new perspective on it.
the particular error you are mentioning sounds like your registry is even bad or corrupted.
you are even saying that BIOS can't detect the drive.
I will see if I can find a really good data recovery OS for you to at least try to get more angles for this.
but that file size definitly is pointing to something wierd.
the particular error you are mentioning sounds like your registry is even bad or corrupted.
you are even saying that BIOS can't detect the drive.
I will see if I can find a really good data recovery OS for you to at least try to get more angles for this.
but that file size definitly is pointing to something wierd.
I've found a few linux recovery distros for you to try.
http://trinityhome.org/Home/index.php?content=TRINITY_RESCUE_KIT____CPR_FOR_YOUR_COMPUTER&front_id=12&lang=en&locale=en
http://partedmagic.com/doku.php
http://ubuntu-rescue-remix.org/
http://trinityhome.org/Home/index.php?content=TRINITY_RESCUE_KIT____CPR_FOR_YOUR_COMPUTER&front_id=12&lang=en&locale=en
http://partedmagic.com/doku.php
http://ubuntu-rescue-remix.org/
try running a disk diag - there can be something else wrong with it.
best download ubcd to run it : http://www.ultimatebootcd.com/
best download ubcd to run it : http://www.ultimatebootcd.com/
ASKER
remixedcat, thanks for your advise to do a chkdsk.. basically i have followed almost all the suggestions listed here except doing a chkdsk.. finally now able to copy out the data and the drive is now readable. had done a chkdsk using the UBCD.. detected some bad sectors and repaired.
would try later to boot up the pc again with the same hard disk to see if \windows\system32\config\s ystem error still there.. seems like its a combination of different problems with the hard disk.
would try later to boot up the pc again with the same hard disk to see if \windows\system32\config\s
ASKER
steps tried:
1. use UBCD run chkdsk.. after which can read the drive, retrieve data and able to boot to windows without error message "\windows\system32\config\ system"
2. run bios diagnostics on hard disk still show read failure
glad the data can be retrieved.
1. use UBCD run chkdsk.. after which can read the drive, retrieve data and able to boot to windows without error message "\windows\system32\config\
2. run bios diagnostics on hard disk still show read failure
glad the data can be retrieved.
ASKER
thanks everyone for the suggestions
ASKER
managed to retrieve the data, though hard disk still has some unknown issue...