LF

Then it says

2015-02-04 22:01:22, Info                  CSI    0000092d    [SR] Repair complete

2015-02-04 22:01:22, Info           CSI      0000092e [SR] Committing transaction

2015-02-04 22:01:22, Info           CSI    00000933 [SR] Verify and Repair Transaction completed. All    files and registry keys listed in this transaction have been  successfully repaired

LF

Then it says

, TypeName neutral, PublicKey neutral in the store, file is    missing

2015-02-04 22:01:22, Info                  CSI    0000092d    [SR] Repair complete

2015-02-04 22:01:22, Info           CSI      0000092e [SR] Committing transaction

2015-02-04 22:01:22, Info           CSI    00000933 [SR] Verify and Repair Transaction completed. All    files and registry keys listed in this transaction have been  successfully repaired

Hi

You can use DISM on Windows 8.1

https://technet.microsoft.com/en-us/library/hh824869.aspx

Try this: DISM /Online /Cleanup-Image /RestoreHealth

Hi

You can use DISM on Windows 8.1

https://technet.microsoft.com/en-us/library/hh824869.aspx

Try this: DISM /Online /Cleanup-Image /RestoreHealth

How did you install Windows? DVD? USB?

How did you install Windows? DVD? USB?

USB , but what difference does it make?

Try this then, but you have to use the installation media

Dism /Online /Cleanup-Image /RestoreHealth /source:wim:D:\sources\install.wim:1 /limitaccess

Replace the drive letter according to your computer

This command will use the local source, and not use the Windows Update

How did you install Windows? DVD? USB?

USB , but what difference does it make?

I was going to ask if you had configured your PC to boot from either the USB or DVD and run a repair. If sfc cannot repair a missing file, then a Windows repair may be able to pull it from the USB and replace it. Have you tried that?

Try this then, but you have to use the installation media

Dism /Online /Cleanup-Image /RestoreHealth /source:wim:D:\sources\install.wim:1 /limitaccess

Replace the drive letter according to your computer

This command will use the local source, and not use the Windows Update

• Edited by lonelyfishcn Saturday, February 07, 2015 3:19 AM

Dism /Online /Cleanup-Image /RestoreHealth /source:wim:D:\sources\install.wim:1 /limitaccess

That's being optimistic about the functionality.  However, now that it has failed in both cases you could go back to the CBS.log and find out what it says.  Usually there is a clue there about where it was expecting to find the module and more importantly why it would be there.  Then you use that information to find a download, e.g. an .msu file which you unpack and then that is what you point DISM at for its "source".  Or just do stuff the old way and hack it back to normal now that you know what is wrong.   <eg>

Good luck

Dism /Online /Cleanup-Image /RestoreHealth /source:wim:D:\sources\install.wim:1 /limitaccess

That's being optimistic about the functionality.  However, now that it has failed in both cases you could go back to the CBS.log and find out what it says.  Usually there is a clue there about where it was expecting to find the module and more importantly why it would be there.  Then you use that information to find a download, e.g. an .msu file which you unpack and then that is what you point DISM at for its "source".  Or just do stuff the old way and hack it back to normal now that you know what is wrong.   <eg>

Goo

"2015-02-04 22:01:22, Info                  CSI    0000092c [SR]    Cannot repair member file [l:40{20}]"System.resources.dll" of    System.resources, Version = 4.0.9600.16384, pA =   

Try using the hints I gave.  Does DISM indicate there is a problem with that module too?  If so, the context given when it is unable to repair it will help you figure out what update that you need to download and unpack.

Otherwise, now that you have a module to check on by yourself you could use this PowerShell pipeline to see if there are any problems indicated that way.

PS C:\> ls -Re -Fi System.Resources.dll | sort LastWriteTime | ft Length, FullName -AutoSize

Good luck

There's a new problem now. According to the information provided by sfcdetails.txt , I suspect it is related to .NET Framework . I tracked down 6 directories which I believe were system.resources.dll related under c:\windows\winsxs

there's  a system.resources.dll under every of these 6 directories.I open the first directory ,and found that size of the system.resources.dll is suspicious, I suspect it was corrupt. So I deleted the file ,and also I deleted the 4th directory which I believe might be relevant because the number in the name of the directory is somewhat consistent with the system.resources.dll  version number provided by  sfcdetails.txt . After that I ran DISM /Online /Cleanup-Image /RestoreHealth again , the file and directory I deleted was recovered successfully, then I ran sfc /scannow ,now there're two problematic entries in sfcdetails.txt :

2015-02-08 20:29:05, Info                  CSI    0000123f [SR] Cannot repair member file [l:40{20}]"System.resources.dll" of System.resources, Version = 4.0.9600.16384, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture = [l:10{5}]"zh-cn", VersionScope neutral, PublicKeyToken = {l:8 b:b77a5c561934e089}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2015-02-08 20:29:05, Info                  CSI    00001242 [SR] Cannot repair member file [l:40{20}]"System.resources.dll" of System.resources, Version = 4.0.9600.16404, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture = [l:10{5}]"zh-cn", VersionScope neutral, PublicKeyToken = {l:8 b:b77a5c561934e089}, Type neutral, TypeName neutral, PublicKey neutral in the store, file cannot be decompressed

The first problem persists ,and now there's this second problematic entry ,what does it tell?

• Edited by lonelyfishcn 21 hours 18 minutes ago

suspect it is related to .NET Framework

Or Silverlight.  Have you considered uninstalling that?

found that size of the system.resources.dll is suspicious, I suspect it was corrupt. So I deleted the file ,and also I deleted the 4th directory which I believe might be relevant because the number in the name of the directory is somewhat consistent with the system.resources.dll  version number provided by  sfcdetails.txt .

That's I was referring to as hacking.  In fact, I suspect you just deleted some cached files which had been compressed and now have even less consistency in your WinSxS than you had before.  So now, SFC which relies on consistency in the WinSxS and attempts to make repairs from it, is now further hindered by its inconsistency.

Did you try the PowerShell pipeline I showed?  Do you have another otherwise identical system that you could do the same command on, to show you what is wrong by comparing the two outputs?

Silverlight is not installed , and I've tried PowerShell pipeline ,nothing happen except that it copied one more  system.resources.dll to c:\windows\system32.

I only deleted one file which I  believe was corrupt, and Dism successfully recovered it, It's not supposed to be a probem.

tried PowerShell pipeline ,nothing happen except that it copied one more  system.resources.dll to c:\windows\system32