locked
SFC fails, errors in CBS.log RRS feed

  • Question

  • Hi,

    My system file check scan consistently fails at 40%. These are the errors in the CBS.log. Is anyone able to help me diagnose please?

    2016-06-15 12:40:17, Info                  CSI    00000153 [SR] Beginning Verify and Repair transaction
    2016-06-15 12:40:18, Error                 CSI    00000154 (F) c0000279 [Error,Facility=(system),Code=633 (0x0279)] #4650730# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = (AllowFileNotFound|AllowSharingViolation|AllowAccessDenied), handle = {provider=NULL, handle=0, name= ("null")}, da = (FILE_GENERIC_READ|0x01000000), oa = @0xb5bc69ba40->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[48]"\??\C:\Windows\System32\en-GB\pcsvDevice.dll.mui"; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0xb5bc69baa0, as = (null), fa = 0, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = (FILE_NON_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT|0x00004000), eab = NULL, eal = 0, disp = Invalid)
    [gle=0xd0000279]
    2016-06-15 12:40:18, Error                 CSI    00000155@2016/6/15:02:40:18.683 (F) base\wcp\sil\merged\ntu\ntsystem.cpp(2155): Error c0000279 [Error,Facility=(system),Code=633 (0x0279)] originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile expression: (null)
    [gle=0x80004005]
    2016-06-15 12:40:18, Info                  CBS    Added C:\Windows\Logs\CBS\CBS.log to WER report.
    2016-06-15 12:40:18, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20160615022703.log to WER report.
    2016-06-15 12:40:18, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20160614234947.log to WER report.
    2016-06-15 12:40:18, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20160613231718.log to WER report.
    2016-06-15 12:40:18, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20160613115538.log to WER report.
    2016-06-15 12:40:18, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20160613053548.cab to WER report.
    2016-06-15 12:40:18, Info                  CBS    Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]
    2016-06-15 12:40:18, Info                  CBS    Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2016-06-15 12:40:18, Info                  CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2016-06-15 12:40:18, Error                 CSI    00000156 (F) c0000279 [Error,Facility=(system),Code=633 (0x0279)] #4650729# from Windows::Rtl::SystemImplementation::CDirectory::OpenExistingFile(...)[gle=0xd0000279]
    2016-06-15 12:40:18, Error                 CSI    00000157 (F) c0000279 [Error,Facility=(system),Code=633 (0x0279)] #4650728# from Windows::Rtl::SystemImplementation::CDirectory_IRtlDirectoryTearoff::OpenExistingFile(flags = (MissingFileIsOk|SharingViolationIsOk|AccessDeniedIsOk), da = (FILE_GENERIC_READ|0x01000000), oa = @0xb5bc69c070->SIL_OBJECT_ATTRIBUTES {s:40; on:"pcsvDevice.dll.mui"; a:(OBJ_CASE_INSENSITIVE)}, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), oo = (FILE_SYNCHRONOUS_IO_NONALERT|FILE_NON_DIRECTORY_FILE|FILE_OPEN_FOR_BACKUP_INTENT), file = NULL, disp = Invalid)
    [gle=0xd0000279]
    2016-06-15 12:40:18, Error                 CSI    00000158 (F) c0000279 [Error,Facility=(system),Code=633 (0x0279)] #4650720# from CFileInstaller::ValidateFileHashAgainstCDF(...)[gle=0xd0000279]
    2016-06-15 12:40:18, Error                 CSI    00000159 (F) c0000279 [Error,Facility=(system),Code=633 (0x0279)] #4650659# from CFileInstaller::DoComponentOperation(...)[gle=0xd0000279]
    2016-06-15 12:40:18, Error                 CSI    0000015a (F) c0000279 [Error,Facility=(system),Code=633 (0x0279)] #4650658# from PrimitiveInstaller::CCoordinator::RepairComponent(Component = Microsoft-DeviceProxy-WMIv2-Provider.Resources, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-GB", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral)[gle=0xd0000279]

    I have run the DISM utility and it claims things are fixed, but still SFC fails. Thanks! 

    I have also run sfc in safe mode and the same thing happens. chkdsk shows no errors.



    • Edited by Cindernat Wednesday, June 15, 2016 4:50 AM
    Wednesday, June 15, 2016 3:10 AM

All replies

  • Hi Cindernat,

     

    I noticed that you also run sfc in safe mode but still failed. I suppose that it may be caused by malware, we could perform a full scan and check the result.

     

    The System Update Readiness tool may be a good idea, please try it.

    https://support.microsoft.com/en-sg/kb/947821#bookmark-checksur

     

    In addition, this article may help you, please refer to the link:

    How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe) program generates

    https://support.microsoft.com/en-sg/kb/928228

     

    Best Regards,

    Tao


    Please mark the reply as an answer if you find it is helpful.

    If you have feedback for TechNet Support, contact tnmff@microsoft.com

    Thursday, June 16, 2016 11:33 AM
  • Hi Tao,

    I have Malwarebytes (premium) and RogueKiller (premium) and they both report the system is clean.

    I have also run the SUR tool and it did fix about 4 items, but the sfc /scannow problem still crashes out at 40.

    In my CBS.log I don't have any 'SR' (strings) with error messages. That's why I pasted in the actual error messages in my original post because there are not a typical error message about not being able to repair a file.

    This is why I need the experts :)

    Friday, June 17, 2016 12:42 AM
  • Hi,

    We haven't heard from you in a couple of days, have you solved the problem? We are looking forward to your good news.

    Best Regards,

    Tao


    Please mark the reply as an answer if you find it is helpful.

    If you have feedback for TechNet Support, contact tnmff@microsoft.com

    Tuesday, June 21, 2016 8:20 AM
  • No I haven't, because you didn't reply to my last response.
    Wednesday, June 22, 2016 4:13 AM