[SOLVED] KB4524570 fails with 0x80073712 for on Win 10, DISM fails with 14098, SFC fails

[turban]

Hello to you all on Sysnative forums, that's my first post!

I've recently encountered issue with Win 10 Pro updates.
It began to throw 0x80073712 (meaning that one or more required files by Windows Update are missing or damaged) for "2019-11 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4524570)".
When I try to skip it and install "Feature update to Windows 10, version 1909" the effect is the same.

What I've tried:
1. sfc /scannow - throws "Windows Resource Protection could not perform the requested operation", the same when run in Safe mode (minimal)
2. dism /Online /Cleanup-Image /RestoreHealth - (tried with /Sources from win10 iso an /LimitAccess too) keeps failing at 4.5% with "14098: The component store has been corrupted".
3. SFCFix - it stucks after dism phase when it throws error described in step above, after pressing enter finishes with clean result as below:

Spoiler: SFCFix output

SFCFix version 3.0.2.1 by niemiro.
Start time: 2019-11-17 12:52:16.638
Microsoft Windows 10 Build 18362 - amd64
Not using a script file.




AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2019-11-17 12:54:25.979
----------------------EOF-----------------------

3. chkdsk /r - no errors, nothing to fix
4. tried Reset-WindowsUpdate.ps1 - no effect, script "finishes successfully" although it throws and error with some missing registry keys.

Spoiler: Reset-WindowsUpdate.ps1

PS C:\Users\turba\Downloads> .\Reset-WindowsUpdate.ps1
1. Stopping Windows Update Services...
2. Remove QMGR Data file...
3. Renaming the Software Distribution and CatRoot Folder...
4. Removing old Windows Update log...
5. Resetting the Windows Update Services to defualt settings...
sc.exe sdset bits DA;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
sc.exe sdset wuauserv DA;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
6. Registering some DLLs...
7) Removing WSUS client settings...
ERROR: The system was unable to find the specified registry key or value.
ERROR: The system was unable to find the specified registry key or value.
The operation completed successfully.
8) Resetting the WinSock...

Sucessfully reset the Winsock Catalog.
You must restart the computer in order to complete the reset.


Current WinHTTP proxy settings:

Direct access (no proxy server).

9) Delete all BITS jobs...
10) Attempting to install the Windows Update Agent...
11) Starting Windows Update Services...
12) Forcing discovery...
Process complete. Please reboot your computer.

Looking at the script source and my registry these failing registry deletes are:
REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v AccountDomainSid /f
REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v PingID /f
I guess that issue is irrevelant to my problem.
5. tried Reset Windows Update Agent, tried options 2,3,5,6,7,8,9,10,11,12 with no effect, basically that tool does the same thing as the steps done above

Spoiler: resetwue

Microsoft Windows 10 [Version: 10.0.18362.449]
Reset Windows Update Tool.

This tool reset the Windows Update Components.

1. Opens the system protection.
2. Resets the Windows Update Components.
3. Deletes the temporary files in Windows.
4. Opens the Internet Explorer options.
5. Runs Chkdsk on the Windows partition.
6. Runs the System File Checker tool.
7. Scans the image for component store corruption.
8. Checks whether the image has been flagged as corrupted.
9. Performs repair operations automatically.
10. Cleans up the superseded components.
11. Deletes any incorrect registry values.
12. Repairs/Resets Winsock settings.
13. Forces Group Policy Update.
14. Searches Windows updates.
15. Runs SetupDiag (Require .NET Framework 4.6).
16. Explores other local solutions.
17. Explores other online solutions.
18. Downloads the Diagnostic Tools.
19. Restarts your PC.

?. Help. 0. Close.

Select an option:

I'm out of ideas, any help would be appreciated! I really do not want to reinstall OS on my PC...
Thanks in advance!

CBS and DISM logs attached

 

[Sysnative Windows Update]

Hello and welcome!

Let's try the following:

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system 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.

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 provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or SendSpace.

 

[turban]

Thanks for replying!

The problem is that's not immediate error (happening right after I click update) but it takes about 3-5 minutes to happen after I click. That causes the PML files to be about 10GB big, even if I turn off every unnecessary service I can.

Do you need the PML log from the whole update process or just the moment before the error being thrown? Maybe you can give me some guidance how to filter out unnecessary entries in PML log (such as ones with RESULT==SUCCESS for example or Procmon64.exe itself processes).

If you need the log started few seconds before the error please see that: logs.zip

Thanks in advance!

 

[Sysnative Windows Update]

Let's see if this helps:

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 the attached fixlist.txt 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.

 

[turban]

Wow, thanks a lot, it has fixed my issue immediately! Tools like dism and sfc started to work too.
Thank you!

By the way, how did you find out that's due to some 2 registry entries and some reg load? (I would never execute any script from web without just briefly looking what it does)
I've looked at the procmon results too and there were dozens of other erratic entries, how did you know that these 2 are the problem?
I wish I have such skill!

 

[Sysnative Windows Update]

Years of practice

The reg load is the command that loaded the hive in which I needed to execute the fix.

Glad to have assisted.