Clean install W10 20H2 showed up sfc errors?

Probably not the best time of year to be posting, so I'll keep it short

Is it possible to carry out a clean install of W10 (ver. 20H2) on a PC and run SFC without it finding faults to fix / repair?
I have tried doing so twice now, but have not been successful. The first time this happened I was rather surprised to say the least. I was expecting no errors to be found from a clean install. I followed the very helpful instructions on this forum, many thanks for the advice there.

It's a brand new PC, I added my own OS.
Motherboard: Asus Prime B450M-A
CPU: AMD Ryzen 5 3400g
RAM: 16GB (2 x 8 sticks) Gammix D10 3200Hz

Thanks in advance.
Merry Christmas.

Chris S said:

Is it possible to carry out a clean install of W10 (ver. 20H2) on a PC and run SFC without it finding faults to fix / repair?

There are times in which it is not possible until hash mismatches are fixed.
This had happened many months ago and was resolved by Windows updates.
It was related to Microsoft defender.

https://support.microsoft.com/en-us/...s-as-corrupted

Chris S said:

Is it possible to carry out a clean install of W10 (ver. 20H2) on a PC and run SFC without it finding faults to fix / repair?

Lance1 said:

Open a Command Prompt as Admin. copy and past this command in: findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"...

That command filters the CBS.log to extract all the reports from SFC of corrupt system resources that could (or sometimes could not) be repaired. I suspect for your clean install you won't find any.

However, there is one issue that SFC may report as found and fixed that is not a system resource corruption. It does not appear in CBS.log as an [SR] error, rather it's just a warning that the owner of a folder was set twice. The ownership issue is trivial error, as its the correct owner that's been set - it's just that it's been set twice.

For these search the CBS.log for the string Warning: Overlap:

Some examples here: File History recent troubles mystify - post #5

Many thanks for your quick replies, I'm amazed, with it being Christmas eve.

I should probably add the SFC repaired the found issue(s). I just felt they shouldn't have been there in the first place with the clean install.

My apologies to dalchina for not adding the OS Build Number. It is: 19042.685.

Thanks for the links, I'll have a look at them. I did do a search before posting and I found one issue with Defender, but that was for earlier W10 builds some years ago.

I hope I have done right by attaching the note pads, if not please let me know.

Many thanks for taking the time to reply, very much appreciated.

- - - Updated - - -

Bree said:

That command filters the CBS.log to extract all the reports from SFC of corrupt system resources that could (or sometimes could not) be repaired. I suspect for your clean install you won't find any.

However, there is one issue that SFC may report as found and fixed that is not a system resource corruption. It does not appear in CBS.log as an [SR] error, rather it's just a warning that the owner of a folder was set twice. The ownership issue is trivial error, as its the correct owner that's been set - it's just that it's been set twice.

For these search the CBS.log for the string Warning: Overlap:

Some examples here: File History recent troubles mystify - post #5

Your link shows exactly that in the CBS.log Warning: Overlap:

Chris S said:

....exactly that in the CBS.log Warning: Overlap:

In that case the clean install would have been fully functional with no effects at all from the double ownership, even if you hadn't fixed it with SFC.

I don't know what causes the ownership to be set twice, lax programming by Microsoft? I've seen it before after a few (but not all) updates. It's a non-problem, just an annoyance that MS let it happen. Nothing to worry about, especially now SFC has fixed it.

Bree said:

In that case the clean install would have been fully functional with no effects at all from the double ownership, even if you hadn't fixed it with SFC.

I don't know what causes the ownership to be set twice, lax programming by Microsoft? I've seen it before after a few (but not all) updates. It's a non-problem, just an annoyance that MS let it happen. Nothing to worry about, especially now SFC has fixed it.

You have restored some of my confidence, in-as-much it appears it's not something I got wrong with the OS clean install, so I appreciate that. Although it would have been great to have sfc find no errors at that point, obviously I expect too much

Many thanks for your very quick reply.

Hi,
Funny this nonsense is still going on.