Help understanding CBS.log file paths


  1. Posts : 2
    Windows 7 64bit
       #1

    Help understanding CBS.log file paths


    So I've been trying to use system file checker, and encountered a problem where it can't repair a file. I found this page detailing how to manually fix the problem:

    Use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7

    I was fine until step 2, where it says

    "For example, type takeown /f E:\windows\system32\extremely_simplified_example.dll"

    The problem is, my CBS.log file says stuff like:

    Cannot repair member file [l:24{12}]"FWPKCLNT.SYS"
    Unable to repair \SystemRoot\WinSXS\Manifests\\[l:24{12}]"FWPKCLNT.SYS"

    and I don't know how to translate that into a path to use with the takeown command. I searched for that file using explorer and found a dozen different copies, so I'm not sure which one to replace.

    Semi-related questions: Can I just replace them all? I'm planning on using a copy of the file from a similar system that works, is that ok?

    Thanks!
      My Computer


  2. Posts : 72,037
    64-bit Windows 11 Pro for Workstations
       #2

    Hello Southbound, and welcome to Seven Forums.

    Those instructions there are fine, but just a bit vague. OPTION THREE in the tutorial below can help give you only the SFC results to help make it easier to go through.
    Next, the tutorial below can show you how to extract files from your installation disc to replace any listed files that SFC cannot repair.
    Before doing anything, please post back and upload your sfcdetails.txt file to see what all may be wrong, and if it any file that cannot be repaired is worth worrying about.
    To help interrupt what it says to know the path:
    Cannot repair member file [l:24{12}]"FWPKCLNT.SYS"
    Unable to repair \SystemRoot\WinSXS\Manifests\\[l:24{12}]"FWPKCLNT.SYS"
    The first line says that SFC cannot repair the FWPKCLNT.SYS file.

    The second line is the path of the file. "SystemRoot" is a variable "%SystemRoot%" that is actually just a shortcut for "C:\Windows". This leaves you with the file path as:
    C:\Windows\WinSXS\Manifests\FWPKCLNT.SYS
    Doing a search on the C: drive for the listed FWPKCLNT.SYS file would help give you all of it's locations if needed as well.

    Hope this helps for now, :)
    Shawn
    Last edited by Brink; 11 Mar 2013 at 22:44. Reason: typo
      My Computer


  3. Posts : 2
    Windows 7 64bit
    Thread Starter
       #3

    Thanks for the reply!

    After making sfcdetails.txt I gave it a glance, and noticed that it referenced "C:\Windows\System32\drivers" in addition to some other system folders I had no experience with. Since the trouble I was having did seem to be driver related, I threw a copy of FWPKCLNT.SYS into the drivers folder, restarted, and the problem was solved.

    Regarding this:

    To help interrupt what it says to know the path:

    Cannot repair member file [l:24{12}]"FWPKCLNT.SYS"
    Unable to repair \SystemRoot\WinSXS\Manifests\\[l:24{12}]"FWPKCLNT.SYS"

    The first line says that SFC cannot repair the FWPKCLNT.SYS file.

    The second line is the path of the file. "SystemRoot" is a variable "%SystemRoot%" that is actually just a shortcut for "C:\Windows". This leaves you with the file path as:

    C:\Windows\WinSXS\Manifests\FWPKCLNT.SYS
    I can just ignore the whole "\[l:24{12}]" part? I mentioned that line specifically because the Manifests folder seemed to contain almost nothing but .manifest files, and didn't seem like the right place for FWPKCLNT.SYS.

    I was probably giving you an incomplete picture with just those lines anyway. I've attached the sfcdetails.txt file in case anyone is curious. Thanks again for the help!
    Help understanding CBS.log file paths Attached Files
      My Computer


  4. Posts : 72,037
    64-bit Windows 11 Pro for Workstations
       #4

    Great news.

    I can't remember exactly what it is, but yeah you can just ignore the "\[l:24{12}]" part.
      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 11:02.
Find Us