System File Checker: Corrupted Files

D

don

Member
Joined
Nov 7, 2012
Posts
11
Hello all,

First time poster. Stumbled across the site and was really impressed by the wealth of knowledge here. I have a problem and I'm stuck. I noticed it when I was unable to install security updates from Microsoft (Code 8007006E). After hours spent pouring through different options, I've hit a wall. Hope someone here might be able to provide some insight...

It sounds to me (and my very limited computer knowledge) like "dee" might have had some similar issues:

https://www.sysnative.com/forums/showthread.php/3360-CBS-Logs-corrupt-file(s)-issue

Here is what I got from the SFC scan....

Corrupted file number 1:

00000161 [SR] Beginning Verify and Repair transaction

00000163 [SR] Repairing corrupted file [ml:520{260},l:64{32}]"\??\C:\Windows\PolicyDefinitions"\[l:24{12}]"inetres.admx" from store

00000166 [SR] Repairing corrupted file [ml:520{260},l:76{38}]"\??\C:\Windows\PolicyDefinitions\en-US"\[l:24{12}]"InetRes.adml" from store

00000169 [SR] Verify complete


Corrupted file number 2:

Beginning Verify and Repair transaction
000001c6 [SR] Cannot repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

000001c8 [SR] Cannot repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

000001c9 [SR] This component was referenced by [l:162{81}]"Package_17_for_KB948465~31bf3856ad364e35~amd64~~6.0.1.18005.948465-60_neutral_GDR"

000001cb [SR] Verify complete



Just a bit more info about what I have tried so far:
Norton 360 full system scan in Safe Mode= no errors
C Drive CHKDSK= no errors
C Drive "Defrag"= no errors
And some other tings I'm surely forgetting...

System Info:

Vista Home Premium
64-bit OS
Service Pack 2

I don't believe I have any "physical" issues with the drive; I hope! I also attached the full SFC txt to this message. I'd be more than happy to attach more information if needed. Thank you in advance! Any and all advice is greatly appreciated.

Best,
Don
 

Attachments

The first one was fixed, so no problem. The 2nd is for Windows Sidebar, so unless you use it, not a problem. You should be able to delete it and let Windows re-create it if needed.

On my Windows 8 system, settings.ini looks like this:

[Root]
SettingsVersion=00.00.00.02
 
Z,

Thanks for the quick reply. You're correct; it does look like the first file was corrected. However, those are the results from the third scan of the evening (read corrupt each time). You'll see that both files read as "cannot repair" in the last few lines of the attachment. Not sure SFC can fix the problem. It's almost like something is changing the file after it has been repaired. Thanks again!
 
No, Don should NOT run the batch fix that was provided for Diane in the other topic. That was written specifically for her situation. Both tom982 and niermiro are in the U.K. and will look at the information provided and provide advice or request additional information.
 
@Ztrucker

Any fix written by me, or anyone else for that matter, is specific to the thread in question and shouldn't be cross referenced to another thread. Running my batch file would have made many changes that have nothing to do with this thread here.

Hi Don, welcome to Sysnative :)

Looking at your SFC log, you'll be glad to hear that everything is in order. settings.ini always comes up and is nothing to worry about. If someone adds a custom sidebar gadget in Vista, settings.ini gets modified accordingly. Then when SFC checks the file hash, it sees it as different to what the default is and thinks it's corrupt, that's all :) So there are no issues with your SFC log that require any attention - one was fixed, and the other is normal.

Let's see what the System Update Readiness Tool (SURT) thinks about your problem. Download and install this:

http://go.microsoft.com/fwlink/?LinkID=167363

Then copy and paste the contents of the log please:

C:\Windows\Logs\CBS\CheckSUR.persist.log

Ignore this, follow Richard's instructions.

Tom
 
Last edited:
Tom, I did not see any indication in your posts that this was specific to that situation only, or if it's there I missed it. Might be a good idea in the future to flag it that way so other folks doing searches won't ttry to use it. Just a suggestion.

Sorry to have posted bad info though, and thanks for letting me know.
 
Hello Don :)

Sorry to pile a load of stuff onto you. In addition to Tom's advice,and after having installed the System Update Readiness Tool, can you please copy the C:\Windows\Logs\CBS folder to your Desktop (the entire folder, please), right click on it > Send to > Compressed (zipped) folder.

This will also include the CheckSUR.persist.log for Tom.

