[7SP1 x64] SFC keeps finding corrupt files and repairing them

I do have a copy of Windows 10 lying around, but I'd rather find out the source of the issues and fix them if possible, reinstalling Windows being a last resort for me.
 
I wasn't thinking of reinstalling, but rather upgrading to the latest version, so all of your files would remain intact.

Let's see if there's something wrong in the registry:

Retrieve Components Hive
 1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
4. The file will likely be too large to upload here so please upload toa file sharing service and just provide the link here.
 
Step#1 - Capture Process Monitor Trace
 1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Cause the error just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
11908d1430506241-windows-updates-fail-repeatedly-stop-jpg


4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and attach the LogFile.PML file as well as your CBS.log
 
Step#1 - Export SideBySide



  1. Click on the Start button and in the search box, type regedit
  2. When you see regedit on the list, right-click on it and select Run as administrator
  3. When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide
  4. Once selected, click File > Export....
  5. Change the Save as type: to Registry Hive Files (*.*)
  6. Name this file SxS (with no file extension) and save it to your Desktop.


Upload it to a filesharing service of your choice and provide the link.
 
You have a corruption within your registry.

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. 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.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply
 

Attachments

Edited user name out.

Code: 
Fix result of Farbar Recovery Scan Tool (x64) Version: 27.01.2018
Ran by **** (04-02-2018 05:46:27) Run:1
Running from C:\Users\****\Desktop
Loaded Profiles: **** (Available Profiles: ****)
Boot Mode: Normal
==============================================

fixlist content:
*****************
CreateRestorePoint:
[-HKLM\Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-directx-ÿÿÿÿÿÿÜS|ÝSÑ]
*****************

Restore point was successfully created.
HKLM\Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-directx-ÿÿÿÿÿÿÜS|ÝSÑ => key not found

==== End of Fixlog 05:47:01 ====
 
Didn't work. Try this one. P.S. May I ask why are you editing the user name out?

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. 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.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply
 

Attachments

Code: 
Fix result of Farbar Recovery Scan Tool (x64) Version: 27.01.2018
Ran by **** (04-02-2018 05:58:38) Run:2
Running from C:\Users\****\Desktop
Loaded Profiles: **** (Available Profiles: ****)
Boot Mode: Normal
==============================================

fixlist content:
*****************
CreateRestorePoint:
[-HKLM\Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-directx-yyyyyy�S|�SN]
*****************

Restore point was successfully created.
HKLM\Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-directx-yyyyyy�S|�SN  => key not found

==== End of Fixlog 05:58:49 ====

>May I ask why are you editing the user name out?
Just a habit of mine for privacy.
 
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