Is it "normal" for SFC to need to repair files after upgrading or installing Windows?

Sammy888 · Feb 12, 2022

I installed several different images and I also installed W11 from scratch. Each time I finish, I reboot my laptop and I run SFC. There are errors found. This even occurs with the default OEM Lenovo laptop image and a "recovery" installation from USB.

,

Ghot · Feb 12, 2022

Sammy888 said:
I installed several different images and I also installed W11 from scratch. Each time I finish, I reboot my laptop and I run SFC. There are errors found. This even occurs with the default OEM Lenovo laptop image and a "recovery" installation from USB.

,

It really doesn't matter, as long as SFC can fix the errors.

zbook · Feb 12, 2022

Please run:
Tuneup_plus_log.bat ─ Click here to go to the BSOD batch repository to download and run this batch file.

https://www.tenforums.com/attachments/bsod-crashes-debugging/359284d1644394465-batch-files-use-bsod-debugging-tuneup_plus_log.bat

https://www.tenforums.com/attachments/bsod-crashes-debugging/359059d1644158079-batch-files-use-bsod-debugging-tuneup_plus_log.zip

Stigg · Feb 13, 2022

It could be an indication of hardware failure such as your system drive or memory module.
I'd be running tests on both.

Sammy888 · Feb 14, 2022

Stigg said:
It could be an indication of hardware failure such as your system drive or memory module.
I'd be running tests on both.

Hmm. Indeed. It's rare but possible. However, I ran some more tests and it seems uninstalling the bloatware that came with my laptop is the main culprit. Except, it's also happened once with a clean install as well, mainly overlapping ownership errors which are fixed as a result of the scan.

Sammy888 · Feb 14, 2022

zbook said:
Please run:
Tuneup_plus_log.bat ─ Click here to go to the BSOD batch repository to download and run this batch file.

https://www.tenforums.com/attachments/bsod-crashes-debugging/359284d1644394465-batch-files-use-bsod-debugging-tuneup_plus_log.bat

https://www.tenforums.com/attachments/bsod-crashes-debugging/359059d1644158079-batch-files-use-bsod-debugging-tuneup_plus_log.zip

Thanks. I'll run it tomorrow. Stay tuned.

Sammy888 · Feb 14, 2022

Ghot said:
It really doesn't matter, as long as SFC can fix the errors. :)

Partly true, but it is concerning if it occurs after a clean installation or a factory image from the manufacturer.

Bree · Feb 14, 2022

Sammy888 said:
I installed several different images and I also installed W11 from scratch. Each time I finish, I reboot my laptop and I run SFC. There are errors found.

Whether it's significant or not very much depends on the type of errors SFC finds and fixes.

I find, typically after installing one of the Preview Cumulative Updates, that there are a few files or folders that have their permissions set twice. This is a trivial error as invariably both permissions were the same. SFC logs the errors it finds and corrects in "C:\Windows\Logs\CBS\CBS.log".

Code:

2021-09-28 23:13:59, Info                  CSI    0000015a Warning: Overlap: Directory \??\C:\ProgramData\Microsoft\Windows\Start Menu\ is owned twice or has its security set twice
   Original owner: Microsoft-Windows-shell32, version 10.0.19041.1202, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
   New owner: Microsoft-Windows-shell32, version 10.0.19041.1202, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
2021-09-28 23:13:59, Info                  CSI    0000015b Warning: Overlap: Directory \??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ is owned twice or has its security set twice
   Original owner: Microsoft-Windows-shell32, version 10.0.19041.1202, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
   New owner: Microsoft-Windows-shell32, version 10.0.19041.1202, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
2021-09-28 23:13:59, Info                  CSI    0000015c Warning: Overlap: Directory \??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\ is owned twice or has its security set twice
   Original owner: Microsoft-Windows-shell32, version 10.0.19041.1202, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
   New owner: Microsoft-Windows-shell32, version 10.0.19041.1202, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}

Bree · Feb 14, 2022

Sammy888 said:
it is concerning if it occurs after a clean installation or a factory image from the manufacturer.