Then please upload that folder, and I shall have a look to see if you do indeed have a similar problem to dee_can.

Thank you.

Richard
 
Tom and Richard,

I'm in the middle of working on your suggestions now. Thanks for the help. Tom, I tried SURT yesterday without any success. I can download the file but it stops halfway through its installation. I apologize for wasting your time. I forgot about SURT by the time I posted last night.

Screen capture of SURT install:
SURT.JPGUnfortunately, this is the same thing that happened multiple times yesterday. I eventually have to end the installation through Task Manager.


The C:\Windows\Logs\CBS folder and CheckSUR.persist.log are attached as well. Thanks for the tip Richard! Not sure the info in those logs is the most current as I have not run another SFC today. Please let me know if there is any info I can provide.

Also, if it helps, I ran Microsoft's "FixIt," and attached the results in .txt file. Thanks again!
 

Attachments

Hi Rich,

You're right, there isn't, and I'm at fault for that. Thanks, I've already amended my canned accordingly :)


Hi Don,

The more problems that the tool finds, the longer it will take to complete. There is the possibility of it not functioning correctly on your system, but before we go down that route, I would like you to leave the SURT running for a couple of hours. Your log indicates that it is hanging on the component store scan, and it has been cancelled before it has gone to completion. If it still doesn't want to complete after two hours (or so), click Cancel then upload the CBS folder as before please.

Thanks for the FixIt log, I've never come across one of those before but it's quite useful.

Try resetting Windows Update components as well: http://support.microsoft.com/kb/971058

Tom
 
Hi Tom,

SURT finished!!! Most recent CBS log is attached. Trying the update reset now...
 

Attachments

Hi Don,

That's great news, even more so that the System Update Readiness Tool isn't reporting any errors:

No errors detected
Click to expand...

Are you still receiving the same error code when you try and install MSE? Are you installing MSE, or an update for MSE? If the latter, which update?

Tom
 
Hi Tom,

I installed MSE in an attempt to remove/fix the problem yesterday. MSE reported that my PC was "good." However, I was still having issues with 6 security updates for Microsoft Office 2007. Here is a screen capture of one failed attempt to install the updates in question:
MS Office 2007 Security Update.JPG I received error code 8007006E (as pictured). MSE could not solve the issue so I started looking for different options.


Here is another capture of the update history:
6 failed security updates.JPG You can see the 6 MS Office updates that fail and their "KB" numbers.


Bit of a different question here:
I was in the middle of resetting Windows Update components with the help of the link you posted (http://support.microsoft.com/kb/971058) when I received this error message:

Error Message.JPG I was on step 6 (Reregister the BITS files and the Windows Update files.); copying each value on the list into CMD, but stopped when I received the message. Should I continue?

Here is a list to better illustrate my point:

• regsvr32.exe atl.dll .....................successful
• regsvr32.exe urlmon.dll ...................successful
• regsvr32.exe mshtml.dll ...................unsuccessful
• regsvr32.exe shdocvw.dll ....................unsuccessful
• regsvr32.exe browseui.dll .......................unsuccessful
• regsvr32.exe jscript.dll .............. I HAVE NOT ATTEMPTED TO COPY INTO CMD.
• regsvr32.exe vbscript.dll
• regsvr32.exe scrrun.dll
• regsvr32.exe msxml.dll
• regsvr32.exe msxml3.dll
• regsvr32.exe msxml6.dll
• regsvr32.exe actxprxy.dll
• regsvr32.exe softpub.dll


Don
 
Tom,

Downloading updates one at a time failed:

Failed KB2687314 Update.JPG

MSE update failed as well. Twice.

MSE update fail.JPG

I'm sorry to be such a pain. Thank you for your continued patience!
 
Don, you may want to start with "step 6" in the link Tom provided for MSE as manually installing the latest definitions often solves the problem of updating MSE.
 
Is this an accurate description of your MSE installation issues:

Try to install: fails with code.
Try to install again: success
Windows Update now says that "no more updates are available"
You manually click "Check for updates"
It reappears
The cycle repeats.

Is this what occurs?

You appear to have two or even three separate issues here. This is going to take a bit of fixing.

Richard
 
Tom,

MSE updated! I didn't complete all the steps listed because the program updated. Should I?

MSE updated.JPG
 
Hi Corrine,

The problem seems to have fixed itself when I got to "step 2." Should I continue with the rest?

Thanks,
Don
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top