SFC /SCANNOW Command - System File Checker

Page 87 of 99 FirstFirst ... 77858687888997 ... LastLast

  1. Posts : 17,322
    Win 10 Pro x64
       #860

    helpful55 said:
    Tells me Cannot open [log file]
    Copy it to the desktop, it should allow it then.
      My Computer


  2. Posts : 49
    W7 Pro 64
       #861

    Wow, why did I go through that long cmd entry!!!? Thanks that worked. Although now I have 5.63MB of pages to look at that I have no idea what they are. Ask and you shall receive. On to my next problems and tasks. Thanks again.
      My Computer


  3. Posts : 17,322
    Win 10 Pro x64
       #862

    You're welcome. You can start a thread here,

    https://www.sevenforums.com/performance-maintenance/

    And attach the zipped file, someone will have a look when they get a chance.
      My Computer


  4. Posts : 70,196
    64-bit Windows 10 Pro
    Thread Starter
       #863

    helpful55 said:
    Wow, why did I go through that long cmd entry!!!? Thanks that worked. Although now I have 5.63MB of pages to look at that I have no idea what they are. Ask and you shall receive. On to my next problems and tasks. Thanks again.
    That would be why. OPTION THREE for the sfcdetails.txt will only show you the results of the SFC command and nothing else.

    If you like, you can copy and paste the command. :)
      My Computer


  5. Posts : 30
    Windows 7 32 Bit
       #864

    Hi
    Is there a utility that gets a list of corrupted files from sfc and export it to another file and use some utility on similar ok system using that list of corrupted files copy ok files from donar system and the using some utility install them in affected system..

    Or any script?

    I hope power shell can do it.. ?

    Or some other program that just extracts list of corrupted files from Windows sfc result and and restore it from Windows DVD etc?
      My Computer


  6. Posts : 70,196
    64-bit Windows 10 Pro
    Thread Starter
       #865

    Hello bhar,

    Not that I'm aware of other than using OPTION THREE, and use the troubleshooting steps in the blue note box at the bottom of OPTION TWO.
      My Computer


  7. Posts : 1
    Windows 7 Home Basic 64bits
       #866

    Hi Brink
    i'm running windows 7 PRO x64 on asus n46vm
    I ran sfxlc 5 times and keeps showing unfixed problems
    Could you help me?
      My Computer


  8. Posts : 70,196
    64-bit Windows 10 Pro
    Thread Starter
       #867

    Hello cyberlan, and welcome to Seven Forums. :)

    Did you modify your log on screen? If so, that would account for most of the hash mismatches found below by SFC.

    Code:
    CSI    00000339 [SR] Cannot repair member file [l:24{12}]"%userprofile%\Desktop" of Microsoft-Windows-Setup-Navigation-Wizard-Framework, Version = 6.1.7601.17514, 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-10-16 21:06:31, Info                  CSI    0000033b [SR] Cannot repair member file [l:28{14}]"background.bmp" of Setup-UXWizard-ClientImages, Version = 6.1.7600.16385, 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-10-16 21:06:31, Info                  CSI    0000033d [SR] Cannot repair member file [l:24{12}]"spwizimg.dll" of Microsoft-Windows-Setup-Navigation-Wizard-Framework, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2015-10-16 21:06:31, Info                  CSI    0000033f [SR] Cannot repair member file [l:24{12}]"spwizimg.dll" of Microsoft-Windows-Setup-Navigation-Wizard-Framework, Version = 6.1.7601.17514, 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-10-16 21:06:31, Info                  CSI    00000340 [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"
    2015-10-16 21:06:31, Info                  CSI    00000343 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:24{12}]"spwizimg.dll"; source file in store is also corrupted
    2015-10-16 21:06:31, Info                  CSI    00000345 [SR] Cannot repair member file [l:24{12}]"spwizimg.dll" of Microsoft-Windows-Setup-Navigation-Wizard-Framework, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2015-10-16 21:06:31, Info                  CSI    00000346 [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"
    2015-10-16 21:06:31, Info                  CSI    00000349 [SR] Could not reproject corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:24{12}]"spwizimg.dll"; source file in store is also corrupted
    2015-10-16 21:06:31, Info                  CSI    0000034b [SR] Cannot repair member file [l:28{14}]"background.bmp" of Setup-UXWizard-ClientImages, Version = 6.1.7600.16385, 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-10-16 21:06:31, Info                  CSI    0000034c [SR] This component was referenced by [l:242{121}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.Microsoft-Windows-Client-Features-Update"
    2015-10-16 21:06:31, Info                  CSI    0000034f [SR] Could not reproject corrupted file [ml:520{260},l:56{28}]"\??\C:\Windows\System32\oobe"\[l:28{14}]"background.bmp"; source file in store is also corrupted
    2015-10-16 21:06:31, Info                  CSI    00000351 [SR] Repair complete
      My Computer


  9. Posts : 3
    Windows 7 Pro x64
       #868

    XXXL CBS Logs Folder


    I apologize in advance if I missed the answer to this somewhere in this thread, but the thread is very long! My C:\Windows\Logs\CBS folder is 112 GB !! There are 22 CbsPersist_timestamp.log files ranging from 15MB to 30.5GB. I have run sfc /verifyonly and get no integrity violations.

    The output from running
    Code:
    findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"
    was too long to post here, but here is a snippet:
    Code:
    2015-10-21 17:48:22, Info                  CSI    00000829 [SR] Verifying 100 (0x0000000000000064) components
    2015-10-21 17:48:22, Info                  CSI    0000082a [SR] Beginning Verify and Repair transaction
    2015-10-21 17:48:23, Info                  CSI    0000082e [SR] Verify complete
    2015-10-21 17:48:23, Info                  CSI    0000082f [SR] Verifying 100 (0x0000000000000064) components
    2015-10-21 17:48:23, Info                  CSI    00000830 [SR] Beginning Verify and Repair transaction
    2015-10-21 17:48:24, Info                  CSI    00000832 [SR] Verify complete
    2015-10-21 17:48:24, Info                  CSI    00000833 [SR] Verifying 100 (0x0000000000000064) components
    2015-10-21 17:48:24, Info                  CSI    00000834 [SR] Beginning Verify and Repair transaction
    2015-10-21 17:48:24, Info                  CSI    00000836 [SR] Verify complete
    2015-10-21 17:48:24, Info                  CSI    00000837 [SR] Verifying 100 (0x0000000000000064) components
    2015-10-21 17:48:24, Info                  CSI    00000838 [SR] Beginning Verify and Repair transaction
    2015-10-21 17:48:25, Info                  CSI    0000083a [SR] Verify complete
    2015-10-21 17:48:25, Info                  CSI    0000083b [SR] Verifying 100 (0x0000000000000064) components
    2015-10-21 17:48:25, Info                  CSI    0000083c [SR] Beginning Verify and Repair transaction
    2015-10-21 17:48:26, Info                  CSI    0000083f [SR] Verify complete
    2015-10-21 17:48:26, Info                  CSI    00000840 [SR] Verifying 100 (0x0000000000000064) components
    2015-10-21 17:48:26, Info                  CSI    00000841 [SR] Beginning Verify and Repair transaction
    2015-10-21 17:48:27, Info                  CSI    00000843 [SR] Verify complete
    2015-10-21 17:48:27, Info                  CSI    00000844 [SR] Verifying 100 (0x0000000000000064) components
    2015-10-21 17:48:27, Info                  CSI    00000845 [SR] Beginning Verify and Repair transaction
    2015-10-21 17:48:28, Info                  CSI    00000847 [SR] Verify complete
    2015-10-21 17:48:28, Info                  CSI    00000848 [SR] Verifying 100 (0x0000000000000064) components
    2015-10-21 17:48:28, Info                  CSI    00000849 [SR] Beginning Verify and Repair transaction
    2015-10-21 17:48:29, Info                  CSI    0000084b [SR] Verify complete
    2015-10-21 17:48:29, Info                  CSI    0000084c [SR] Verifying 100 (0x0000000000000064) components
    2015-10-21 17:48:29, Info                  CSI    0000084d [SR] Beginning Verify and Repair transaction
    2015-10-21 17:48:30, Info                  CSI    00000850 [SR] Verify complete
    2015-10-21 17:48:30, Info                  CSI    00000851 [SR] Verifying 100 (0x0000000000000064) components
    2015-10-21 17:48:30, Info                  CSI    00000852 [SR] Beginning Verify and Repair transaction
    2015-10-21 17:48:31, Info                  CSI    00000854 [SR] Verify complete
    2015-10-21 17:48:31, Info                  CSI    00000855 [SR] Verifying 100 (0x0000000000000064) components
    2015-10-21 17:48:31, Info                  CSI    00000856 [SR] Beginning Verify and Repair transaction
    2015-10-21 17:48:32, Info                  CSI    00000858 [SR] Verify complete
    2015-10-21 17:48:32, Info                  CSI    00000859 [SR] Verifying 100 (0x0000000000000064) components
    2015-10-21 17:48:32, Info                  CSI    0000085a [SR] Beginning Verify and Repair transaction
    2015-10-21 17:48:33, Info                  CSI    0000085c [SR] Verify complete
    2015-10-21 17:48:33, Info                  CSI    0000085d [SR] Verifying 80 (0x0000000000000050) components
    2015-10-21 17:48:33, Info                  CSI    0000085e [SR] Beginning Verify and Repair transaction
    2015-10-21 17:48:33, Info                  CSI    00000860 [SR] Verify complete
    It goes on and on like that. What's the best way to proceed? Can I safely delete the log files? Will they continue to pop back up? In case it matters, I'm on Windows 7 Pro x64 and connected to a domain. The computer is an i7-4790 with 16GB RAM. I'm happy to answer any other questions which may be helpful. Thanks!!
      My Computer


  10. Posts : 70,196
    64-bit Windows 10 Pro
    Thread Starter
       #869

    Hello makismagoo99, and welcome to Seven Forums. :)

    There's no need to delete the log files unless you just wanted to. They will be automatically recreated as items are logged again.

    We'll need to see the full sfcdetails.txt file to see what SFC reported though.
      My Computer


 
Page 87 of 99 FirstFirst ... 77858687888997 ... LastLast

  Related Discussions
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 22:23.
Find Us