Member Avatar for nadiam

Hi. i ran a SFC /SCANNOW on my laptop(Asus, Windows 8.1) and there are corrupt files according to cmd. Checked the CBS log file and found multiple DIRSD OWNER WARNING , Ignoring duplicate ownership for directory AND [SR] Cannot repair member file [l:36{18}] . Could someone explain to me what the first one means? I mean if its possible to fix all three problems, how? I guess, if you see the whole log then only you'd know how to help but theres like dozens of lines (crazy to copy paste all that). So how do i proceed? maybe i'll attach it? is that safe? is the log safe to share to public?

  • 2 Contributors
  • 1 Reply
  • 433 Views
  • 48 Minutes Discussion Span
  • Latest Post Latest Post by rproffitt

Dani AI

Generated

Short answer and focus

ran System File Checker and saw lots of directory-owner warnings plus a few files that SFC could not fix. Those directory-owner lines are informational: they mean a component manifest expects an SDDL (security descriptor) for a folder but the filesystem entry didn’t show an owner — common and often not the immediate cause of breakage. The important items are the entries where SFC says it could not replace a file; those need repair. This echoes ’s advice to concentrate on what’s actually failing. Microsoft guidance on SFC/DISM and community discussion about these warnings. (learn.microsoft.com)

Straightforward recovery steps

  1. From an elevated command prompt run the DISM repair command, then rerun SFC. Example commands:
    DISM.exe /Online /Cleanup-Image /RestoreHealth
sfc /scannow

    If DISM can’t contact Windows Update, give it a local repair source (replace the path with your install media or mounted ISO):

    DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccess

    These are the Microsoft-recommended first steps. (support.microsoft.com)

If SFC still reports unrepairable files

Create a trimmed report and examine only the SFC lines:

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

For each unrepaired file follow the documented manual-replace steps: take ownership, grant Administrators full control, copy a known-good file from install media or another identical system, then re-run SFC. Commands (use the exact paths you find in sfcdetails.txt):

takeown /f <Path_And_File_Name>
icacls <Path_And_File_Name> /grant administrators:F
copy <Source_File> <Destination_File>
sfc /scannow

Also run a disk check first (example):

chkdsk C: /f /r

This sequence and the file-replacement steps are described by Microsoft. (support.microsoft.com)

When to escalate

If many files remain unrepaired or the OS is unstable, an in-place repair (repair install / refresh) or a reset/reinstall is the practical next step — Microsoft documents how to do a repair in-place and how Refresh/Reset work. If you want help pasting logs, share only the sfcdetails.txt excerpt (it’s safe to publish paths and SR lines but may reveal installed software names), not the entire CBS.log. (learn.microsoft.com)

Summary checklist: run DISM → run SFC → extract sfcdetails.txt → manually replace listed files (takeown/icacls/copy) → chkdsk → consider repair install if needed.

Member Avatar for rproffitt

As I read priors at https://www.google.com/search?q=DIRSD+OWNER+WARNING I'll add I won't duplicate the answers there.

Now that the SFC part of your question is answered can you share what issues the OS is showing otherwise?

That is, because of how Microsoft treats issues like these, it is OK to see the entries in the log file and have a working OS. Drop the concerns about the log file for a moment and tell me what's broken. We know Microsot's penchant for less than a clean SFC is well discussed so I want to focus on what's broken elsewhere. If you are going to complain about Microsoft OS bugs, you're in good company.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.