[SOLVED] sfcfix help, windows 7 pro sr1 64

[obroad]

So for background the machine had a hard drive with a SSD cache (Intel rapid storage). Recently it started corrupting badly, and the corruption only stopped when I disabled the cache.

Unfortunately Windows is damaged and I badly need to repair it not just reinstall clean due to installed software.

At this time it boots but cannot run elevated actions, run as administrator returns an error.

In safe mode it boots, can run elevated, but currently can't run SFC as the trustedinstaller service won't start.

In REPAIR mode command line SFC can be run on the windows drive, and it creates a log file.

I've tried to run DISM to no avail.

SFCFix returned a report I've attached.

SFCFix asked for an install CD. I have an "ISO" file, is there any way to use that?

Also I've attached CBS.log

 

[PeterJ]

Hello and welcome,

Follow the instructions below please.

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

• Move the executable
  
  SFCFix to your desktop.
• Download the attachment SFCFix.zip and save it on your desktop.
• Save any work you have open, and close all 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.
• Attach that file to your next reply.

 

[obroad]

I've attached the result. Looks like it succeeded. I haven't tried anything else yet.

 

[PeterJ]

Well done.
Attach the file C:\Windows\Logs\CBS\CheckSUR.log to your next reply.

 

[obroad]

Thanks for helping me. I'm away from the broken machine until Monday.

does SFCFIX also fix files in system32 or should I run SFC SCANNOW again to try and complete the repair? If it fixes normal mode so I can access the network and run elevated tasks then any further steps will get much simpler as I'll be able to log into the forum from the machine in question.

Is CheckSUR.log generated by the System Update Readiness Tool because I haven't run that one yet, mainly because I didn't know which file to download.

I read somewhere that it is the one that ends in .msu so I now have that ready on another computer, I still need to copy it to a flash drive.

 

[PeterJ]

I'm away from the broken machine until Monday.

No problem.

Is CheckSUR.log generated by the System Update Readiness Tool because I haven't run that one yet, mainly because I didn't know which file to download.
I read somewhere that it is the one that ends in .msu so I now have that ready on another computer, I still need to copy it to a flash drive.

Yes, the CheckSUR.log is generated by the System Update Readiness Tool. Don't run that tool yet, we do that later.
First I 'd like so see the file CheckSur.log.

 

[obroad]

There was another similar looking file so I attached both.

 

[PeterJ]

Step 1:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

• Download the attachment SFCFix.zip and save it on your desktop.
• Save any work you have open, and close all 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.
• Attach that file to your next reply.

Step 2:
Follow the instructions below to run a scan with the System Update Readiness Tool (SURT) and provide a log.

1. Download SURT for your system. (Windows 7 SP1 x64)
2. Once downloaded, execute the installer, and go through the installation (this process can take around 15-20 minutes).
3. On completion, a log will be created in C:\Windows\Logs\CBS\CheckSUR.log.
4. Attach this log to your next reply.

Alternatively, if these instructions are unclear for you, you can follow the tutorial below.
System Update Readiness Tool (SURT)

 

[obroad]

Partial update because I'm running SURT now.

GOOD NEWS!! I see that it is possible to run elevated/administrator actions now, it wasn't before.

 

[PeterJ]

Great.
Lets see what the new CheckSur log reports.

 

[obroad]

I ended up leaving it running, after half an hour the log reached 13k, but it just kept growing. Here's the log.

 

[obroad]

Also I'm still getting a zero-length DLL in system32 and it also appears in a winsxs folder:

 Volume in drive C has no label.
 Volume Serial Number is BED6-BBD0

 Directory of C:\windows\winsxs\amd64_microsoft-windows-errorreportingconsole_31bf3856ad364e35_6.1.7601.24521_none_b4aebca952add14e

10/10/2019  03:00    <DIR>          .
10/10/2019  03:00    <DIR>          ..
13/07/2009  21:26             3,126 ErrorReportingConsole.ptxml
10/09/2019  03:24         1,281,536 werconcpl.dll
10/09/2019  03:24                 0 wercplsupport.dll
               3 File(s)      1,284,662 bytes
               2 Dir(s)  389,155,340,288 bytes free

 

[obroad]

Also on shutting down it has decided it has an "update" to install.

 

[PeterJ]

Looks like there is more to fix.

Step 1:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

• Download the attachment SFCFix.zip and save it on your desktop.
• Save any work you have open, and close all 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.

Step 2:
Start the System Update Readiness Tool (SURT) again.
On completion, attach the logfile C:\Windows\Logs\CBS\CheckSUR.log to your next reply.

 

[obroad]

The tool is stuck in a seemingly endless loop. It appears to be spamming cbs.log with the same sequence of steps over and over.

I think I'll need to find a way to abort it.

Looks like the trustedinstaller service is broken again (it had been working), so that might be a setback.

 

[obroad]

Right now even SFC won't run. I've run it from repair mode again but I don't think it is logging the result as there is no new entry in cbs.log.
The trustedinstaller service won't run now and both SFC and SURT appear to depend on this, so the CheckSUR.log file is still yesterdays.

Right now the only thing I can think to do is to boot into the recovery drive and use the "sfc /scannow /offbootdir=d:\ /offwindir=d:\windows" settings and send you the outcome of that but it isn't logging it so there's nothing new to send.

 

[PeterJ]

Looks like the trustedinstaller service is broken again (it had been working), so that might be a setback.

Weird, the fix contained only files for the folder \packages, nothing related to the trustedinstaller.

Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.

1. Download the Farbar Recovery Scan Tool and save it to your Desktop:
   64-bit: Downloading Farbar Recovery Scan Tool
   Note: Your antivirus program may report FRST incorrectly as an infection. If so, disable the real-time protection when downloading and running FRST.
   
   
2. Download the attachment fixlist.txt and save it to your desktop.
3. Right-click on FRST64.exe and select "Run as administrator".
4. Press the Fix button.
5. The tool will now process fixlist.txt.
6. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
7. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
8. Attach the logfile Fixlog.txt to your next reply.

 

[obroad]

Here it is.

 

[PeterJ]

Step 1:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

• Download the attachment SFCFix.zip and save it on your desktop.
• Save any work you have open, and close all 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.

Step 2:
Restart the machine.
Run the command sfc /scannow in a elevated commandprompt and report the result.
If it fails attach the file cbs.log to your next reply.

 

[obroad]

Here's the latest CBS.log, the SFCfix job seems to have worked as SFC /scannow ran this time. It still reports unable to fix some things.

After running the SFC /scannow and shutting down it is trying to install an "update". I'm going to wait and see.