Win 10 sfc scannow result

[dvtrv]

Windows Resource Protection found corrupt files but was unable to fix some of them.

I've tried running sfc in safe mode and get the same result.

Please can anyone assist me in fixing these?

Thanks

 

[Billb2]

Pretty much if Windows can't fix the files they've gone to "bit heaven"

The best you can do is to use Windows Repair if they're windows files, reinstall programs if they're program files, and if they're data files restore form you backup.

 

[bbhaag]

Right click on the start button and click on Command Prompt (Admin). When the cmd window opens paste this command and press enter

Dism /Online /Cleanup-Image /RestoreHealth

Let Dism repair and replace any corruption in the component store then restart your computer and run sfc /scannow and see if the corruption was repaired.

 

[dvtrv]

I followed as per your suggestion, thank you for that, but same response from sfc /scannow

Any suggestions.

Right click on the start button and click on Command Prompt (Admin). When the cmd window opens paste this command and press enter

Dism /Online /Cleanup-Image /RestoreHealth

Let Dism repair and replace any corruption in the component store then restart your computer and run sfc /scannow and see if the corruption was repaired.

 

[Elixer]

Is this a SSD or HD?
What does SMART health show on your boot device? (Use crystaldiskinfo [free] to check)
Also, list the files that are corrupted from the log.

 

[bbhaag]

Can you please post your Dism log. It can be found at C:\Windows\Logs\DISM It will be a simple .txt file. It would be helpful if you posted your CBS log to. It can be found at C:\Windows\Logs\CBS

 

[dvtrv]

Not sure re you SSD HD q but i'm using a Dell Inspiron 3521 Core i3

I tried to add both logs by copying and pasting but they are too big.
I'm not sure how to attach as file either.

Your advice please and thank you o far for your assistance

 

[Ketchup]

What actual problems are having, aside from these scan results?

 

[PliotronX]

About 1 in 5 times I see this, this is fixed by disabling the page file, rebooting and running SFC, and enabling the page file again. If you look through the CBS log, it is helpful in finding what its complaining about. If you use an automated cleanup program, it can remove redundant system files which do nothing but take up space (like language packs) but produce SFC failures. Also on domain machines with a WSUS server, it will fail just about every time because you have to set in local group policy to check Microsoft update servers for optional components and repair.