Corrupted System Files Win7 Home

[DD]

I recently carried out an sfc scan as part of troubleshooting
procedures to see if I could get rid of a few minor irregularities that
I have noticed from time to time.
The results indicated that there were some corrupted system files but
sfc could not correct them and I was referred to the log at
C:\windows\logs\cbs\cbs.log. I have scrutinised this log but have not
been able to identify the files that sfc said were corrupted.
I then followed the procedure in kb/929833 which is supposed to list
the corrupted files. I opened an elevated command prompt and entered
"findstr /C:"[SR] Cannot repair member file "%windir%\logs\cbs\cbs.log

sfcdetails.txt" as specified in kb\929833 but nothing happened and the

curser just dropped down to the next line.
Any suggestions would be appreciated...

Dennis

 

[LouB]

I recently carried out an sfc scan as part of troubleshooting
procedures to see if I could get rid of a few minor irregularities that
I have noticed from time to time.
The results indicated that there were some corrupted system files
but sfc could not correct them and I was referred to the log at
C:\windows\logs\cbs\cbs.log. I have scrutinised this log but have not
been able to identify the files that sfc said were corrupted.
I then followed the procedure in kb/929833 which is supposed to list
the corrupted files. I opened an elevated command prompt and entered
"findstr /C:"[SR] Cannot repair member file "%windir%\logs\cbs\cbs.log

sfcdetails.txt" as specified in kb\929833 but nothing happened and the

curser just dropped down to the next line.
Any suggestions would be appreciated...

Dennis

sfc = ??

 

[Dave-UK]

I recently carried out an sfc scan as part of troubleshooting
procedures to see if I could get rid of a few minor irregularities that
I have noticed from time to time.
The results indicated that there were some corrupted system files but
sfc could not correct them and I was referred to the log at
C:\windows\logs\cbs\cbs.log. I have scrutinised this log but have not
been able to identify the files that sfc said were corrupted.
I then followed the procedure in kb/929833 which is supposed to list
the corrupted files. I opened an elevated command prompt and entered
"findstr /C:"[SR] Cannot repair member file "%windir%\logs\cbs\cbs.log

sfcdetails.txt" as specified in kb\929833 but nothing happened and the

curser just dropped down to the next line.
Any suggestions would be appreciated...

Dennis

The kb929833 article is not very clear on what it does. The string you typed into
a command prompt generated a text file called sfcdetails.txt.
So when you ran the command it created the text file and then returned to the cursor.
The text file will be wherever you opened the elevated command prompt, usually
in your users folder.
Also, the kb929833 article mentions 'edit' to view the text file. Well that doesn't
work in Win7 64 bit as there is no edit command available. Use your usual text editor.

 

[philo]

I recently carried out an sfc scan as part of troubleshooting procedures
to see if I could get rid of a few minor irregularities that I have
noticed from time to time.
The results indicated that there were some corrupted system files but
sfc could not correct them and I was referred to the log at
C:\windows\logs\cbs\cbs.log. I have scrutinised this log but have not
been able to identify the files that sfc said were corrupted.
I then followed the procedure in kb/929833 which is supposed to list the
corrupted files. I opened an elevated command prompt and entered
"findstr /C:"[SR] Cannot repair member file "%windir%\logs\cbs\cbs.log

sfcdetails.txt" as specified in kb\929833 but nothing happened and the

curser just dropped down to the next line.
Any suggestions would be appreciated...

Dennis

Do not use SFC!

Unless you have specifically updated the SFC repository after every
Windows update you run the danger of replacing newer system files with
older ones and you can end up damaging your system.

Older versions of Windows would allow the user to do so...
but Win7 at least has some degree of built-in protection


If you have problems you cannot solve...just post the exact nature of
the difficulty...and be sure to supply as many relevant details as possible

 

[KCB]

I recently carried out an sfc scan as part of troubleshooting
procedures to see if I could get rid of a few minor irregularities that I
have noticed from time to time.
The results indicated that there were some corrupted system files but
sfc could not correct them and I was referred to the log at
C:\windows\logs\cbs\cbs.log. I have scrutinised this log but have not
been able to identify the files that sfc said were corrupted.
I then followed the procedure in kb/929833 which is supposed to list
the corrupted files. I opened an elevated command prompt and entered
"findstr /C:"[SR] Cannot repair member file "%windir%\logs\cbs\cbs.log

sfcdetails.txt" as specified in kb\929833 but nothing happened and the

