Windows 10: Weird entries in CBS log after SFC /Scannow

Does anyone know what this is???? I have about 50 of them.

"0000049a Error - Overlap: Duplicate ownership for directory [l:23]"\??\C:\WINDOWS\bcastdvr" in component Microsoft-Media-Capture-Internal-BroadcastDVR, version 10.0.10586.11, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}

Thank you.

:)

 

Windows Update failing

After sfc /scannow I received this message:

"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."

 

windows 10 stuck at 2% for downloading windows update on surface pro 4

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.

the above is the message received after running sfc /scannow as admin from cmd.

 

I see many of these "errors" too for various folders, etc. I just ignore them as Windows seems happy

 

I generally ignore stuff like this, but this has me annoyed

 

It is the final results that matters - (no corruption found) not the process..

 

Background: I just got a brand new Dell laptop with Windows 10 Pro. I started the process of updating drivers / Windows 10 / installing my favorite apps. After about 5 hours of this, somewhere in that process (I have no idea how..) I acquired a virus that modified my Windows dnsapi.dll files (in Windows/System32 and SysWOW64 dirs).

I ran sfc /SCANNOW and it identified the DLL problems along with a slew of "Overlap" errors. It also said that it could not fix any of these problems .

I decided to reinstall Windows via the "reset" windows command, but using the "leave my files" option.

To be safe, I ran sfc /SCANNOW after the re-install. The DLL problems were gone, but the Overlap problems were still there. I can't accept that these are OK to have after feeling it was a virus that caused them. I did some research and found a sequence using DISM that got rid of them:

NOTE: DISM did not work for me without having my own local install.wim source (I have a wim 10 image on a USB stick).

I ran cmd prompt as admin:

Dism /Online /Cleanup-Image /RestoreHealth /source:wim:E:\sources\install.wim:1 /limitaccess

Then I re-ran sfc /SCANNOW. Same Overlap errors, but this time it said it successfully fixed these issues.

I rebooted and re-ran sfc /SCANNOW again. The errors were gone.

 

SFC Scannow and Dism RestoreHealth - Image Health - Repair Corrupt Files