Windows Resource Protection found corrupt files but was unable to fix


  1. Posts : 116
    Win-7 Prof 64bit
       #1

    Windows Resource Protection found corrupt files but was unable to fix


    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.
    Windows Resource Protection found corrupt files but was unable to fix Attached Files
      My Computer


  2. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #2

    Here's the error...
    Code:
    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
      My Computer


  3. Posts : 116
    Win-7 Prof 64bit
    Thread Starter
       #3

    NoelDP said:
    Here's the error...
    Code:
    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.
      My Computer


  4. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #4

    nkaufman said:

    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
      My Computer


  5. Posts : 17
    Windows 7 Ultimate x64
       #5

    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.
      My Computer


  6. Posts : 116
    Win-7 Prof 64bit
    Thread Starter
       #6

    NoelDP said:
    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.
    Windows Resource Protection found corrupt files but was unable to fix Attached Files
      My Computer


  7. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #7

    Yep that looks fine now.
      My Computer


  8. Posts : 116
    Win-7 Prof 64bit
    Thread Starter
       #8

    Thank you for your assistance. marking thread as solved.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 16:13.
Find Us