curser just dropped down to the next line.
Any suggestions would be appreciated...

Dennis

sfc = ??

System File Checker

http://msdn.microsoft.com/en-us/library/aa382541(VS.85).aspx

 

[DD]

I recently carried out an sfc scan as part of troubleshooting
procedures to see if I could get rid of a few minor irregularities
that I have noticed from time to time.
The results indicated that there were some corrupted system files but
sfc could not correct them and I was referred to the log at
C:\windows\logs\cbs\cbs.log. I have scrutinised this log but have not
been able to identify the files that sfc said were corrupted.
I then followed the procedure in kb/929833 which is supposed to list
the corrupted files. I opened an elevated command prompt and entered
"findstr /C:"[SR] Cannot repair member file "%windir%\logs\cbs\cbs.log

sfcdetails.txt" as specified in kb\929833 but nothing happened and

the curser just dropped down to the next line.
Any suggestions would be appreciated...

Dennis

The kb929833 article is not very clear on what it does. The string you
typed into
a command prompt generated a text file called sfcdetails.txt.
So when you ran the command it created the text file and then returned
to the cursor.
The text file will be wherever you opened the elevated command prompt,
usually
in your users folder.
Also, the kb929833 article mentions 'edit' to view the text file. Well
that doesn't
work in Win7 64 bit as there is no edit command available. Use your
usual text editor

Thanks for the information, I found the corrupted files
[NLslexicons0019.dll and windows logon soundwave.dll] I don't know what
the first is all about but I still get the logon sound so I don't think
that one at least is important. The reason given for sfc picking them up
was, in both cases, Hash Mismatch.
I reckon I will have to look elsewhere for the annoyances that cased me
to start investigating in the first place.

Dennis

 

[DD]

I recently carried out an sfc scan as part of troubleshooting procedures
to see if I could get rid of a few minor irregularities that I have
noticed from time to time.
The results indicated that there were some corrupted system files but
sfc could not correct them and I was referred to the log at
C:\windows\logs\cbs\cbs.log. I have scrutinised this log but have not
been able to identify the files that sfc said were corrupted.
I then followed the procedure in kb/929833 which is supposed to list the
corrupted files. I opened an elevated command prompt and entered
"findstr /C:"[SR] Cannot repair member file "%windir%\logs\cbs\cbs.log

sfcdetails.txt" as specified in kb\929833 but nothing happened and the

curser just dropped down to the next line.
Any suggestions would be appreciated...

Dennis

Do not use SFC!

Unless you have specifically updated the SFC repository after every
Windows update you run the danger of replacing newer system files with
older ones and you can end up damaging your system.

Older versions of Windows would allow the user to do so...
but Win7 at least has some degree of built-in protection


If you have problems you cannot solve...just post the exact nature of
the difficulty...and be sure to supply as many relevant details as possible

Unfortunately I had already run sfc so I guess I will have to live with
whatever the outcome is! As for posting the reason I am searching for
the source of my difficulties, that will be difficult because there are
several unexpected and random occurrences. I'll live with it for now and
post when I have more concrete data.

Thanks for your interest...

Dennis

 

[philo]

I recently carried out an sfc scan as part of troubleshooting procedures
to see if I could get rid of a few minor irregularities that I have
noticed from time to time.
The results indicated that there were some corrupted system files but
sfc could not correct them and I was referred to the log at
C:\windows\logs\cbs\cbs.log. I have scrutinised this log but have not
been able to identify the files that sfc said were corrupted.
I then followed the procedure in kb/929833 which is supposed to list the
corrupted files. I opened an elevated command prompt and entered
"findstr /C:"[SR] Cannot repair member file "%windir%\logs\cbs\cbs.log
sfcdetails.txt" as specified in kb\929833 but nothing happened and the
curser just dropped down to the next line.
Any suggestions would be appreciated...

Dennis

Do not use SFC!

Unless you have specifically updated the SFC repository after every
Windows update you run the danger of replacing newer system files with
older ones and you can end up damaging your system.

Older versions of Windows would allow the user to do so...
but Win7 at least has some degree of built-in protection


If you have problems you cannot solve...just post the exact nature of
the difficulty...and be sure to supply as many relevant details as
possible

Unfortunately I had already run sfc so I guess I will have to live with
whatever the outcome is! As for posting the reason I am searching for
the source of my difficulties, that will be difficult because there are
several unexpected and random occurrences. I'll live with it for now and
post when I have more concrete data.

