Windows 10: Corrupted file shown in sfc /scannow after fresh Windows install

Hi,


I am facing some issue with respect to disk drive in my system. One day, I couldn't boot windows and it runs to automatic repair loop on boot. I have tried repair, reset and all other options provided in trouble shoot, but still nothing works. Finally, I have used HP recovery option provided to reinstall Windows in my system. When I boot it again, I could see that Windows is fresh, all apps and data is lost and even the partition in drives are removed and the whole 1 TB is dedicated to C: drive now.


After this, I am frequently getting 'Scan your drive for errors' from Security and Maintenance. I then tried to run sfc /scannow to check the drivers but got this error as result.

Windows Resource Protection could not perform the requested operation.


In CBS log files, I could find many errors and details of corrupted files.


Cannot repair member file [l:34]'System.ServiceModel.Primitives.dll' of System.ServiceModel.Primitives, version 4.0.15744.161, arch msil, versionScope neutral, pkt {l:8 b:b03f5f7f11d50a3a} in the store, hash mismatch

Cannot repair member file [l:27]'System.ServiceModel.Web.dll' of System.ServiceModel.Web, version 4.0.15744.161, arch msil, versionScope neutral, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

Cannot repair member file [l:35]'System.Text.Encoding.Extensions.dll' of System.Text.Encoding.Extensions, version 4.0.15744.161, arch msil, versionScope neutral, pkt {l:8 b:b03f5f7f11d50a3a} in the store, hash mismatch

Cannot repair member file [l:31]'System.Threading.Overlapped.dll' of System.Threading.Overlapped, version 4.0.15744.161, arch msil, versionScope neutral, pkt {l:8 b:b03f5f7f11d50a3a} in the store, hash mismatch

Cannot repair member file [l:20]'System.Threading.dll' of System.Threading, version 4.0.15744.161, arch msil, versionScope neutral, pkt {l:8 b:b03f5f7f11d50a3a} in the store, hash mismatch

Cannot repair member file [l:34]'System.Web.ApplicationServices.dll' of System.Web.ApplicationServices, version 4.0.15744.551, arch msil, versionScope neutral, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

Cannot repair member file [l:21]'System.Web.Entity.dll' of System.Web.Entity, version 4.0.15744.161, arch msil, versionScope neutral, pkt {l:8 b:b77a5c561934e089} in the store, hash mismatch

Cannot repair member file [l:33]'System.Web.RegularExpressions.dll' of System.Web.RegularExpressions, version 4.0.15744.161, arch msil, versionScope neutral, pkt {l:8 b:b03f5f7f11d50a3a} in the store, hash mismatch

Cannot repair member file [l:22]'System.Web.Routing.dll' of System.Web.Routing, version 4.0.15744.161, arch msil, versionScope neutral, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

Cannot repair member file [l:38]'System.Windows.Input.Manipulations.dll' of System.Windows.Input.Manipulations, version 4.0.15744.161, arch msil, versionScope neutral, pkt {l:8 b:b77a5c561934e089} in the store, hash mismatch

Cannot repair member file [l:38]'System.Windows.Input.Manipulations.dll' of System.Windows.Input.Manipulations, version 4.0.15744.161, arch msil, versionScope neutral, pkt {l:8 b:b77a5c561934e089} in the store, hash mismatch

Could not reproject corrupted file \??\C:\windows\Microsoft.NET\Framework\v4.0.30319\\System.Threading.Overlapped.dll; source file in store is also corrupted

Cannot repair member file [l:24]'vcruntime140_clr0400.dll' of NetFx4-vcruntime140_CLR_DLL, version 4.0.15744.161, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch


May I know what could be the reason for these issues after a recovery? Can someone help me with fixing these issues.

:)

 

sfc /scannow found corrupt files after fresh win10 install

I had the exact same problem in each of my Windows 10 fresh installations, whether it was 1809, 1903. Every time after a fresh installation SFC /Scannow found corruptions, but it managed to repair the corruptions on all of these cases. And after that there were no longer any integrity violations.

This is weird because when I previously had Windows 8.1 never did SFC /Scannow find any corruptions. In fact even when I had problems with Windows 8.1 after 4 years, SFC failed to find integrity violation.

Sometimes when you have real problems SFC reports as no integrity violation, next time you feel you don't have any problems and this system reports that it has problems, lol.

 

Microsoft Gives Windows 10 a Major Performance Boost

I did a fresh install and ran sfc /scannow, seems to have corrupted files that can't be repaired. Doe anyone know how to fix these?

 

sfc/scannow corrupt file

sfc/scannow keeps finding corrupt files and fixing them