New
#950
SFC is only for repairing corrupted or modified Windows system files.
I hope the repair install will help.
SFC is only for repairing corrupted or modified Windows system files.
I hope the repair install will help.
I did the Repair Install about 6 weeks ago too. That's supposed to replace corrupted files. Nothing is fixed except that I was able to install the Nov update.
I'm not having any of these problems on the newly-installed Gateway, identical OS, so it's this machine. SFC says my files are fine. I patted it on the head and gave it a Hershey's chocolate kiss.
I presume my.NET is working fine with who-knows-what Win does with it. Garmin chat couldn't help, and I tried installing the next-to-last version and the one before that, but nada. That's why it's good to have 2 or 3 machines. I don't feel desperate if something goes wrong. I'm going to start doing my work on the Gateway, and use this one as backup.
First, let me thank you for your help.
I run C:\Windows\system32>sfc /scannow periodically as a checkup. In the past, I have always seen the following result :
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.
This time I received a result that indicates there is a problem which I am at a loss to explain or resolve. I have run sfc /scannow several times and continue to see the same result on screen as well as in the sfcdetails.txt file.
The result I received is as follows:
C:\Windows\system32>sfc /scannow
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
C:\Windows\system32>
I have attached the sfcdetails.txt file.
Thank you for any help that you can provide.
Hello @admjgreer, and welcome to Seven Forums.
Your sfcdetails log reports this below. It appears to be a driver issue that reinstalling the driver may help.
Code:Cannot verify component files for c801f401a6eb25564cbd5e9ec745fc06, Version = 6.1.7601.24255, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)
Hello Brink
Thank you for your reply.
Which driver needs to be reinstalled ?
Thank you again.
admjgreer
You can check in Device Manager to see if any of your devices are reporting an issue. If one is, check to see if there is a newer driver version from the device manufacturer's website.
@admjgreer, not necessarily drivers! And not!
or amd64_c801f401a6eb25564cbd5e9ec745fc06_b03f5f7f11d50a3a_6.1.7601.24255_none_9ec760324a3907d8.manifestCode:Cannot verify component files for c801f401a6eb25564cbd5e9ec745fc06
If this file is damaged or missing in winsxs/Manifests folder sfc /scannow will fail on repair.
Would you please download, run SURTx64 and post CheckSUR.log when it completes.
Temporary location: C:\Windows\Logs\CBS
That file is part of the November 2018 update for .NET - but I've never been much good at repairing .NET errors as they need a little more TLC than most![]()