System File Checker Tool

I ran Microsoft's System File Checker tool on my computer. Afterwards, I followed Microsoft's instructions how to determine which files could not be repaired System File Checker tool. The instructions that I followed are here. Although I have tried twice to do this nothing comes up in Command Prompt to tell me what files were not repaired. I have attached an image of the Command Prompt screen after I have checked to see which files were not repaired. Have I done something wrong? I have read, carefully, Microsoft's instructions several times. I cannot see what I have missed or failed to do.

My computer is an Acer Aspire 5920 laptop. My operating system is Microsoft Vista Home Premium Service Pack 2.

 

The command should cause Notepad to open a file with the failed info. It doesn't open in the Command window. Check your taskbar to see if there is an open file in Notepad.

 

Neither a Notepad file nor anything else opens.

 

Maybe there weren't any failures, so no logfile was created.

 

In the third part you have to go to Start and type/paste "sfcdetails.txt" without quotes into the Start/Search box to open the results file. Or it should be on your desktop and you can just double-click it to open.

 

Also %windir%=C:\windows

So you can look in the C:\windows folder and follow the file path to the log file (if it's there).

 

According to the instructions on the original post's screenshot, the logfile sfcdetails.txt should be on the Desktop.

 

Thank you for all your replies.

I found the file by typing sfcdetails.txt into search. My fault really because I thought the file ending was .log.

Now, can anyone please translate the final set of instructions into English please:

 

Greetings, mark59...

1. You're just 'taking ownership' of the file in question - it's a security thing, basically telling Windows that it's alright to modify or replace an important file.

2. 'Icacis' is Microsoft-speak for access control - again, a Windows security protocol.

3. A DOS-like copy-paste-overwrite procedure - in the example given, you're overwriting the 'jscript.dll' file located in the System32 folder with one from the Temp folder.

 

Hello Caliban

I am not sure which part of what is in the example is the name of the file I need to replace and which part is always required in the command. I know I am over cautious but I do not want to end up creating worse problems.:-o Do I do it for every file that was listed as having a problem in the sfcdetails.txt file I generated yesterday? Alternatively, what information should I be looking for in the sfcdetails.txt file to determine if I need to follow these steps for that file?

 

Is the sfcdetails.txt file very large? If not, can you attach it to your next post; someone can have a look at it and tell you if anything needs to be done.

 

It's 27.4 kb is that too big? I've attached it.