[SOLVED] SFC detects corruption but can't fix, SFCFix used.

ConductedForce

ConductedForce

Member
Joined
Dec 2, 2021
Posts
13
Backstory here, but let me update since then. Safe mode works, regular start-up is kinda stuck at "Setting up personalized settings". Safe mode with Networking/CMD doesn't load anything (but cmd works in plain Safe Mode).

SFC /scannow fails at 45%, /verifyonly works fine.

I found SFCFix and tried it (it asked for install disk, used upgrade disk). It fixed some stuff but not everything.

Attached is the SFCFix report and my CBS log.

This is Windows 7 Home Premium 64-bit.
 

Attachments

Last edited:
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.
  • 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.
    1p8eDnI.gif
  • 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.
 

Attachments

Additionally, I wanted to add a new "development". I did a registry compare (my taskbar has been different this whole ordeal) and I believe portions of user registry are missing. I did a reverse compare with RegistryChangesView (current registry -> backup hdd registry) which has a bunch of HKCU\Software\.. Keys and Values that are not present in the current registry (backup -> current seemed to show less differences, but I was having snapshot issues). When comparing with my tower that suffered a similar fate as this laptop, and with a fresh VM of Win7, I noticed that when all three are in safemode, the HKCU\Software\Microsoft\Windows\Explorer\ registry entry only contains SessionInfo\ for the two machines, with the VM having standard other keys. Taskband is the Key that works in conjunction with the Taskbar. The fact that the actual Taskbar folder where these shortcuts are kept (%AppData%\Microsoft\Internet Explorer\Quick Launch\User Pinned\TaskBar) has ALL of my shortcuts, but none are present on the taskbar, leads me to believe a registry problem is causing a host of other issues.

I have prepared two reg files, one to restore the "missing" keys and one for certain modified keys between the two. I do have another prospect, the RegBack folder has a reg copy (Windows but no ntuser.dat or usrclass.dat) the day I took the HDD out to copy files. Just before the trouble began.

I've made backups of the registry, but so we're on the right page, and for a second opinion, the locations are:
Windows/System32/config/
(I just took everything but it looks like 5 files mainly)
Windows/System32/RegBack/
Windows/System32/systemprofile/
(TxR and Journal left out)
Users/UsrProfile/ntuser.dat
%appdata%/local/microsoft/windows/usrclass.dat

I haven't tried booting normally yet or any reg changes.
 
Run SFC /SCANNOW in an elevated commandprompt and report the result.
If it fails copy the file c:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.
 
The same file/folder it references is a file, don't know if that makes a difference.

"\SystemRoot\WinSxS\amd64_microsoft-windows-o..calmediadisc-styles_31bf3856ad364e35_6.1.7600.16385_none_dac1eab162daeb45"
 
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.
 

Attachments

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.
    1p8eDnI.gif
  • 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:
Run SFC /SCANNOW in an elevated commandprompt and report the result.
If it fails copy the file C:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.
 

Attachments

Ran it and SFC, no go. I understood why when I looked at the sfcfix.txt. That same "file" which I believe should be a folder. Threw in temporary security access and deleted it, created a folder in its name. There are 10 more files with the naming convention of those folders. I posted the file list earlier (files-in-winsxs.txt). Ran SFCFix a second time (sfcfix4.txt is results) and it worked. SFC now focuses on the next "folder" (CBS4.log). Working on deleting the other 10 and creating folders in their place. Will post results of SFC again.
 

Attachments

Got to 99% before stopping. A "missing object". Looked like a folder that flat didn't exist. I added the folder but I imagine SFC won't complete as the folder will be empty.

EDIT:
SFC finished at 100% but found corrupt files that it couldn't fix. Added log (CBS6.log). I have a sneaking suspicion that you'll want SFCFix run for more info, so I'll do that.
 

Attachments

It's getting a bit confusing with the latest fixes being done. Please do following only.

Restart the machine.
Run the command SFC /SCANNOW in an elevated commandprompt and report the result.
If it fails, attach the zipped cbs.log to your next reply.
 
100% complete, no integrity violations. Restart was probably what it needed last. You have earned your donation for the week.
 
Thanks for the donation. Well done too.

Follow the instructions below to cleanup the tools and logfiles used in this thread.
Rename the file FRST64.exe to uninstall.exe and run it. This will remove all files and folders created by FRST and the tool itself.
Reboot the machine to complete.
You may remove all other tools and log files.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top