[Solved] SFC verification error

Discussion in 'Windows 8' started by adric, Dec 7, 2020.

  1. adric

    adric MDL Expert

    Jul 30, 2009
    1,385
    1,498
    60
    #1 adric, Dec 7, 2020
    Last edited: Dec 7, 2020
    Anyone know how to fix the errors below after running SFC?
    DISM.exe /Online /Cleanup-image /Scanhealth reports no corruption in the component store
    Code:
    "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\.log. Note that logging is currently not
    supported in offline servicing scenarios."
    
    CBS.log (partial)
    Code:
    2020-12-07 18:15:14, Info                  CSI    00000a2a [SR] Verify complete
    2020-12-07 18:15:14, Info                  CSI    00000a2b [SR] Repairing 1 components
    2020-12-07 18:15:14, Info                  CSI    00000a2c [SR] Beginning Verify and Repair transaction
    2020-12-07 18:15:14, Error                 CSI    00000a2d@2020/12/7:17:15:14.489 (F) base\wcp\library\delta_library.cpp(287): Error NTSTATUS_FROM_WIN32(ERROR_INVALID_DATA) originated in function Windows::Rtl::DeltaDecompressBuffer expression: g_pfnApplyDeltaB(( (DELTA_FLAG_TYPE)0x00000000 ), ReferenceInput, CompressedInput, &UncompressedOutput)
    [gle=0x80004005]
    2020-12-07 18:15:14, Info                  CBS    Added C:\Windows\Logs\CBS\CBS.log to WER report.
    2020-12-07 18:15:14, Info                  CBS    Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]
    2020-12-07 18:15:14, Info                  CBS    Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2020-12-07 18:15:14, Info                  CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2020-12-07 18:15:14, Info                  CBS    Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2020-12-07 18:15:14, Error                 CSI    00000a2e (F) Failed on regenerating file [l:18{9}]"MSDTC.LOG"[gle=0x80004005]
    2020-12-07 18:15:14, Info                  CSI    00000a2f [SR] Cannot repair member file [l:18{9}]"MSDTC.LOG" of Microsoft-Windows-COM-DTC-Runtime, Version = 6.3.9600.17415, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file cannot be decompressed
    2020-12-07 18:15:14, Error                 CSI    00000a30@2020/12/7:17:15:14.536 (F) base\wcp\library\delta_library.cpp(287): Error NTSTATUS_FROM_WIN32(ERROR_INVALID_DATA) originated in function Windows::Rtl::DeltaDecompressBuffer expression: g_pfnApplyDeltaB(( (DELTA_FLAG_TYPE)0x00000000 ), ReferenceInput, CompressedInput, &UncompressedOutput)
    [gle=0x80004005]
    2020-12-07 18:15:14, Info                  CBS    Added C:\Windows\Logs\CBS\CBS.log to WER report.
    2020-12-07 18:15:14, Info                  CBS    Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]
    2020-12-07 18:15:14, Info                  CBS    Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2020-12-07 18:15:14, Info                  CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2020-12-07 18:15:14, Info                  CBS    Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2020-12-07 18:15:14, Error                 CSI    00000a31 (F) Failed on regenerating file [l:18{9}]"MSDTC.LOG"[gle=0x80004005]
    2020-12-07 18:15:14, Info                  CSI    00000a32 [SR] Cannot repair member file [l:18{9}]"MSDTC.LOG" of Microsoft-Windows-COM-DTC-Runtime, Version = 6.3.9600.17415, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file cannot be decompressed
    2020-12-07 18:15:14, Info                  CSI    00000a33 [SR] This component was referenced by [l:164{82}]"Package_929_for_KB3000850~31bf3856ad364e35~amd64~~6.3.1.8.3000850-2734_neutral_GDR"
    2020-12-07 18:15:14, Info                  CSI    00000a34 [DIRSD OWNER WARNING] Directory [ml:520{260},l:58{29}]"\??\C:\Windows\System32\Msdtc" is not owned but specifies SDDL in component Microsoft-Windows-COM-DTC-Runtime, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
    
    2020-12-07 18:15:14, Info                  CSI    00000a35 [SR] Repair complete
    2020-12-07 18:15:14, Info                  CSI    00000a36 [SR] Committing transaction
    2020-12-07 18:15:14, Info                  CSI    00000a37 Creating NT transaction (seq 2), objectname [6]"(null)"
    2020-12-07 18:15:14, Info                  CSI    00000a38 Created NT transaction (seq 2) result 0x00000000, handle @0xd7c
    2020-12-07 18:15:14, Info                  CSI    00000a39@2020/12/7:17:15:14.677 Beginning NT transaction commit...
    2020-12-07 18:15:14, Info                  CSI    00000a3a@2020/12/7:17:15:14.692 CSI perf trace:
    CSIPERF:TXCOMMIT;14254
    2020-12-07 18:15:14, Info                  CSI    00000a3b [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired
    2020-12-07 18:17:15, Info                  CBS    Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
    2020-12-07 18:17:15, Info                  CBS    TiWorker signaled for shutdown, going to exit.
    2020-12-07 18:17:15, Info                  CBS    Ending the TiWorker main loop.
    2020-12-07 18:17:15, Info                  CBS    Starting TiWorker finalization.
    2020-12-07 18:17:15, Info                  CBS    Ending the TrustedInstaller main loop.
    2020-12-07 18:17:15, Info                  CBS    Starting TrustedInstaller finalization.
    2020-12-07 18:17:15, Info                  CBS    Ending TrustedInstaller finalization.
    2020-12-07 18:17:15, Info                  CBS    Ending TiWorker finalization.
    
     
  2. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    17,209
    90,791
    340
    Maybe extract the file from Update 3 ISO, and use NSudo to copy it to WinSxS folder
     
  3. donmiller

    donmiller MDL Addicted

    Jun 4, 2016
    800
    490
    30
    Ordinarily, when I encounter SFC errors that cannot be repaired, I run a DISM to RestoreHealth followed by another SFC /Scannow. But you've already ran a ScanHealth and received no report of corruption. Under these circumstances, I suggest an In-Place Upgrade.
     
  4. adric

    adric MDL Expert

    Jul 30, 2009
    1,385
    1,498
    60
    #4 adric, Dec 7, 2020
    Last edited: Dec 7, 2020
    (OP)
    do you mean MSDTC.log from the u3 install.wim?
     
  5. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    17,209
    90,791
    340
    Yes
    Code:
    \Windows\WinSxS\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.17415_none_0a5dfdcc33c06e7e\MSDTC.LOG
    
    \Windows\System32\MsDtc\MSDTC.LOG
    the two files are different
     
  6. adric

    adric MDL Expert

    Jul 30, 2009
    1,385
    1,498
    60
    #6 adric, Dec 7, 2020
    Last edited: Dec 8, 2020
    (OP)
    Good call abbodi1406 :clap3: SFC came up clean. I have another SFC problem with W7, but I can't
    figure out what the error is.:dunno:. I'll start another thread on the Win7 forum.
     
  7. adric

    adric MDL Expert

    Jul 30, 2009
    1,385
    1,498
    60
    Well, it turns out that on Win7, the MSDTC.log file wasn't there at all , so I copied it from my W7 install.wim and that fixed SFC too. I'm not sure how it got deleted, but I suspect Dism++ may have had something to do with it removing expired files from winsxs.
     
  8. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    17,209
    90,791
    340
    MSDTC.LOG has been always a weird file
     
  9. adric

    adric MDL Expert

    Jul 30, 2009
    1,385
    1,498
    60
    FYI, I just checked the MSDT.log file from the u1 install.wim and it's the same as the one in the u3 install.wim