sfcdetails.txt

Hi

You did not follow my instructions. Yes, SFCFix can repair some types of files on its own, but not all. That's why I sourced the files and created a fix script with those files

CKing123 said:

Sourced the files :) We will run a fix followed by another SFC scan to verify:

SFCFix Fix
This fix is very specific for AddRAM's computer. Trying this fix on your own computer might damage your computer. If you are after assistance, create a new thread, and you will be assisted shortly.

Download SFCFix.exe (by niemiro) and move the executable on your Desktop.
Download SFCFix from here (It was too big to attach) and move the archive to your Desktop
Note: Make sure that the file is named SFCFix.zip, do not rename it.
Save any work you have open, and close every programs
Drag the SFCFix.zip file over the SFCFix.exe executable and release it

SFCFix will launch, let it complete
Once done, a file will appear on your Desktop, called SFCFix.txt
Open the file, then copy and paste its content in your next reply

Now we run the SFC scan

SFC Scan
1. Click on Start and type cmd. When Command Prompt appears, right-click on it, and click Run as Administrator
2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter

Code:

sfc /scannow

3. Once it finishes, copy and paste the following into the command-prompt window and press Enter.

Code:

copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"

4. Once this has completed please go to your Desktop and you will find CBS.txt => Right-click on this file and choose Send To...Compressed (zipped folder). Please upload this zipped file CBS.zip to this thread
Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.

-CKing

Actually he DID,
1 of your files was incorrect
try the SXS one.

C:\Windows\winsxs\msil_system.design_b03f5f7f11d50a3a_6.1.7601.18763_none_89ab76c7bfbe23e4\System.De sign.dll

Roy

Looking at the SFCFix log:

Code:

version 3.0.0.0 by niemiro.
Start time: 2016-08-14 01:06:58.094
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.

AddRAM did not run the fix script

And, the OP had three files corrupt, and one of them was fixed by SFCFix. SFCFix can often detect corrupt files, but not all of them

-CKing

Yes i know it didnt run correctly,
but
the file you sourced for >> MSIL system design<<
WAS NOT the right one.
yours
C:\Windows\msil_system.design_b03f5f7f11d50a3a_6.1.7601.18763_none_89ab76c7bfbe23e4\System.De sign.dll
CORRECT version
C:\Windows\winsxs\msil_system.design_b03f5f7f11d50a3a_6.1.7601.18763_none_89ab76c7bfbe23e4\System.De sign.dll

Roy

Have you downloaded and checked the script?

It copies all of these to the correct folders in the WinSxS folder

-CKing

Yep looked at the ZIP you created thats where i picked up the file name error
Actually it works the other way round, WINSXS updates the lower files, non sxs

Roy

I think there is some confusion about WinSxS and system files or you are confused on the way SFCFix works. Essentially, files that in the system32 or any other location are hardlinked to the files in WinSxS. That's how SFC repairs the files.

As for the SFCFix script, it correctly copies the files to the subfolders inside the WinSxS folder.

Could you explain to me (using the script) where the file system mistake is?

-CKing

in my post 16.
Your fix file does not include the >> winsxs << part of the drilldown, which is where the error is, not the operational file.

Maybe it is me, but your saying the SFCFix script is replacing a valid NON winsxs file, and then performs a second operation
QUOTE
As for the SFCFix script, it correctly copies the files to the subfolders inside the WinSxS folder.

though i'v never seen this being reported in any SFCfix output report.

If thats the case its my miss-understanding of the way SFCexe works,

Roy