[SOLVED] Errors with sfc /scannow that are all related to ownership

ftblady

Contributor
Joined
Oct 10, 2015
Posts
3
Hello,
New member today
I'm not having any specific problem. OS windows 8.1 64 bit
Ran sfc today - said there were unfixed errors (Windows Resource Protection found corrupt files but was unable to fix some of them.) and the cbs log show tons of the following type - too many to count

2015-10-10 09:37:54, Info CSI 00000901 [DIRSD OWNER WARNING] Directory [ml:520{260},l:56{28}]"\??\C:\WINDOWS\system\Speech" is not owned but specifies SDDL in component Windows-Media-SpeechSynthesis-WinRT, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-10-10 09:37:54, Info CSI 00000902 Ignoring duplicate ownership for directory [l:56{28}]"\??\C:\WINDOWS\system\Speech" in component Windows-Media-SpeechSynthesis-WinRT, Version = 6.3.9600.17415, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral


as well as


2015-10-10 09:38:00, Info CSI 00000907 [SR] Repairing 1 components
2015-10-10 09:38:00, Info CSI 00000908 [SR] Beginning Verify and Repair transaction
2015-10-10 09:38:00, Info CSI 00000909 Hashes for file member \SystemRoot\WinSxS\amd64_prncacla.inf_31bf3856ad364e35_6.3.9600.17415_none_95dd5540d57f8c01\Amd64\CNBJ2530.DPB do not match actual file [l:36{18}]"Amd64\CNBJ2530.DPB" :
Found: {l:32 b:bK+SqCPDem3WnlDfc09mca9zNFtFONzIK8IRQ8dxFew=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}
2015-10-10 09:38:00, Info CSI 0000090a [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.17415, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-10-10 09:38:01, Info CSI 0000090b Hashes for file member \SystemRoot\WinSxS\amd64_prncacla.inf_31bf3856ad364e35_6.3.9600.17415_none_95dd5540d57f8c01\Amd64\CNBJ2530.DPB do not match actual file [l:36{18}]"Amd64\CNBJ2530.DPB" :
Found: {l:32 b:bK+SqCPDem3WnlDfc09mca9zNFtFONzIK8IRQ8dxFew=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}
2015-10-10 09:38:01, Info CSI 0000090c [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.17415, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-10-10 09:38:01, Info CSI 0000090d [SR] This component was referenced by [l:166{83}]"Package_2709_for_KB3000850~31bf3856ad364e35~amd64~~6.3.1.8.3000850-6825_neutral_GDR"
2015-10-10 09:38:01, Info CSI 0000090e [SR] Repair complete


Have not run your SFCFix.exe and perhaps that would solve these ... but thought I would post first

Any ideas?
NormaLee
Fort Bragg, CA
 
Follow up ... found thread regarding the Amd64/CNBJ2530. DPB and ran the SFCFix.exe which corrected that - log results
SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-10-10 11:02:38.791
Microsoft Windows 8.1 Update 3 - amd64
Not using a script file.
AutoAnalysis::
FIXED: Performed DISM repair on file Amd64\CNBJ2530.DPB of version 6.3.9600.17415.
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.
Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2015-10-10 11:38:20.857
----------------------EOF-----------------------
 
Hi ftblady :)

My name is Aura and I'll be assisting you with your issue. "Ownership" lines can be ignored in SFC. They do not change anything in the way your system works and aren't worthy of attention, on top of the fact that are they are simply "warnings" and not "fatal" errors. As for your corrupt file, it seems like SFCFix indeed fixed it. Shall we run SFC again to confirm that? :)

EndqYRa.png
System File Checker (SFC)
Follow the instructions below to run a SFC scan on your system and to provide the CBS log in your next reply;
  • On Windows Vista & 7, click on the Windows Start Menu, then enter cmd in the search box, right-click on the cmd icon and select
    Spcusrh.png
    Run as Administrator
  • On Windows 8, drag your cursor in the bottom-left corner, and right-click on the metro menu preview, then select Command Prompt (Admin);
  • On Windows 8.1, right click on the Windows logo in the bottom-left corner and select Command Prompt (Admin);
  • Enter the command below and press on Enter;
    Code:
    sfc /scannow
    Note: There's a space between "sfc" and "/scannow";
  • Once the scan is complete, enter the command below and press on Enter
    Code:
    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  • A file called cbs.txt will have appeared on your Desktop. Upload the file on Dropbox, Google Drive or OneDrive and post the download URL for it here;
Note: Please note that the CBS.log is volatile, which means that if you don't upload it after the SFC scan is completed, it won't have the information from the scan anymore. So archive it and upload it as soon as you can.
 
Ran the sfc again and only the ownership errors now ... I guess I will just ignore since that's what the sfc seems to do. Thanks for the support.
NormaLee
Fort Bragg, CA
 
No problem NormaLee, you're welcome :)
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top