Solved Windows Resource Protection found corrupt files but was unable to fix

[nkaufman]

Hello,

ran sfc and got the following:
--Begin-------
Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some of th
em.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log
---End ------

ran the following in cmd prompt
C:\Windows\system32>findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\
Desktop\sfcdetails.txt"

Attached is the sfcdetails file.

Thank you for your assistance in resolving this issue.

 

[NoelDP]

Here's the error...

2015-09-22 19:27:48, Info                  CSI    0000035e [SR] Repairing 1 components
2015-09-22 19:27:48, Info                  CSI    0000035f [SR] Beginning Verify and Repair transaction
2015-09-22 19:27:52, Info                  CSI    00000361 [SR] Cannot repair member file [l:38{19}]"NlsLexicons0024.dll" of Microsoft-Windows-NaturalLanguage6, Version = 6.1.7601.17514, 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

I'll post a fix protocol later

 

[nkaufman]

Here's the error...

2015-09-22 19:27:48, Info                  CSI    0000035e [SR] Repairing 1 components
2015-09-22 19:27:48, Info                  CSI    0000035f [SR] Beginning Verify and Repair transaction
2015-09-22 19:27:52, Info                  CSI    00000361 [SR] Cannot repair member file [l:38{19}]"NlsLexicons0024.dll" of Microsoft-Windows-NaturalLanguage6, Version = 6.1.7601.17514, 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

I'll post a fix protocol later

Thank you very much for looking into this. Will wait for your fix.

 

[NoelDP]

Thank you very much for looking into this. Will wait for your fix.

I've uploaded a file - nkfaa.zip - to my OneDrive at Noel's OneDrive
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:\nkfaa
hit the enter key - if you get a 'Not Found' error try
DIR D:\nkfaa
or
DIR E:\nkfaa



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



XCOPY <drive>:\nkfaa <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

 

[Joseph182]

More than one antivirus working in a single system is also creating more issues.Because all of them using some static files from the system at a time for updation.ESSET is first class one and Spybot is more inner depth use.It can use in some critical situations.

 

[nkaufman]

I've uploaded a file - nkfaa.zip - to my OneDrive at Noel's OneDrive
Please download and save it.
.....

Thank you for your assistance.

SFC worked fine. No errors.

Attached is the sfcdetails log.

Thank you again.

 

[NoelDP]

Yep that looks fine now.

 

[nkaufman]

Thank you for your assistance. marking thread as solved.