HELP!! WINDOWS RESOURCE PROTECTION FOUND CORRUPT FILES UNABLE TO FIX (SFC SCANNOW)

STR8ARROW · May 3, 2013

Hi -
I need help desperately.

I ran SFC Scannow because I am having difficulty installing programs. I received a message that Windows Resource Protection found corrupt files that it was unable to fix.

I found the following in the CBS.log

2013-05-03 17:02:58, Info CBS Reboot mark refs incremented to: 1
2013-05-03 17:02:58, Info CBS Scavenge: Starts
2013-05-03 17:02:58, Info CSI 0000000a CSI Store 3734784 (0x0038fd00) initialized
2013-05-03 17:02:58, Info CSI 0000000b@2013/5/3:21:02:58.905 CSI Transaction @0x3f6ef0 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000002 and client id [10]"TI6.0_0:0/"

2013-05-03 17:02:58, Info CBS Scavenge: Begin CSI Store
2013-05-03 17:02:59, Info CSI 0000000c Performing 1 operations; 1 are not lock/unlock and follow:
Scavenge (8): flags: 00000017
2013-05-03 17:02:59, Info CSI 0000000d Store coherency cookie matches last scavenge cookie, skipping scavenge.
2013-05-03 17:02:59, Info CSI 0000000e ICSITransaction::Commit calling IStorePendingTransaction::Apply - coldpatching=FALSE applyflags=7
2013-05-03 17:02:59, Info CSI 0000000f Creating NT transaction (seq 2), objectname [6]"(null)"
2013-05-03 17:02:59, Info CSI 00000010 Created NT transaction (seq 2) result 0x00000000, handle @0x1e8
2013-05-03 17:02:59, Info CSI 00000011@2013/5/3:21:02:59.615 CSI perf trace:
CSIPERF:TXCOMMIT;388240
2013-05-03 17:02:59, Info CBS Scavenge: Completed, disposition: 0X1
2013-05-03 17:02:59, Info CSI 00000012@2013/5/3:21:02:59.616 CSI Transaction @0x3f6ef0 destroyed
2013-05-03 17:02:59, Info CBS Reboot mark refs: 0
2013-05-03 17:02:59, Info CBS Idle processing thread terminated normally
2013-05-03 17:02:59, Info CBS Ending the TrustedInstaller main loop.
2013-05-03 17:02:59, Info CBS Starting TrustedInstaller finalization.
2013-05-03 17:03:00, Info CBS Ending TrustedInstaller finalization.

I tried the following:
1 - I reran the SFC Scannow command in SAFE MODE - same result.
2- I restored the computer to an earlier time to see if perhaps that would remedy the problem - it did not.
3 - I tried installing the Windows System Update Readiness Tool (DOWNLOAD FROM
Download System Update Readiness Tool for Windows 7 (KB947821) [February 2013] from Official Microsoft Download Center --> System Update Readiness Tool fixes Windows Update errors in Windows 8, Windows 7, Windows Vista, Windows Server 2008 R2, and Windows Server 2008).
4- I restored the computer (to restore it to the original state, prior to #2, above). I ran SFC Scannow and I'm getting the same problem (as expected - I just undid the earlier restore, as it was ineffective).

I keep getting the same error. I don't know how to fix it. Could someone please help???

Thanks so much.
str8arrow

View attachment CBS.zip

NoelDP · May 5, 2013

There is only the one error in the SFC results...

Code:

 Line 58283: 2013-05-03 15:36:19, Info                  CSI    000001a9 [SR] Repairing 1 components
 Line 58284: 2013-05-03 15:36:19, Info                  CSI    000001aa [SR] Beginning Verify and Repair transaction
 Line 58287: 2013-05-03 15:36:19, Info                  CSI    000001ac [SR] Cannot repair member file [l:22{11}]"termsrv.dll" of Microsoft-Windows-TerminalServices-RemoteConnectionManager, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

I'll post a fix protocol for it a little later - but we also need to see the results of the CheckSUR tool.
Please attach the CheckSUR.log file to your next post. (found in the same folder as the CBS.log)

NoelDP · May 5, 2013

I've uploaded a file - s8aaa.zip - to my SkyDrive at Noel's SkyDrive

Please download and save it.

Right-click on the saved file and select Extract all...

Change the target to C:\ and click on Extract

Close all windows (it would be a good idea to print these instructions!)

Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'

Pick that

You'll have to log in with your username and password.

Pick the option to use a Command Prompt

At the prompt type

DIR C:\s8aaa

hit the enter key - if you get a 'Not Found' error try

DIR D:\s8aaa
or
DIR E:\s8aaa

The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...

XCOPY <drive>:\s8aaa <drive>:\windows\winsxs /y /i /s /v /h

(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )

run the command (it should take almost no time) and when the prompt returns, type

EXIT

and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in an Elevated Command Prompt

then reboot and upload the new CBS.log file to your reply

Search

Search

HELP!! WINDOWS RESOURCE PROTECTION FOUND CORRUPT FILES UNABLE TO FIX (SFC SCANNOW)

STR8ARROW

New member

NoelDP

Windows Update Analyst, Contributor

NoelDP

Windows Update Analyst, Contributor