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

daveguitaruno

daveguitaruno

Contributor
Joined
May 1, 2019
Posts
103
Location
United Kingdom
I have a music studio machine, this is for a AMD phenom II CPU on a 970 Extreme 4 six core Mobo 16Gb RAM Running Windows 7 SP1 64-bit OS (OEM Version!!!).
I have an unbelievable amount of (All legal) audio plugins, software, PACE anti-piracy, an assortment of dongles and a number of DAW programs, loads of configuration changes.
This and it's predecessors is (and always has been) a precarious system(s). Early this year I've been having Windows update and SFC/DISM issues.
In the process of trying to fix them I've had to restore an Acronis True image quite a few times (Acronis, now only produces corrupt image files)
so I have to go back everytime to a several months old image and have to do a plethora of fixes.
I've rebuilt my studio time and time again, as the audio plugins don't play nice with each other Waves, Gobbler, TC Electronic Antares (and many more).

I really don't want to do a complete re-install as it will take at least two months to get the system fully working again.
Also I have some legacy TCElectronics Powercore additional purchased plugins. Which I can't re-install as TC Electronic have disabled their activation server last year.

My day job is I'm a software developer/Programmer and I like to think I know my way fairly well around a computer (but I'm no OS/Networking god).
My passion (and sometimes night job) is a musician/guitarist/singer/songwriter.
I'd really like to go back to using my studio to record and master music again and not spend months fighting Microsoft's OS.
I have learnt quite a lot in the past fex months about:
SFC /scannow,
the great SFCFix.exe tool (it's really great)
DISM (Windows 7 users DISM syntax is a little different from Windows 8 & 10 syntax that is plastered everywhere (try this dism /online /cleanup-image /scanhealth),
SURT,
Windows Update Fixing Tool: WindowsUpdate.diagcab

and sadly about OEM OS (Don't buy OEM, or PC's with OEM OS is my advice)
What I found out is OEM OS can only run on your hardware, so major hardware upgrade like a different Mobo invalidates it, but the most serious bit is you can't do an in place upgrade.
When you have corrruptions/problems etc You get the advice: "Well just do an in-place upgrade and voila!" It kindly goes through taking an age to about 99% and then it rolls it all back.
I also have a suspicion that certain Security updates are different from the Full retail version.

SFC & SFCfix hit a problem with "component NetFx-Debugging_msdia70 and file diasymreader.dll. File is reported as corrupt by SFC. CORRUPT: diasymreader.dll of component NetFx-Debugging_msdia70."
Along with a changing list of "SURT total detected corruption count: 14"
I've done TakeOwn /f <path>\diasymreader.dll and icacls <path>\diasymreader.dll /grant administrators:f from an all nice and sparkly clean OS drive (same version different OS key)
It keeps coming back protesting with hash mismatch

Here are uploaded my freshest logs
Please can someone help me I've been at this for months
 

Attachments

An additional bit, while I was preparing the logs, I ran the WUT after submitting the files above, It mentioned that I had error 0x80070057, but for the first time spotted in the WUT the advanced troubleshooting, it said I was missing an Update kb4019264-x64 which I downloaded and installed this fixed one outstanding problem. I also found on a site a fix of adding a Registry Key Value HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\SystemCertificates
Creating a new DWORD32 entry of CopyFileBufferedSynchronousIo and setting it to Hexadecimal 1. I reran the WUT and it stated that error 0x80070057 was fixed. However when I rebooted and ran Windows Update is still failing with the same error message 0x80070057 and I still have the same corrupt files. I have the log for this first WUT run, but not the WUT run that was fixed I have one I've just run now see attached.
 

Attachments

Last edited:
I know you are all really busy, so I reran the SURT tool and followed your useful instructions here on
How to fix Windows Update errors using DISM (DISM.log) or the System Update Readiness Tool / SURT (CheckSUR.log) on how to go through the SURT log and fix errors
It identified the following Unavailable repair files:
winsxs\manifests\amd64_microsoft-windows-a..ence-mitigations-c1_31bf3856ad364e35_6.1.7601.24001_none_6ad959b622048bdb.manifest
servicing\packages\Package_273_for_KB4019264~31bf3856ad364e35~amd64~~6.1.1.3.mum
servicing\packages\Package_273_for_KB4019264~31bf3856ad364e35~amd64~~6.1.1.3.cat
The .mum and .cat files were no sweat to fix Expand and fix but the manifest what a nightmare, I didn't understand how you said to find the kb from the manifest file, but I found this amazing article on SevenForums Windows Update Manifests - Manually Trace Through Registry - Windows 7 Help Forums it explained the rather torturous way to find the kb file. But it is not for the faint hearted novice user so that said I replaced all the above files with clean versions. Reran the SURT and those most serious problems are resolved. The SURT detected 110 more minor issues of which it fixed 90, so I still have 20 more items to make that pristine.
I also followed the same reasoning for my NetFx-Debugging_msdia70, Version = 6.1.7601.18523 corrupt file so I got a clean version of that took ownership of the corrupt folder and file and copied over the clean version. I reran SFC and I still have the same corrupt files it says the store has hash mismatch. This is making me think that either that kb contains corrupt files or I have other problems. I could really use someone smarter than me to bounce ideas off.
 
Last edited:
Here's my latest SURT logs now with 12 errors, most of which seem to revolve around Avast! anti-virus
The 3 exceptions look a bit nasty
(f) CSI Missing Identity 0x00000000 appid 10c00275e1e19c1e845ea5b85ecf7e98b28b21f6f4d6296ec4e2e678f65f5454
(f) CSI Payload File Corrupt 0x00000000 smipi.dll amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0
(f) CSI Missing Deployment Key 0x00000000 33ec9c6d943..b8657aaeb00_31bf3856ad364e35_6.1.7601.23591_8d4f62a8a3f5c54d HKLM\Components\CanonicalData\Deployments
I'm hoping that I can find an old components hive in one of my older Acronis TI images that I might be able to extract the missing identity and the Missing Deployment.
I know I'm ploughing my way through problems here, but I could really do with a hand to sort out my remaining problems.
 

Attachments

Hi,

Please provide the current components hive.

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
 
BTW, I've reduced my SURT list to one problem. On the SFC I still have the annoying remaining few corrupt files and the NetFx-Debugging_msdia70, Version = 6.1.7601.18523 diasymreader.dll problem. Needless to say Windows update is still broken with error 80070057
 

Attachments

Thanks for the update. Now please avoid any other fix's because they can interfere with my work...

I will post a fix for you shortly.
 
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 SFCFIX.ZIP, attached below, and save this to your Desktop
  • On your Desktop, make sure you have the two files:
    myjIXnC.png
    SFCFix.exe and
    sfpcJCen14An3ndjNGCI7mByhjHJud.png
    SFCFIX.zip
  • Drag the file SFCFIX.zip 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
 

Attachments

Thanks for your reply and help, here it is:

SFCFix version 3.0.1.0 by niemiro.
Start time: 2019-06-02 21:13:17.913
Microsoft Windows 7 Service Pack 1 - amd64
Using .zip script file at C:\Users\Dave\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_netfx-debugging_msdia70_b03f5f7f11d50a3a_6.1.7601.18523_none_5d8e7c2cbcdbcc40\diasymreader.dll
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-directwrite.resources_31bf3856ad364e35_7.1.7601.16492_tr-tr_6ee9aab7a6ef961c\DWrite.dll.mui

Successfully copied file C:\Users\Dave\AppData\Local\niemiro\Archive\WinSxS\amd64_netfx-debugging_msdia70_b03f5f7f11d50a3a_6.1.7601.18523_none_5d8e7c2cbcdbcc40\diasymreader.dll to C:\Windows\WinSxS\amd64_netfx-debugging_msdia70_b03f5f7f11d50a3a_6.1.7601.18523_none_5d8e7c2cbcdbcc40\diasymreader.dll.
Successfully copied file C:\Users\Dave\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-directwrite.resources_31bf3856ad364e35_7.1.7601.16492_tr-tr_6ee9aab7a6ef961c\DWrite.dll.mui to C:\Windows\WinSxS\amd64_microsoft-windows-directwrite.resources_31bf3856ad364e35_7.1.7601.16492_tr-tr_6ee9aab7a6ef961c\DWrite.dll.mui.

Successfully restored ownership for C:\Windows\WinSxS\amd64_netfx-debugging_msdia70_b03f5f7f11d50a3a_6.1.7601.18523_none_5d8e7c2cbcdbcc40\diasymreader.dll
Successfully restored permissions on C:\Windows\WinSxS\amd64_netfx-debugging_msdia70_b03f5f7f11d50a3a_6.1.7601.18523_none_5d8e7c2cbcdbcc40\diasymreader.dll
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-directwrite.resources_31bf3856ad364e35_7.1.7601.16492_tr-tr_6ee9aab7a6ef961c\DWrite.dll.mui
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-directwrite.resources_31bf3856ad364e35_7.1.7601.16492_tr-tr_6ee9aab7a6ef961c\DWrite.dll.mui
PowerCopy:: directive completed successfully.




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\33ec9c6d943..b8657aaeb00_31bf3856ad364e35_6.1.7601.23591_8d4f62a8a3f5c54d.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\33ec9c6d943..b8657aaeb00_31bf3856ad364e35_6.1.7601.23591_8d4f62a8a3f5c54d.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.1.0 by niemiro has completed.
Currently storing 22 datablocks.
Finish time: 2019-06-02 21:13:19.273
Script hash: 2B3HeYjPA0NdDBqc1mWYTBYyWBvYAhQAKvpifflF3Rw=
----------------------EOF-----------------------
 
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2019-06-02 21:28

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f) CSI Catalog Missing 0x00000002 b3ba019b97b4bfc04b0ee73682a629ae1ac4a30a6b62b247361a16725d906011.cat 33ec9c6d943..b8657aaeb00_31bf3856ad364e35_6.1.7601.23591_8d4f62a8a3f5c54d Missing catalog or invalid CatalogThumprint
(fix) CSI Catalog Missing CSI File Replaced Deleted CatalogThumbprint

Summary:
Seconds executed: 505
Found 1 errors
Fixed 1 errors
CSI Catalog Missing Total count: 1
Fixed: CSI Catalog Missing. Total count: 1
Customer Experience report successfully uploaded. Thank you for participating. For more information, see the Microsoft Customer Experience Improvement Program on the Microsoft web site.
 
After reboot and rerun:

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2019-06-02 21:59

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 637
No errors detected
Customer Experience report successfully uploaded. Thank you for participating. For more information, see the Microsoft Customer Experience Improvement Program on the Microsoft web site.
 
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