[SOLVED] Windows update fails to install cumulative updates (WS2012R2)

AimarPL · Sep 23, 2019

Hi,
I'm having an issue with windows update on WS2012R2 server. It only fails to install monthly, cumulative updates.

SFCFix didn't show any issues:

Code:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2019-09-23 14:56:24.246
Microsoft Windows Server 2012 R2 Update 3 - 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-09-23 14:57:10.663
----------------------EOF-----------------------

CBS log is uploaded here

I would appreciate any help on this one.

Thank you!

Sysnative Windows Update · Sep 23, 2019

Hi!

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.

AimarPL · Sep 23, 2019

Here's execution log:

Code:

Fix result of Farbar Recovery Scan Tool (x64) Version: 22-09-2019
Ran by t1-admin (23-09-2019 16:45:36) Run:12
Running from C:\Users\adminsl\Desktop
Loaded Profiles: t1-admin & CitrixTelemetryService (Available Profiles: t1-admin)
Boot Mode: Normal
==============================================

fixlist content:
*****************
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-s..spellcheck.binaries_31bf3856ad364e35_0.0.0.0_none_a2c6138737438a14]
StartRegedit:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-s..spellcheck.binaries_31bf3856ad364e35_0.0.0.0_none_a2c6138737438a14]
"Package_57_for_KB2919394~31bf3856ad364e35~amd64~~6.3.1.3.2919394-59_neutral_GDR"="6.3.9600.16500@4"
"Package_1726_for_KB2919355~31bf3856ad364e35~amd64~~6.3.1.14.2919355-3669_neutral_GDR"="6.3.9600.16500@4"
"Package_873_for_KB3000850~31bf3856ad364e35~amd64~~6.3.1.8.3000850-2559_neutral_GDR"="6.3.9600.17415@4"
"Package_638_for_KB4103725~31bf3856ad364e35~amd64~~6.3.1.4.4103725-1014_neutral_GDR"="6.3.9600.18937@4"
"Package_641_for_KB4284815~31bf3856ad364e35~amd64~~6.3.1.6.4284815-1023_neutral_GDR"="6.3.9600.18937@4"
"Package_642_for_KB4338815~31bf3856ad364e35~amd64~~6.3.1.9.4338815-1031_neutral_GDR"="6.3.9600.18937@4"
"Package_642_for_KB4338831~31bf3856ad364e35~amd64~~6.3.1.11.4338831-1031_neutral_GDR"="6.3.9600.18937@4"
"Package_642_for_KB4343898~31bf3856ad364e35~amd64~~6.3.1.9.4343898-1031_neutral_GDR"="6.3.9600.18937@4"
"Package_599_for_KB4093114~31bf3856ad364e35~amd64~~6.3.1.5.4093114-969_neutral_GDR"="6.3.9600.18937@4"
"Package_642_for_KB4457129~31bf3856ad364e35~amd64~~6.3.1.7.4457129-1036_neutral_GDR"="6.3.9600.18937@4"
"Package_643_for_KB4471320~31bf3856ad364e35~amd64~~6.3.1.4.4471320-1040_neutral_GDR"="6.3.9600.18937@4"
"Package_643_for_KB4480963~31bf3856ad364e35~amd64~~6.3.1.5.4480963-1040_neutral_GDR"="6.3.9600.18937@4"
"Package_643_for_KB4487000~31bf3856ad364e35~amd64~~6.3.1.12.4487000-1042_neutral_GDR"="6.3.9600.18937@4"
"Package_676_for_KB4507448~31bf3856ad364e35~amd64~~6.3.1.9.4507448-1100_neutral_GDR"="6.3.9600.18937@4"
"Package_676_for_KB4507463~31bf3856ad364e35~amd64~~6.3.1.12.4507463-1101_neutral_GDR"="6.3.9600.18937@4"
"Package_716_for_KB4512488~31bf3856ad364e35~amd64~~6.3.1.5.4512488-1143_neutral_GDR"="6.3.9600.18937@4"
EndRegedit:
*****************

"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-s..spellcheck.binaries_31bf3856ad364e35_0.0.0.0_none_a2c6138737438a14" => not found
Registry ====> ERROR: Error accessing the registry.

==== End of Fixlog 16:45:54 ====

Sysnative Windows Update · Sep 23, 2019

Please take ownership of the Component Based Servicing Key and then retry the fix. Let me know if you need instructions.

AimarPL · Sep 23, 2019

if possible, would be nice - dunno which key (or file?) is it
Thanks in advance!

AimarPL · Sep 23, 2019

well, it wasn't so complicated, path was in the log

took the ownership, set perms and here's the execution log:

Code:

Fix result of Farbar Recovery Scan Tool (x64) Version: 22-09-2019
Ran by t1-adminslempluk (23-09-2019 17:18:26) Run:13
Running from C:\Users\admin\Desktop
Loaded Profiles: t1-admin & CitrixTelemetryService (Available Profiles: t1-admin & CitrixTelemetryService)
Boot Mode: Normal
==============================================

