SFC /SCANNOW Command - System File Checker

Page 86 of 99 FirstFirst ... 76848586878896 ... LastLast

  1. glnz
    Posts : 135
    Dual boot - Win 10 Pro 64-bit (good) and Win 7 Pro 64-bit (won't boot on the NVMe)
       New #850

    Brink - thanks to your thread here, I've run sfc / scannow a number of times on the Win 7 Pro 64-bit side of my dual-booting Dell (including three times in safe mode), and there are now very few error or warning messages in event viewer. Very nice. BUT ...

    The sfc / scannow end message still says that it could not repair some corrupted files (don't have the exact language). And the CBS.log is not exactly user-friendly.

    Should I attach here that CBS.log? Would you have time to look and advise what it's actually saying?

    If this isn't exactly the right place, is there a forum dedicated to medical advice for CBS.logs?

    Thanks again.
      My Computer
    Quote Quote

  3. Brink
    Posts : 72,511
    64-bit Windows 11 Pro for Workstations
    Thread Starter
       New #851

    Hello glnz, :)

    If you like, you can use OPTION THREE in the tutorial to post the sfcdetails.
      My Computer
    Quote Quote

  4. glnz
    Posts : 135
    Dual boot - Win 10 Pro 64-bit (good) and Win 7 Pro 64-bit (won't boot on the NVMe)
       New #852


    Brink - great. Showed very little that remains unrepaired. Here are those lines, which repeat in the various sfc reports.
    2015-09-02 22:39:02, Info CSI 000006a0 [SR] Repairing 1 components
    2015-09-02 22:39:02, Info CSI 000006a1 [SR] Beginning Verify and Repair transaction
    2015-09-02 22:39:02, Info CSI 000006a3 [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-09-02 22:39:02, Info CSI 000006a5 [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
    2015-09-02 22:39:02, Info CSI 000006a7 [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-09-02 22:39:02, Info CSI 000006a8 [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.3068708-814_neutral_GDR"
    2015-09-02 22:39:02, Info CSI 000006aa [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
    2015-09-02 22:39:02, Info CSI 000006ab [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.3068708-814_neutral_GDR"
    2015-09-02 22:39:03, Info CSI 000006ad [SR] Repair complete
    2015-09-02 22:39:03, Info CSI 000006ae [SR] Committing transaction
    2015-09-02 22:39:03, Info CSI 000006b2 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired

    I am guessing this makes sense, as I have UNinstalled various MS updates that are designed to prepare my Win 7 to ascend to Heaven and become Win 10. I prefer my terrestrial Win 7. But just a guess.

    What do you think?

    Many thanks.
      My Computer
    Quote Quote

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

    These errors are perfectly normal - and MS's fault. There's nothing amiss here
    If you want to get rid of them you'll have to uninstall KB3068708 (and possibly KB3022345) and hide it/them
      My Computer
    Quote Quote

  7. Brink
    Posts : 72,511
    64-bit Windows 11 Pro for Workstations
    Thread Starter
       New #854

    Yep, it's just a false hash mismatch from the KB3068708 update. There's nothing that needs to be done or to worry about. :)
      My Computer
    Quote Quote

  8. glnz
    Posts : 135
    Dual boot - Win 10 Pro 64-bit (good) and Win 7 Pro 64-bit (won't boot on the NVMe)
       New #855

    NoelDP - Per your suggestion and a number of other comments, I uninstalled those two updates (in elevated cmd using wusa /uninstall, which can be repeated immediately until you know you got all copies of each update).

    And ... voilą! A new sfc / scannow "did not find any integrity violations". Progress!

    Many thanks to Brink and you!

    Now what to do about diagtrackrunner.exe, which still appears (once only) in my c:/ drive? I have read that it can't be deleted. Please send me links to any good instructions for killing that one.
      My Computer
    Quote Quote

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

    There should actually be at least 4 different copies of diagtrackrunner.exe present (if you'd kept your machine up-to-date)

    Why would you want to remove it?
      My Computer
    Quote Quote

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

    Just for info... the first two were in KB2952664 and KB2977759 - after that I lose track a little... but I think the later ones are all associated with KB2952664 versions (it's been updated quite a few times since first release in January!)
      My Computer
    Quote Quote

  12. glnz
    Posts : 135
    Dual boot - Win 10 Pro 64-bit (good) and Win 7 Pro 64-bit (won't boot on the NVMe)
       New #858

    NoelDP - It might be a stealth "phone home" app to Microsoft. Please google it - many articles - it's linked to the updates I've been trying to get rid of and for which I needed Brink's thread here to repair my machine.

    But that's "enuff" about this side topic. Let's leave this thread to Brink's great advice about sfc.
      My Computer
    Quote Quote

  13. helpful55
    Posts : 67
    W7 Pro 64
       New #859

    Error


    scannow says that it was able to repair, but I am curious as to what it fixed. Tells me Cannot open [log file]
      My Computer
    Quote Quote

 
Page 86 of 99 FirstFirst ... 76848586878896 ... 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 12:35.
Find Us