Windows Update/SFC Issue Windows 7 SP1 64 bit SFC & SFCFix unable to fix corrupt files

[daveguitaruno]

Hi SleepyDude,

Here is the Checksur.log as requested

 

[SleepyDude]

Now SURT is helping...

I need a fresh copy of the registry:

Retrieve the Components Hive

1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file
2. Please copy the COMPONENTS 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. If file will is too large to upload to the forum please share the file using a service like Dropbox, OneDrive, Google Drive, or upload to www.sendspace.com and just provide the link for the file here

Export Registry Hive (CBS)

• download the script ExportCBSRegistry2.cmd and save it to the Desktop
• right-click the file ExportCBSRegistry2.cmd and select Run as administrator
• when the script ends a new file called SoftwareCBS.zip will be located on the Desktop
• If the zip file is too large to upload to the forum please share the file using a service like Dropbox, OneDrive, Google Drive, or upload to www.sendspace.com and just provide the link for the file here

Export Registry keys (SBS)

• download the script ExportSbSRegistry.cmd and save it to the Desktop
• right-click the file ExportSbSRegistry.cmd and select Run as administrator
  
• when the script ends a new file called SoftwareSBS.zip will be located on the Desktop
• If zip file is too large to upload to the forum please share the file using a service like Dropbox, Google Drive, etc. or upload to SendSpace and just provide the link for the file here

 

[daveguitaruno]

Here you are. I had to reboot to send you the Components file

 

[SleepyDude]

Hi,

I need some time to prepare a fix but I would like to alert you that something is most likely wrong with your computer! you should run some Memory and Hard Disk tests.

The first copy of the registry that you uploaded didn't have the following error that exists on the last uploaded copy:

From the last CheckSur.log:

(f) CBS Registry Error 0x00000002 Microsoft-Windows-RemoteAssistance-Package-Client~31bf3856ad364e35~amt64~zh-HK~0.0.0.0

the correct key is:

Microsoft-Windows-RemoteAssistance-Package-Client~31bf3856ad364e35~amd64~zh-HK~0.0.0.0

Those called bitshifts are often related with RAM problems!

 

[daveguitaruno]

I have previously extensively checked my RAM with Memcheck 86+ no errors came up I've ran scandisk on my HDD they both came up fine, but that does worry me.
I've scan for viruses and nothing has come up. I regularly scan for malware as well

 

[SleepyDude]

Did you run memtest 86+ untill it completes a complete round of tests? it can take a long time depending on the amount of memory.

For the HDD did you use the manufacturer diagnostic tool if available? Not sure what is scandisk.

 

[daveguitaruno]

I did run 86+ for several of rounds of all the tests, it took hours and didn't highlight any problems. The Harddrive is Western Digitial, I didn't use their specific diagnostic tool.
I have had a few BSoD's recently which did flag up "memory error". I have two 8Gb sticks of HyperX memory, which I thought was supposed to be very good.

 

[SleepyDude]

I did run 86+ for several of rounds of all the tests, it took hours and didn't highlight any problems. The Harddrive is Western Digitial, I didn't use their specific diagnostic tool.

Its highly recommended to use their tool, sometimes the tool can offer to "repair" bad sectors and if the drive is under warranty they want the diagnostic error code generated to accept the RMA.

I have had a few BSoD's recently which did flag up "memory error". I have two 8Gb sticks of HyperX memory, which I thought was supposed to be very good.

You may want to post on your BSOD section, there are good analysts there that could help you check what is going on. Is the memory brand new? everything electronics can fail! sometimes a bad configuration or a bad motherboard can create problems that point to memory...

 

[SleepyDude]

Lets see if its possible to continue working...


SFCFix Script

!!! WARNING !!! The following fix is only relevant for this system and no other, applying this fix on another computer will not work and most likely will cause problems...

• Download SFCFix.exe (by Niemiro) and save it to the Desktop
• Download the file SFCScript.txt, attached below, and save this to your Desktop
• On your Desktop, make sure you have the two files:
  
  SFCFix.exe and
  
  SFCScript.txt
• Drag the file SFCScript.txt onto the file SFCFix.exe and release it
• The SFCFix tool will process the script
• Upon completion, a log file SFCFix.txt should be created on your Desktop
• Open the SFCFix.txt log and copy & paste the contents to your post

 

[daveguitaruno]

Here's the dmp files from the minidump folder

 

[daveguitaruno]