I have only ever seen 'permissions set twice' errors in a clean install, and as I said, those are insignificant errors with no impact on system operation. Microsoft seem a bit lax sometimes in checking their builds before release.

zbook · Feb 14, 2022

Microsoft at one time changed Microsoft Defender.

When that happened sfc /scannow displayed integrity violations.

These were hash mismatches.

Once Microsoft had created a new update the hash mismatches were resolved.

So even after a relatively new installation scannow can display integrity violations.

Sammy888 · Feb 15, 2022

Bree said:
I have only ever seen 'permissions set twice' errors in a clean install, and as I said, those are insignificant errors with no impact on system operation. Microsoft seem a bit lax sometimes in checking their builds before release.

Thanks. This is good to know.

Sammy888 · Feb 15, 2022

zbook said:
Microsoft at one time changed Microsoft Defender.

When that happened sfc /scannow displayed integrity violations.

These were hash mismatches.

Once Microsoft had created a new update the hash mismatches were resolved.

So even after a relatively new installation scannow can display integrity violations.

Thanks. Good to know.

AddRAM · Feb 15, 2022

Mine was fine yesterday, I just ran it and I got this.

zbook · Feb 15, 2022

AddRAM said:
Mine was fine yesterday, I just ran it and I got this.

View attachment 21966

Please run tuneup plus.
Tuneup_plus_log.bat ─ Click here to go to the BSOD batch repository to download and run this batch file.
It may fix the underlying problem(s) by running dism commands.
The script should also generate a text file if it had found a problem.

AddRAM · Feb 15, 2022

And now it`s perfect. The only thing that may have caused it is a update.

zbook · Feb 15, 2022

The first image displayed that scannow had repaired the problem.
The second scannow found no new problems.
So your set.
If you were interested in seeing what had been found you could view the CBS log file.
However there are more fun things to do.

AddRAM · Feb 15, 2022

Yep, I`m gonna hit the pillows

Bree · Feb 15, 2022

AddRAM said:
Mine was fine yesterday, I just ran it and I got this.

SFC says that it found and fixed errors. If you open your C:\Windows\Logs\CBS\CBS.log in Notepad and search for "twice" I'm willing to bet you'll find that the only errors it fixed were "owned twice or has its security set twice" ones, like mine in post #8. As I said, this type of error is typically found after an update, but has no significance. As the next line says, the new owner SFC resets it to is invariably the same as the original owner.

humbird · Feb 15, 2022

I remember a few years ago I ran sfc and it found and fixed errors, but after another sfc directly afterwards it still showed errors and fixed them. It did this 4 times before it had a clean sfc readout. I rebooted and ran it till it showed no errors found.

Bree · Feb 15, 2022

humbird said:
after another sfc directly afterwards it still showed errors and fixed them. It did this 4 times before it had a clean sfc readout.

There are two types of error SFC may find and fix. The first is the trivial ownership/permission one I described above. The second is replacing corrupt files with good copies from the component store. This second type may indeed take several runs before all corruption is fixed.

Use Option Three in this tutorial to read the log and see if SFC has found/fixed corrupted files.

Use System File Checker (SFC) to Repair System Files in Windows 11

This tutorial will show you how to run the System File Checker (SFC) tool to repair missing, corrupted, and modified system files in Windows 10 and Windows 11. System File Checker (SFC) is a tool built into Windows that will check for system file corruption. The SFC /SCANNOW command scans and...

www.elevenforum.com

If it says it found corrupt files but couldn't fix them, then you need to run DISM to repair the components store before running SFC again.

Repair Windows Image Component Store in Windows 11

This tutorial will show you how to repair Windows image component store corruption in Windows 11. If a Windows image becomes unserviceable, you can use the DISM (Deployment Imaging and Servicing Management) tool or Repair-WindowsImage cmdlet to update the files and correct the problem. For...

www.elevenforum.com

Is it "normal" for SFC to need to repair files after upgrading or installing Windows?

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

R.I.P.

My Computers

Well-known member

My Computer

R.I.P.

My Computers

Well-known member

My Computer

R.I.P.

My Computers

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computers