missing or corrupt windows\system32\config\software

  • Thread starter Thread starter ram
  • Start date Start date
R

ram

I have a user with a laptop getting the following error:
Windows xp could not start because the following file is
missing or corrupt: windows\system32\config\software.
When I boot the system into the recovery console, I see
the file, but it is around 41-42 MB. It seems to be
unusually big in relation to the other registry files in
the config folder. No recent changes in software
install/unistall that the user knows of. Let me know what
you think.
 
Hello,

Take a look at the following article:
307545 How to Recover from a Corrupted Registry That Prevents Windows XP
from
http://support.microsoft.com/?id=307545

--
Have a great day!

Graham, MCSE²+I, MCSA
Microsoft Corporation Exchange Enterprise Messaging

* Please do not send email directly to this alias. This alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.


Find out about Strategic Technology Protection Program and get our Security
Toolkit! Go to http://www.microsoft.com/security.
Microsoft Exchange "How-To" Documents:
http://support.microsoft.com/support/exchange/content/Howtos/Howtos.asp
Exchange 2000 Server "How-To" Articles:
http://support.microsoft.com/support/exch2000/e2khowto.asp
Exchange 2000 Setup Whitepaper:
http://www.microsoft.com/technet/tr...hange2000/proddocs/articles/e2kias/E2KIAS.ASP

Realize Your Potential with Microsoft
 
I've tried that, but when I try and copy the software
file, I get the message that the file cannot be copied.
When I look at the target directory, it shows the other
four: default, security, sam, and system, along with what
I'm assuming is a partial copy of the software file,
named $$tmp$$.* with a file size of 86 KB. I looked at
the attributes of the file, and the only one set is for
the archive. I'm not sure wht I can't copy it. Let me
know. Thanks.
 
Well, since it's a system file, you'll have to either create a parallel
installation, or better still use

307654 HOW TO: Install and Use the Recovery Console in Windows XP
http://support.microsoft.com/?id=307654

--
Have a great day!

Graham, MCSE²+I, MCSA
Microsoft Corporation Exchange Enterprise Messaging

* Please do not send email directly to this alias. This alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.


Find out about Strategic Technology Protection Program and get our Security
Toolkit! Go to http://www.microsoft.com/security.
Microsoft Exchange "How-To" Documents:
http://support.microsoft.com/support/exchange/content/Howtos/Howtos.asp
Exchange 2000 Server "How-To" Articles:
http://support.microsoft.com/support/exch2000/e2khowto.asp
Exchange 2000 Setup Whitepaper:
http://www.microsoft.com/technet/tr...hange2000/proddocs/articles/e2kias/E2KIAS.ASP

Realize Your Potential with Microsoft




I've tried that, but when I try and copy the software
file, I get the message that the file cannot be copied.
When I look at the target directory, it shows the other
four: default, security, sam, and system, along with what
I'm assuming is a partial copy of the software file,
named $$tmp$$.* with a file size of 86 KB. I looked at
the attributes of the file, and the only one set is for
the archive. I'm not sure wht I can't copy it. Let me
know. Thanks.
 
my solution

I had some registry problem with a machine at work. In my case the machine did not finish booting into windows. after the windows XP screen the system just hung up.

here is the solution that worked for me and in many other instances where i have seen registry currupt or missing problems.

take HDD out of system and install as secondary master of a known working system running Windows 2000 or XP, boot system and go to command prompt. run check disk on hard drive that does not boot windows.
use the following command :
c:\ chkdsk volume /F /R
where volume = driver letter followed by a colon

this should scan the hard drive and recover or replace any corrupted registry file.
after check disk is finished return hard drive to original system and boot up in normal mode.
wha i normally do after system boots up is I run a system restore to a previous date, before the registry got currupted.
it would also be good to run memory test on ur RAM modules to verify intergrity of modules.
 
Last edited:
How to fix [/contents/win/winintro.php3 Windows] system32 config system is corrupt in Windows xp [http://www.techgyaan.org/2008/07/win...ystem-is.html]

Resolution:

1. Insert your Windows Xp CD and reboot from the CD drive

[To boot from CD, go to BIOS Setup option on startup and select your CD/DVD drive as the first boot drive, save the present settings and exit]

Your computer will reboot & will boot from Windows Xp

2. Press ‘R’ when offered the option of using the Windows Recovery Console

Recovery Console will prompt at the command prompt type the following:

C:\WINDOWS >cd system32\

this changes the current directory to C:\Windows\System32

ren config configold

This renames the config folder to configold

mkdir config

this makes a new directory called config

cd config

changes the current directory to c:\Windows\System32\Config

then type the following lines pressing enter after each one

copy c:\windows\repair\system

copy c:\windows\repair\software

copy c:\windows\repair\sam

copy c:\windows\repair\security

copy c:windows\repair\default

after each line it should say:

1 file copied

type: exit

Now your system will reboot

[To boot from Hard Drive, go to BIOS Setup option on startup and select your Hard drive as the first boot drive, save the present settings and exit]

Best Regards,
Balaram R
email: (e-mail address removed)
www: http://www.techgyaan.org
Forum: http://techgyaan.forumotion.com/
 
I have done everything mentioned in these posts and I recovered the system. I used the process outlined in the MS Knowledge base article http://support.microsoft.com/kb/307545

I ran the system, read some e-mail, watched a show on Hulu. I shut down the system properly without incident.

Next morning, I turned on the system and the problem returned.

Running WinDbg on the system dump files tells me Probably caused by : ntoskrnl.exe ( nt+21cc5 )

Thanks for your help.

The system is an IBM Laptop (2 Ghz, 1 Gig RAM) running XP Pro SP3.
 
Last edited:
Back
Top