Thanks for your interest...

Dennis

To get help you'll really need to state what the problem is...
about all I can say is to run a RAM test to at least check the integrity
of your H/W

 

[Dave \Crash\ Dummy]

I recently carried out an sfc scan as part of troubleshooting
procedures to see if I could get rid of a few minor irregularities
that I have noticed from time to time. The results indicated that
there were some corrupted system files but sfc could not correct
them and I was referred to the log at C:\windows\logs\cbs\cbs.log.
I have scrutinised this log but have not been able to identify the
files that sfc said were corrupted. I then followed the procedure
in kb/929833 which is supposed to list the corrupted files. I
opened an elevated command prompt and entered "findstr /C:"[SR]
Cannot repair member file "%windir%\logs\cbs\cbs.log

sfcdetails.txt" as specified in kb\929833 but nothing happened
and the

curser just dropped down to the next line. Any suggestions would be
appreciated...

Do not use SFC!

Unless you have specifically updated the SFC repository after every
Windows update you run the danger of replacing newer system files
with older ones and you can end up damaging your system.

Older versions of Windows would allow the user to do so... but Win7
at least has some degree of built-in protection

I have Windows 7 Ultimate x64, with automatic updating enabled. I was
curious and ran SFC with the /verifyonly switch to avoid the danger you
cite. This is what I got.

C:\Windows\system32>sfc /verifyonly

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

 

[DD]

I recently carried out an sfc scan as part of troubleshooting
procedures to see if I could get rid of a few minor irregularities
that I have noticed from time to time. The results indicated that
there were some corrupted system files but sfc could not correct them
and I was referred to the log at C:\windows\logs\cbs\cbs.log. I have
scrutinised this log but have not been able to identify the files
that sfc said were corrupted. I then followed the procedure in
kb/929833 which is supposed to list the corrupted files. I opened an
elevated command prompt and entered "findstr /C:"[SR] Cannot repair
member file "%windir%\logs\cbs\cbs.log
sfcdetails.txt" as specified in kb\929833 but nothing happened and the
curser just dropped down to the next line. Any suggestions would be
appreciated...

Do not use SFC!

Unless you have specifically updated the SFC repository after every
Windows update you run the danger of replacing newer system files with
older ones and you can end up damaging your system.

Older versions of Windows would allow the user to do so... but Win7 at
least has some degree of built-in protection

I have Windows 7 Ultimate x64, with automatic updating enabled. I was
curious and ran SFC with the /verifyonly switch to avoid the danger you
cite. This is what I got.

C:\Windows\system32>sfc /verifyonly

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

That's useful to know. Actually, most of the irritations I was having
have gone since I ran sfc. I think the only one left may be mouse
related which I will keep working on, so I'm happy! I enjoy sorting out
these little problems so I won't post the problem until I run out of
ideas, that way I learn!

Dennis

 

[philo]

On 05/08/2010 03:13 AM, DD wrote:
I recently carried out an sfc scan as part of troubleshooting
procedures to see if I could get rid of a few minor irregularities
that I have noticed from time to time. The results indicated that
there were some corrupted system files but sfc could not correct them
and I was referred to the log at C:\windows\logs\cbs\cbs.log. I have
scrutinised this log but have not been able to identify the files
that sfc said were corrupted. I then followed the procedure in
kb/929833 which is supposed to list the corrupted files. I opened an
elevated command prompt and entered "findstr /C:"[SR] Cannot repair
member file "%windir%\logs\cbs\cbs.log
sfcdetails.txt" as specified in kb\929833 but nothing happened and the
curser just dropped down to the next line. Any suggestions would be
appreciated...

Do not use SFC!

Unless you have specifically updated the SFC repository after every
Windows update you run the danger of replacing newer system files with
older ones and you can end up damaging your system.

Older versions of Windows would allow the user to do so... but Win7 at
least has some degree of built-in protection

I have Windows 7 Ultimate x64, with automatic updating enabled. I was
curious and ran SFC with the /verifyonly switch to avoid the danger you
cite. This is what I got.

C:\Windows\system32>sfc /verifyonly

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

That's useful to know. Actually, most of the irritations I was having
have gone since I ran sfc. I think the only one left may be mouse
related which I will keep working on, so I'm happy! I enjoy sorting out
these little problems so I won't post the problem until I run out of
ideas, that way I learn!

Dennis

Nope

since sfc wrote no changes it did noting to fix your problem

which you still have not stated