SFC /SCANNOW Command - System File Checker

Page 78 of 99 FirstFirst ... 68767778798088 ... LastLast

  1. Brink
    Posts : 72,036
    64-bit Windows 11 Pro for Workstations
    Thread Starter
       New #770

    Hello Somuch2learn, and welcome to Seven Forums.

    From you log file, it's the KB3068708 update for the same false mismatch issue. Nothing needs to be done. :)
      My Computer
    Quote Quote

  3. Somuch2learn
    Posts : 3
    KY, Windows 7 Home Premium, 64 Bit
       New #771

    Brink, that's reassuring. Thanks for your reply

    I noticed that today you addressed the upgrade to Windows 10 in a separate message. Will the W10 OS installation have the effect of debugging my OS, only making even better? I've had some errors (Windows can't update... code: 80070003) while trying to install "optional" updates to W9.

    You have a gift for clear and concise communication. Thanks again.
      My Computer
    Quote Quote

  4. Brink
    Posts : 72,036
    64-bit Windows 11 Pro for Workstations
    Thread Starter
       New #772

    Upgrading to Windows 10 should sort it since you'll be installing a new Windows. :)
      My Computer
    Quote Quote

  5. lehnerus2000
    Posts : 4,049
    W7 Ultimate SP1, LM19.2 MATE, W10 Home 1703, W10 Pro 1703 VM, #All 64 bit
       New #773

    MS needs to fix this ...


    Brink said:
    Hello Somuch2learn, and welcome to Seven Forums.

    From you log file, it's the KB3068708 update for the same false mismatch issue. Nothing needs to be done. :)
    MS needs to fix this false positive issue.

    SFC is a great tool in Windows.
    I have no idea how you confirm the validity of system files in Linux.
      My Computer
    Quote Quote

  7. Somuch2learn
    Posts : 3
    KY, Windows 7 Home Premium, 64 Bit
       New #774

    sfc /scannow vs. Windows Update


    Despite Brink's suggestion that I didn't need to do anything about Update KB3068708, I uninstalled it along with KB3022345 (based on a tip from another WSF thread). I then ran sfc /scannow and got a clean bill of health. This morning Windows Update automatically re-installed KB3068708. Just for grins I re-ran sfc /scannow and got the dreaded "Windows Resource Protection found corrupt files but was unable to fix some of them." This time I will follows Brink's suggestion and do nothing abut Windows 7. After all, later this month we can all start a new learning curve with Windows 10. Good luck out there.
      My Computer
    Quote Quote

  8. AddRAM
    Posts : 13,576
    Windows 10 Pro x64
       New #775

    You have to tutn off auto update.
      My Computer
    Quote Quote

  9. NoelDP
    Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       New #776

    According to MS, these errors are perfectly normal, and can be ignored...
    Code:
    2015-07-03 16:36:01, Info                  CSI    00000511 [SR] Repairing 1 components
2015-07-03 16:36:01, Info                  CSI    00000512 [SR] Beginning Verify and Repair transaction
2015-07-03 16:36:01, Info                  CSI    00000514 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-07-03 16:36:01, Info                  CSI    00000516 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2
    They are the result of MS not actually following their own rules, and tagging the relevant files in the update as 'static' rather than 'variable'.

    You can either:
    1) Uninstall the related update(s) KB3068708 and KB3022345 - and then hide them to prevent reinstall before MS produce a fixed version
    or
    2) ignore them.

    There are no other significant errors in the uploaded file.
      My Computer
    Quote Quote

  11. marsmimar
    Posts : 10,994
    Win 7 Pro 64-bit
       New #777

    NoelDP said:
    According to MS, these errors are perfectly normal, and can be ignored...
    They are the result of MS not actually following their own rules, and tagging the relevant files in the update as 'static' rather than 'variable'.

    You can either:
    1) Uninstall the related update(s) KB3068708 and KB3022345 - and then hide them to prevent reinstall before MS produce a fixed version
    or
    2) ignore them.

    There are no other significant errors in the uploaded file.
    Noel, I think your option one is the best course of action. If someone merely ignores the updates, runs SFC and gets the "Windows Resource Protection found corrupt files but was unable to fix some of them" notice, there's no easy way to know if the corrupted files are due to the updates or some other system files being corrupted.

    I think Microsoft owes it to consumers who are running Windows 7 to correct this issue.
      My Computer
    Quote Quote

  12. NoelDP
    Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       New #778

    I totally agree - especially since these two updates are far from being 'critical'!
      My Computer
    Quote Quote

  13. Jesse Williams
    Posts : 1,944
    Windows 10 Home 64-bit
       New #779

    How do I find out which files are corrupt, and how to fix them?
      My Computer
    Quote Quote

 
Page 78 of 99 FirstFirst ... 68767778798088 ... LastLast

  Related Discussions
System file checker scan and fix command
in Performance & Maintenance

The sfc /scannow command works ok on here but is there one to scan and fix such as the chkdsk /f/r What Ive got here is a really slow startup which maybe should have a different subject. I've refreshed the MBR and run Fixboot at the command prompt. I've run the special command to run sfc...
I have run System File Checker (sfc) and it found many files that were corrupt and could not be repaired. My PC appears to be running fine - but I am anal about repairing anything that is wrong on my PC. The only suggestion I've received so far was to perform a Repair Install. That's very risky....
Ran system file checker and it said it found corrupted files but could not repair all of them. Looking at the log is not helping. I have posted the last several lines as they are representative of the entire log with the exception of the last few lines that mention an actual repair. Where is the...
I have just completed a System File Check and some repairs were done I was told that the relevant report could be seen at C:\WINDOWS\LOGS\CBS\CBS.LOG. When I Clicked on that I got Access Denied How can I Open that log file? I am the Administrator
I hope this will be a help to some and I would appreciate any feed-back. :) SFC /SCANNOW : Run in Command Prompt at Boot Edit: I've just added a Method Two to this. :)
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

 © Designer Media Ltd
All times are GMT -5. The time now is 06:50.
Find Us