Announcement

Collapse
No announcement yet.

sfc and corrupted files

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • sfc and corrupted files

    Hi

    I booted Windows 7 Ultimate SP1 64-bit in safe mode with the command prompt, I started the sfc /scannow command and it told me that I have some corrupted files that it can not restore.

    Now, my CBS.log file is:

    https://www.dropbox.com/s/sgmtzmvzl704ay9/CBS.log?dl=0

    So, how do I restore these files?

    Thanks

    Bye
    Last edited by balubeto; 2nd February 2015, 19:42.
    balubeto

  • #2
    Re: sfc and corrupted files

    Sorry, but no way am I opening an unknown file from a cloud drive - that's how system files get corrupted in the first place.

    You could restore from a backup (of course an IT administrator of your knowledge and experience will have backups) or using System Restore. Failing those, you could do a repair install of Windows from media, or bite the bullet, back up your data and nuke the computer and start again

    Out of curiousity, does it boot (a) normally or (b) in Safe Mode with GUI and networking
    What do you think caused the original file corruption?
    Tom Jones
    MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
    PhD, MSc, FIAP, MIITT
    IT Trainer / Consultant
    Ossian Ltd
    Scotland

    ** Remember to give credit where credit is due and leave reputation points where appropriate **

    Comment


    • #3
      Re: sfc and corrupted files

      Originally posted by Ossian View Post
      Sorry, but no way am I opening an unknown file from a cloud drive - that's how system files get corrupted in the first place.

      You could restore from a backup (of course an IT administrator of your knowledge and experience will have backups) or using System Restore. Failing those, you could do a repair install of Windows from media, or bite the bullet, back up your data and nuke the computer and start again

      Out of curiousity, does it boot (a) normally or (b) in Safe Mode with GUI and networking
      What do you think caused the original file corruption?
      Try if now you see the file.

      Thanks

      Bye
      balubeto

      Comment


      • #4
        Re: sfc and corrupted files

        I don't care if I see the file or not - I would never click on a link like that without having an idea what it is (and you saying it is a log is not enough). I would advise anyone else to treat the link with extreme caution
        Tom Jones
        MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
        PhD, MSc, FIAP, MIITT
        IT Trainer / Consultant
        Ossian Ltd
        Scotland

        ** Remember to give credit where credit is due and leave reputation points where appropriate **

        Comment


        • #5
          Re: sfc and corrupted files

          It does not matter which files cannot be replaced. Your best bet is follow Ossian's advice and choose a System Restore point, a backup, repair or reinstallation depending on the severity of the problem.
          A recent poll suggests that 6 out of 7 dwarfs are not happy

          Comment


          • #6
            Re: sfc and corrupted files

            Originally posted by Blood View Post
            It does not matter which files cannot be replaced. Your best bet is follow Ossian's advice and choose a System Restore point, a backup, repair or reinstallation depending on the severity of the problem.
            From the CBS.log file (see above) that created the sfc /scannow command, how do I understand which files are corrupt?

            Thanks

            Bye
            balubeto

            Comment


            • #7
              Re: sfc and corrupted files

              But that's the whole point of what we are saying - you do not need to. Have you tried any of the options that Ossian outlined to you? Once you have done one or more of those, run SFC again.
              A recent poll suggests that 6 out of 7 dwarfs are not happy

              Comment


              • #8
                Re: sfc and corrupted files

                Examining the CBS.log file created by the sfc /scannow command, I found the following errors:
                Code:
                2015-02-02 11:04:17, Info                  CSI    0000019c [SR] Verifying 100 (0x0000000000000064) components
                2015-02-02 11:04:17, Info                  CSI    0000019d [SR] Beginning Verify and Repair transaction
                2015-02-02 11:04:20, Info                  CSI    0000019f [SR] Cannot repair member file [l:18{9}]"login.cmd" of Microsoft-Windows-Telnet-Server, 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-02-02 11:04:20, Info                  CSI    000001a1 [SR] Cannot repair member file [l:18{9}]"login.cmd" of Microsoft-Windows-Telnet-Server, 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-02-02 11:04:20, Info                  CSI    000001a2 [SR] This component was referenced by [l:182{91}]"Microsoft-Windows-Telnet-Server-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.TelnetServer"
                2015-02-02 11:04:20, Info                  CSI    000001a5 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:18{9}]"login.cmd"; source file in store is also corrupted
                2015-02-02 11:04:21, Info                  CSI    000001a7 [SR] Verify complete
                 2015-02-02 11:07:33, Info                  CSI    00000339 [SR] Verifying 99 (0x0000000000000063) components
                2015-02-02 11:07:33, Info                  CSI    0000033a [SR] Beginning Verify and Repair transaction
                2015-02-02 11:07:35, Info                  CSI    0000033c [SR] Verify complete
                2015-02-02 11:07:35, Info                  CSI    0000033d [SR] Repairing 1 components
                2015-02-02 11:07:35, Info                  CSI    0000033e [SR] Beginning Verify and Repair transaction
                2015-02-02 11:07:35, Info                  CSI    00000340 [SR] Cannot repair member file [l:18{9}]"login.cmd" of Microsoft-Windows-Telnet-Server, 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-02-02 11:07:35, Info                  CSI    00000342 [SR] Cannot repair member file [l:18{9}]"login.cmd" of Microsoft-Windows-Telnet-Server, 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-02-02 11:07:35, Info                  CSI    00000343 [SR] This component was referenced by [l:182{91}]"Microsoft-Windows-Telnet-Server-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.TelnetServer"
                2015-02-02 11:07:35, Info                  CSI    00000346 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:18{9}]"login.cmd"; source file in store is also corrupted
                2015-02-02 11:07:35, Info                  CSI    00000348 [SR] Repair complete
                2015-02-02 11:07:35, Info                  CSI    00000349 [SR] Committing transaction
                2015-02-02 11:07:35, Info                  CSI    0000034d [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired
                 2015-02-02 11:17:57, Info                  CSI    0000019c [SR] Verifying 100 (0x0000000000000064) components
                2015-02-02 11:17:57, Info                  CSI    0000019d [SR] Beginning Verify and Repair transaction
                2015-02-02 11:18:00, Info                  CSI    0000019f [SR] Cannot repair member file [l:18{9}]"login.cmd" of Microsoft-Windows-Telnet-Server, 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-02-02 11:18:00, Info                  CSI    000001a1 [SR] Cannot repair member file [l:18{9}]"login.cmd" of Microsoft-Windows-Telnet-Server, 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-02-02 11:18:00, Info                  CSI    000001a2 [SR] This component was referenced by [l:182{91}]"Microsoft-Windows-Telnet-Server-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.TelnetServer"
                2015-02-02 11:18:00, Info                  CSI    000001a5 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:18{9}]"login.cmd"; source file in store is also corrupted
                2015-02-02 11:18:01, Info                  CSI    000001a7 [SR] Verify complete
                ...
                balubeto

                Comment


                • #9
                  Re: sfc and corrupted files

                  Code:
                  2015-02-02 11:21:29, Info                  CSI    00000339 [SR] Verifying 99 (0x0000000000000063) components
                  2015-02-02 11:21:29, Info                  CSI    0000033a [SR] Beginning Verify and Repair transaction
                  2015-02-02 11:21:32, Info                  CSI    0000033c [SR] Verify complete
                  2015-02-02 11:21:32, Info                  CSI    0000033d [SR] Repairing 1 components
                  2015-02-02 11:21:32, Info                  CSI    0000033e [SR] Beginning Verify and Repair transaction
                  2015-02-02 11:21:32, Info                  CSI    00000340 [SR] Cannot repair member file [l:18{9}]"login.cmd" of Microsoft-Windows-Telnet-Server, 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-02-02 11:21:32, Info                  CSI    00000342 [SR] Cannot repair member file [l:18{9}]"login.cmd" of Microsoft-Windows-Telnet-Server, 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-02-02 11:21:32, Info                  CSI    00000343 [SR] This component was referenced by [l:182{91}]"Microsoft-Windows-Telnet-Server-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.TelnetServer"
                  2015-02-02 11:21:32, Info                  CSI    00000346 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:18{9}]"login.cmd"; source file in store is also corrupted
                  2015-02-02 11:21:32, Info                  CSI    00000348 [SR] Repair complete
                  2015-02-02 11:21:32, Info                  CSI    00000349 [SR] Committing transaction
                  2015-02-02 11:21:32, Info                  CSI    0000034d [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired
                   2015-02-02 11:42:23, Info                  CSI    0000019c [SR] Verifying 100 (0x0000000000000064) components
                  2015-02-02 11:42:23, Info                  CSI    0000019d [SR] Beginning Verify and Repair transaction
                  2015-02-02 11:42:26, Info                  CSI    0000019f [SR] Cannot repair member file [l:18{9}]"login.cmd" of Microsoft-Windows-Telnet-Server, 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-02-02 11:42:27, Info                  CSI    000001a1 [SR] Cannot repair member file [l:18{9}]"login.cmd" of Microsoft-Windows-Telnet-Server, 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-02-02 11:42:27, Info                  CSI    000001a2 [SR] This component was referenced by [l:182{91}]"Microsoft-Windows-Telnet-Server-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.TelnetServer"
                  2015-02-02 11:42:27, Info                  CSI    000001a5 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:18{9}]"login.cmd"; source file in store is also corrupted
                  2015-02-02 11:42:27, Info                  CSI    000001a7 [SR] Verify complete
                   2015-02-02 11:45:58, Info                  CSI    00000339 [SR] Verifying 99 (0x0000000000000063) components
                  2015-02-02 11:45:58, Info                  CSI    0000033a [SR] Beginning Verify and Repair transaction
                  2015-02-02 11:46:00, Info                  CSI    0000033c [SR] Verify complete
                  2015-02-02 11:46:00, Info                  CSI    0000033d [SR] Repairing 1 components
                  2015-02-02 11:46:00, Info                  CSI    0000033e [SR] Beginning Verify and Repair transaction
                  2015-02-02 11:46:00, Info                  CSI    00000340 [SR] Cannot repair member file [l:18{9}]"login.cmd" of Microsoft-Windows-Telnet-Server, 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-02-02 11:46:00, Info                  CSI    00000342 [SR] Cannot repair member file [l:18{9}]"login.cmd" of Microsoft-Windows-Telnet-Server, 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-02-02 11:46:00, Info                  CSI    00000343 [SR] This component was referenced by [l:182{91}]"Microsoft-Windows-Telnet-Server-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.TelnetServer"
                  2015-02-02 11:46:00, Info                  CSI    00000346 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:18{9}]"login.cmd"; source file in store is also corrupted
                  2015-02-02 11:46:00, Info                  CSI    00000348 [SR] Repair complete
                  2015-02-02 11:46:00, Info                  CSI    00000349 [SR] Committing transaction
                  2015-02-02 11:46:00, Info                  CSI    0000034d [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired
                  How do I do to fix these errors?


                  Thanks

                  Bye
                  balubeto

                  Comment


                  • #10
                    Re: sfc and corrupted files

                    Now why couldn't you have posted that in the first place instead of a dodgy link?

                    Unless you use Telnet, none of the errors look critical so if this is the only problem, just ignore them.

                    What EXACTLY are the problems you are having with this computer (and please DONT say SFC has failed)?
                    Have you tried any of the fixes above?
                    Tom Jones
                    MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
                    PhD, MSc, FIAP, MIITT
                    IT Trainer / Consultant
                    Ossian Ltd
                    Scotland

                    ** Remember to give credit where credit is due and leave reputation points where appropriate **

                    Comment


                    • #11
                      Re: sfc and corrupted files

                      Insert relevatnt OS disk for system.
                      Open a command prompt
                      Type sfc /scannow

                      If that doesn't fix it then you have a corruption in the OS DLLCACHE and will need to re-install.

                      Comment

                      Working...
                      X