fixlist content:
*****************
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-s..spellcheck.binaries_31bf3856ad364e35_0.0.0.0_none_a2c6138737438a14]
StartRegedit:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-s..spellcheck.binaries_31bf3856ad364e35_0.0.0.0_none_a2c6138737438a14]
"Package_57_for_KB2919394~31bf3856ad364e35~amd64~~6.3.1.3.2919394-59_neutral_GDR"="6.3.9600.16500@4"
"Package_1726_for_KB2919355~31bf3856ad364e35~amd64~~6.3.1.14.2919355-3669_neutral_GDR"="6.3.9600.16500@4"
"Package_873_for_KB3000850~31bf3856ad364e35~amd64~~6.3.1.8.3000850-2559_neutral_GDR"="6.3.9600.17415@4"
"Package_638_for_KB4103725~31bf3856ad364e35~amd64~~6.3.1.4.4103725-1014_neutral_GDR"="6.3.9600.18937@4"
"Package_641_for_KB4284815~31bf3856ad364e35~amd64~~6.3.1.6.4284815-1023_neutral_GDR"="6.3.9600.18937@4"
"Package_642_for_KB4338815~31bf3856ad364e35~amd64~~6.3.1.9.4338815-1031_neutral_GDR"="6.3.9600.18937@4"
"Package_642_for_KB4338831~31bf3856ad364e35~amd64~~6.3.1.11.4338831-1031_neutral_GDR"="6.3.9600.18937@4"
"Package_642_for_KB4343898~31bf3856ad364e35~amd64~~6.3.1.9.4343898-1031_neutral_GDR"="6.3.9600.18937@4"
"Package_599_for_KB4093114~31bf3856ad364e35~amd64~~6.3.1.5.4093114-969_neutral_GDR"="6.3.9600.18937@4"
"Package_642_for_KB4457129~31bf3856ad364e35~amd64~~6.3.1.7.4457129-1036_neutral_GDR"="6.3.9600.18937@4"
"Package_643_for_KB4471320~31bf3856ad364e35~amd64~~6.3.1.4.4471320-1040_neutral_GDR"="6.3.9600.18937@4"
"Package_643_for_KB4480963~31bf3856ad364e35~amd64~~6.3.1.5.4480963-1040_neutral_GDR"="6.3.9600.18937@4"
"Package_643_for_KB4487000~31bf3856ad364e35~amd64~~6.3.1.12.4487000-1042_neutral_GDR"="6.3.9600.18937@4"
"Package_676_for_KB4507448~31bf3856ad364e35~amd64~~6.3.1.9.4507448-1100_neutral_GDR"="6.3.9600.18937@4"
"Package_676_for_KB4507463~31bf3856ad364e35~amd64~~6.3.1.12.4507463-1101_neutral_GDR"="6.3.9600.18937@4"
"Package_716_for_KB4512488~31bf3856ad364e35~amd64~~6.3.1.5.4512488-1143_neutral_GDR"="6.3.9600.18937@4"
EndRegedit:
*****************

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-s..spellcheck.binaries_31bf3856ad364e35_0.0.0.0_none_a2c6138737438a14 => not found
Registry ====> The operation completed successfully.


==== End of Fixlog 17:18:37 ====

WU still fails with error code 80073712
here's CBS log: CBS

Sysnative Windows Update · Sep 23, 2019

Thanks.

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.

AimarPL · Sep 24, 2019

Hi, data is captured and available under following url.

Sysnative Windows Update · Sep 24, 2019

Hi!

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.

AimarPL · Sep 25, 2019

It looks good! :)
cumulative update is installed, but there's one small issue left - SFC says there are some corrupt files and it's can't fix it, but I should be able to find them in cbs log;
Would you please take a look on it?

CBS Log

Thank you in advance!

Sysnative Windows Update · Sep 25, 2019

Code:

2019-09-24 22:53:34, Info                  CSI    00000ed3 [SR] Cannot repair member file [l:24{12}]"Narrator.exe" of Microsoft-Windows-Narrator, Version = 6.3.9600.17415, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file cannot be checked
2019-09-24 22:53:34, Info                  CSI    00000ed4 [SR] Cannot repair member file [l:24{12}]"Narrator.exe" of Microsoft-Windows-Narrator, Version = 6.3.9600.17415, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file cannot be checked

The files are not corrupt. They are inaccessible which can be indicative of HDD failure.

AimarPL · Sep 26, 2019

Hi,
indeed it was only narrator file broken :) I have taken a copy of it from similar system and now it works as expected!

Thank you very much!
Once again you've made great work, I'm truly impressed with your commitment here mate :)

Sysnative Windows Update · Sep 26, 2019

Thank you very much for your kind words. Much appreciated.

[SOLVED] Windows update fails to install cumulative updates (WS2012R2)

AimarPL

Contributor

Sysnative Windows Update

Inactive

Attachments

AimarPL

Contributor

Sysnative Windows Update

Inactive

AimarPL

Contributor

AimarPL

Contributor

Sysnative Windows Update

Inactive

AimarPL

Contributor

Sysnative Windows Update

Inactive

Attachments

AimarPL

Contributor

Sysnative Windows Update

Inactive

AimarPL

Contributor

Sysnative Windows Update

Inactive