Windows 10: System File Checker found problems.

Hi, I spend the last week discovering my new computer. Updating some drivers, downloading some software, things here and there. The computer is not slow. Sometimes it shows compatibility problems with some software and games, like every Windows 10 user seem to have in the start.
But what got me was the internet. (THIS IS NOT AN INTERNET PROBLEM) It performs in an acceptable way. Not slow, not fast. I decided to run a scf scan to see if anything was happening since other computers had a much faster Wi-Fi than me.

It showed me this message:
--------------------//
Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

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

I got a little scared so I decided to check the Log. But I don't know how to read those thousands of lines.
Can someone tell me from the CBS log what is wrong and how to fix it? Thanks.

:)

 

System File Checker found corrupted files and not able to fix them on Windows 10

Care to tell us the underlying issue?

What do you mean by "no use"?

 

System File Checker found corrupted files and not able to fix them on Windows 10

Old title: sfc /scannow command fails fix currepted file

Dear Sir,

sfc /scannow command shows the following result

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.

DISM command also no use

Please help me.

 

Restart your machine
Run SFC /scannow again


The 'errors' are related to two WU
KB3147458
KB3140743

Both are cumalative updates and both were known to cause issues - although your machine isn't hanging, unable to boot, or unable to logon - right?
So these are minor nuisance affects.
There 'errors' all point to sound files, not important system files