SFCFix version 3.0.2.0 by niemiro.
Start time: 2019-06-13 00:02:41.293
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at C:\Users\Dave\Desktop\SFCScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-RemoteAssistance-Package-Client~31bf3856ad364e35~amd64~zh-HK~0.0.0.0.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\7050837ff44..6cda410288b_31bf3856ad364e35_6.1.7601.24475_5a218aedb1350127.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\013ba29af72..af2c3b421cf_31bf3856ad364e35_6.1.7601.24475_cabb7e5123e353f9.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\f2628affe82..31ecdedb813_31bf3856ad364e35_6.1.7601.24475_8b441861a09da6ff.

Successfully deleted registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-RemoteAssistance-Package-Client~31bf3856ad364e35~amt64~zh-HK~0.0.0.0.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-RemoteAssistance-Package-Client~31bf3856ad364e35~amd64~zh-HK~0.0.0.0.

Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-RemoteAssistance-Package-Client~31bf3856ad364e35~amd64~zh-HK~0.0.0.0.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\7050837ff44..6cda410288b_31bf3856ad364e35_6.1.7601.24475_5a218aedb1350127.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\013ba29af72..af2c3b421cf_31bf3856ad364e35_6.1.7601.24475_cabb7e5123e353f9.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\f2628affe82..31ecdedb813_31bf3856ad364e35_6.1.7601.24475_8b441861a09da6ff.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-RemoteAssistance-Package-Client~31bf3856ad364e35~amd64~zh-HK~0.0.0.0.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\7050837ff44..6cda410288b_31bf3856ad364e35_6.1.7601.24475_5a218aedb1350127.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\013ba29af72..af2c3b421cf_31bf3856ad364e35_6.1.7601.24475_cabb7e5123e353f9.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\f2628affe82..31ecdedb813_31bf3856ad364e35_6.1.7601.24475_8b441861a09da6ff.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.0 by niemiro has completed.
Currently storing 57 datablocks.
Finish time: 2019-06-13 00:02:42.377
Script hash: nBlco4jNHR1XXhiRwOK6H/OQ2n+K+wDJ3rXWvg7yyY8=
----------------------EOF-----------------------

 

[SleepyDude]

Hi,

About the dumps I'm not an expert on that area you should start a new thread on the BSOD, Crashes, Kernel Debugging section of the forum.

Run SURT again and post the CheckSur.log please.

 

[daveguitaruno]

Hi Sleepy Dude, thanks I've posted on that section I've had about 6 BSoD's this year, so it's very sporadic.
As I said in my opening a lot of my musical interfaces, dongles and software don't all play nice together.
Again thanks with all the help you given me, I'm really grateful.
Here's my latest CheckSur log

 

[SleepyDude]

Hi,

I have some doubts that the fix done on step #91 worked as expected! Lets try with FRST...

Farbar Recovery Scan Fix

!!! WARNING !!! The following fix is only relevant for this system and no other, running the script on another computer will not work and may cause problems...

• Download FRST or FRST x64 and save it to the Desktop.
  (Please pick the version that matches your operating system's bit type. If you don't know which version matches your system, try FRST if it say that is not compatible with your OS you have to use FRST64)
• Download the file attached and save it to the Desktop as fixlist.txt
  (It's important that both files, FRST or FRST64 and fixlist.txt are in the same location or the fix will not work!)
• Execute FRST/FRST64 right click on the icon
  
  and choose Run as Administrator. Make sure all other windows are closed.
  
  
• Press the Fix button just once and Wait. After the fix the system needs to restart if the tool does not request it please Restart the computer.
• The tool will make a log (Fixlog.txt) on the same location as FRST/FRST64 please post it in your next reply.

 

[daveguitaruno]

Hi SleepyDude,

I will reboot shortly here's the FixLog

 

[SleepyDude]

Ok, after that run SURT again and post the Checksur.log please.

 

[daveguitaruno]

Hi SleepyDude,

Here you are:

 

[SleepyDude]

Export Registry Hive (CBS)

• download the script ExportCBSRegistry2.cmd and save it to the Desktop
• right-click the file ExportCBSRegistry2.cmd and select Run as administrator
• when the script ends a new file called SoftwareCBS.zip will be located on the Desktop
• If the zip file is too large to upload to the forum please share the file using a service like Dropbox, OneDrive, Google Drive, or upload to www.sendspace.com and just provide the link for the file here

 

[daveguitaruno]

Thank you SleepyDude,
Here you are

 

[SleepyDude]

Hi,

From a Command Prompt running as Administrator run this command:
dir /s /A %systemroot%\Microsoft-Windows-RemoteAssistance-Package-Client~31bf3856ad364e35~amt64*

Let me now if it find anything and where.