sfc /scannow run from Installation Disk

Page 3 of 6 FirstFirst 12345 ... LastLast

  1. Posts : 24,479
    Windows 7 Ultimate X64 SP1
       #21

    Good news indeed.

    Gary
      My Computer


  2. Posts : 24
    Windows 7 Home Premium 64 bit
    Thread Starter
       #22

    I ran chkdsk and the the sfc again after replacing the two files. I replaced the files by putting a known good copy of the file on my desktop. Navigating to the corrupt file folder (system32) and take ownership of the folder. Then move the one on my desktop to the system32 folder. The option window "There is already a file named.." select replace. That should work correct?
    sfc /scannow run from Installation Disk Attached Files
      My Computer


  3. Posts : 24,479
    Windows 7 Ultimate X64 SP1
       #23

    Code:
     
    2014-01-26 14:58:12, Info                  CSI    00000309 [SR] Cannot repair member file [l:38{19}]"NlsLexicons0416.dll" of Microsoft-Windows-NaturalLanguage6, 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
    2014-01-26 14:58:15, Info                  CSI    0000030b [SR] Cannot repair member file [l:38{19}]"NlsLexicons0416.dll" of Microsoft-Windows-NaturalLanguage6, 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
    2014-01-26 14:58:15, Info                  CSI    0000030c [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"
    2014-01-26 14:58:19, Info                  CSI    0000030e [SR] Repair complete
    2014-01-26 14:58:19, Info                  CSI    0000030f [SR] Committing transaction
    2014-01-26 14:58:19, Info                  CSI    00000313 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired
    What message did you get after running the SFC? Those in red didn't fix, but later it said they are.
      My Computer


  4. Posts : 24
    Windows 7 Home Premium 64 bit
    Thread Starter
       #24

    It says the same thing after any sfc. I just ran this one:
    sfc /scannow run from Installation Disk Attached Files
      My Computer


  5. Posts : 24,479
    Windows 7 Ultimate X64 SP1
       #25

    OK, I meant what does it say in the CMD window upon completion.

    Code:
    Windows Resource Protection found corrupt files and successfully repaired
    them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
    example C:\Windows\Logs\CBS\CBS.log
    The system file repair changes will take effect after the next reboot.
    Or a message that no integrity violations were found.
    Or that Windows Resource Protection found errors it cannot repair.[/QUOTE]
      My Computer


  6. Posts : 24
    Windows 7 Home Premium 64 bit
    Thread Starter
       #26

    It says the same thing, found corrupt files but couldn't fix all of them check the log at CBS.log every time.
      My Computer


  7. Posts : 24,479
    Windows 7 Ultimate X64 SP1
       #27

    I'll ask for help for the SFC issues.
      My Computer


  8. Posts : 24
    Windows 7 Home Premium 64 bit
    Thread Starter
       #28

    Funny, I'm not having computer issues yet. Everything seems to be working normally.
      My Computer


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

    You need to replace the files in the proper manner for it to work.
    Code:
    2014-01-27 21:59:05, Info                  CSI    00000306 [SR] Repairing 1 components
    2014-01-27 21:59:05, Info                  CSI    00000307 [SR] Beginning Verify and Repair transaction
    2014-01-27 21:59:07, Info                  CSI    00000309 [SR] Cannot repair member file [l:38{19}]"NlsLexicons0416.dll" of Microsoft-Windows-NaturalLanguage6, 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
    You've now messed with the permissions of a critical system folder - which may create problems later on.
    I'll worry about that once we have the files sorted.
    The reason this didn't work is almost certainly because you replaced the wrong copy of the file - the 'daughter' rather than the 'mother' which resides in the winsxs folder -and the one in the System32 folder may only exist as a hardlink to the mother file.
    We therefore need to replace the mother file..
    I'll post a fix a bit later.
      My Computer


  10. Posts : 24
    Windows 7 Home Premium 64 bit
    Thread Starter
       #30

    Thank you very much!
      My Computer


 
Page 3 of 6 FirstFirst 12345 ... 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 05:01.
Find Us