none
sfc /scannow "corrupt files but was unable to fix"

    Question

  • I just tried to run the command "sfc /scannow" on Win8, and although the scan started it seems to have encountered an error. Here is the command line output from the command.

        "Beginning system scan.  This process will take some time.

        Beginning verification phase of system scan.
        Verification 51% complete.

        Windows Resource Protection found corrupt files but was unable to fix some
        of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
        example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
        supported in offline servicing scenarios."

    After reviewing this output i checked the file "windir\Logs\CBS\CBS.log" as instructed, and the following is a snipit from the end of the log file marked as and "ERROR"

    CBS.log:
        2012-12-16 10:37:39, Error                 CSI    0000044b (F) STATUS_OBJECT_NAME_NOT_FOUND #5044386# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags
     = (AllowSharingViolation), handle = {provider=NULL, handle=0, name= ("null")}, da = (SYNCHRONIZE|FILE_READ_ATTRIBUTES), oa = @0x284841c148->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[100]"\??\C:\WINDOWS\WinSxS\amd64_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.6195_none_8a1dd9552ed7f8d8";
     a:(OBJ_CASE_INSENSITIVE)}, iosb = @0x284841c128, as = (null), fa = 0, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = (FILE_SYNCHRONOUS_IO_NONALERT|0x00004000), eab = NULL, eal = 0, disp = Invalid)
        [gle=0xd0000034]
        2012-12-16 10:37:39, Error                 CSI    0000044c@2012/12/16:10:37:39.471 (F) base\wcp\sil\merged\ntu\ntsystem.cpp(2155): Error STATUS_OBJECT_NAME_NOT_FOUND
     originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile expression: (null)
        [gle=0x80004005]
        2012-12-16 10:37:39, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CBS.log to WER report.
        2012-12-16 10:37:39, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20121216054209.log to WER report.
        2012-12-16 10:37:39, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20121216044340.log to WER report.
        2012-12-16 10:37:39, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20121214153023.log to WER report.
        2012-12-16 10:37:39, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20121214000505.cab to WER report.
        2012-12-16 10:37:39, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20121213233126.cab to WER report.
        2012-12-16 10:37:39, Info                  CBS    Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]
        2012-12-16 10:37:39, Info                  CBS    Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
        2012-12-16 10:37:39, Info                  CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
        2012-12-16 10:37:39, Info                  CBS    Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
        2012-12-16 10:37:59, Error                 CSI    0000044d (F) STATUS_OBJECT_NAME_NOT_FOUND #5044385# from Windows::Rtl::SystemImplementation::CDirectory::OpenExistingDirectory(...)[gle=0xd0000034]
        2012-12-16 10:37:59, Error                 CSI    0000044e (F) STATUS_OBJECT_NAME_NOT_FOUND #5044384# from Windows::Rtl::SystemImplementation::CDirectory_IRtlDirectoryTearoff::OpenExistingDirectory(flags
     = 0, da = (SYNCHRONIZE), oa = @0x284841cb80->SIL_OBJECT_ATTRIBUTES {s:40; on:"amd64_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.6195_none_8a1dd9552ed7f8d8"; a:(OBJ_CASE_INSENSITIVE)}, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), oo = (FILE_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT|FILE_OPEN_FOR_BACKUP_INTENT),
     dir = NULL, disp = Invalid)
        [gle=0xd0000034]

    I am unsure on how to proceed and fix this error, in an ideal situation i would like the sfc scan to finish 100% and state that it has fixed all the corrupt files. Could someone please advise me on how to continue.






    • Edited by ResQue1980 Monday, December 17, 2012 12:31 AM spelling
    Sunday, December 16, 2012 9:13 PM

Answers

  • Andre the KB2538242 update did not fix the issue.

    This issue is now closed, i could not fix the issue. In the end i restored an image of a working Win8 install over the top.

    Andre Could you please explain to me why you choose the specific kb2538242, i would like to understand your reasoning to coming to this conclusion to help me out in the future.


    Wednesday, December 19, 2012 4:31 AM

All replies

  • Here is a copy of the whole log file:

    https://skydrive.live.com/redir?resid=889A9BF0380EB2C6!115



    • Edited by ResQue1980 Sunday, December 16, 2012 10:34 PM
    Sunday, December 16, 2012 9:25 PM
  • I think this is similar to your post at the link below......

    Linky


    Be kind and Mark as Answer if I helped.

    Monday, December 17, 2012 4:24 AM
  • Although both questions share the same set of log files and maybe related, the questions are very different in nature. This post is requesting help to resolve an issue with an application error. The second post is requesting more information on one particular file and its use within the operating system, and if it is possible to easily obtain a specific file with a specific version number for use with SxS.

    Monday, December 17, 2012 5:27 AM
  • Try to reinstall this update:

    http://support.microsoft.com/kb/2538242

    If this doesn't fix it, try the new DISM commands:

    http://blogs.technet.com/b/joscon/archive/2012/09/26/fixing-component-store-corruption-in-windows-8-and-windows-server-2012.aspx

    to fix issues that sfc can't fix.


    "A programmer is just a tool which converts caffeine into code"

    Monday, December 17, 2012 5:43 AM
  • Andre the KB2538242 update did not fix the issue.

    This issue is now closed, i could not fix the issue. In the end i restored an image of a working Win8 install over the top.

    Andre Could you please explain to me why you choose the specific kb2538242, i would like to understand your reasoning to coming to this conclusion to help me out in the future.


    Wednesday, December 19, 2012 4:31 AM
  • Andre Could you please explain to me why you choose the specific kb2538242, i would like to understand your reasoning to coming to this conclusion to help me out in the future.

    I've look at the file version. And the version is 8.0.50727.6195 so did a google search and found this update.

    "A programmer is just a tool which converts caffeine into code"

    Wednesday, December 19, 2012 6:07 AM
  • Thank you, issue closed.

    Wednesday, December 19, 2012 8:19 AM