|
Rebrabuk
|
posted on 28th Jun 05 at 15:14 |
And here's us thinking it was urgent. :o :P
|
Half Pint
|
posted on 28th Jun 05 at 14:58 |
not tried yet but will do within the next few days
|
jamesw
|
posted on 28th Jun 05 at 11:37 |
if its only security thats damaged you only need to copy the security file back which would be
cd \windows\system32\config
ren security security.fkd
copy c:\windows\repair\security c:\windows\system32\config\
If you find it boots but you cant logon with usual username and password its a bit more tricky as you will either have to do a full repair, put drive in another computer and get the latest system restore version of the security file or use the unix based password changer you can get.
|
Antz
|
posted on 28th Jun 05 at 09:34 |
Did it work?
|
Half Pint
|
posted on 27th Jun 05 at 12:59 |
thank you all for you assistance, i will try tonight :D
|
Skinz
|
posted on 27th Jun 05 at 12:01 |
boot off xp CD, go into recovery console, when logged in type in chkdsk /r /p this will repair the files
|
Antz
|
posted on 27th Jun 05 at 11:50 |
Link might help >>> http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B307545
These are the steps that are 65%(it's MSoft) garanteed to get it working
Boot to the Recovery Console.
At the Recovery Console command prompt, type the following lines, pressing ENTER after you type each line:
md tmp
copy c:\windows\system32\config\system c:\windows\tmp\system.bak
copy c:\windows\system32\config\software c:\windows\tmp\software.bak
copy c:\windows\system32\config\sam c:\windows\tmp\sam.bak
copy c:\windows\system32\config\security c:\windows\tmp\security.bak
copy c:\windows\system32\config\default c:\windows\tmp\default.bak
delete c:\windows\system32\config\system
delete c:\windows\system32\config\software
delete c:\windows\system32\config\sam
delete c:\windows\system32\config\security
delete c:\windows\system32\config\default
copy c:\windows\repair\system c:\windows\system32\config\system
copy c:\windows\repair\software c:\windows\system32\config\software
copy c:\windows\repair\sam c:\windows\system32\config\sam
copy c:\windows\repair\security c:\windows\system32\config\security
copy c:\windows\repair\default c:\windows\system32\config\default
Type exit to quit Recovery Console. Your computer will restart.
[Edited on 27-06-2005 by Antz]
|
PaulW
|
posted on 27th Jun 05 at 11:45 |
put in windows install cd & do a repair install (not via recovery console)
if it still does it, alex's option is only real viable way to recover his files, as could well be a fooked hard-disk due to damage/virus
|
TNM
|
posted on 27th Jun 05 at 11:16 |
just do it dry.
|
Half Pint
|
posted on 27th Jun 05 at 11:10 |
tried both Timmeh :o looks terminal think i'll try the rename function then trash the little mo fo !
|
TNM
|
posted on 27th Jun 05 at 11:09 |
Tried safe mode?
Last known good config?
|
Rebrabuk
|
posted on 27th Jun 05 at 11:07 |
Move the files to a different directory rather than deleting them then just incase it causes more problems.
I doubt you can actually replace the files from the repair facility because log files are generally generated by using the computer...
|
Half Pint
|
posted on 27th Jun 05 at 11:02 |
some one, any body ???
|
Half Pint
|
posted on 27th Jun 05 at 10:51 |
yep the security file and the security log file are both there..... thought about renaming or deleting them ????
would prefer trying to replace them with ones from the Windows restore CD but can't.
Alex,
Great idea but it's alot of hassle doing that, worst caser i trash the hard disk and install a clean version of O/S
|
Rebrabuk
|
posted on 27th Jun 05 at 10:48 |
Is the Security file actually there? If so, delete it.. :boggle:
|
Alex
|
posted on 27th Jun 05 at 10:46 |
take out the hard disk, put a new one in, install windows on the new one as master drive, then put the old disk in as slave and hey presto all is ok :)
|
Half Pint
|
posted on 27th Jun 05 at 10:44 |
Right, Have a friend who's PC is Fooked. when the PC boot's up we get a blue screen and error message appears :
windows/system32/config/security
is invalid, curupt or it's log file is missing.
How do i go about repairing these files without having to trash the machine.
I have tried to go through the windows CD to repair the two files but cannot seem to get any further that accessing the directory :boggle:
WTF? next
Help very much appreciated
[Edited on 27-06-2005 by Half Pint]
|