Server 2016 - Update Errors

adamb · Aug 23, 2020

Hi,

I have been fighting with two Server 2016 Domain Controllers, which I cannot get to update for me... they have been reporting back: 0x80073712 (ERROR_SXS_COMPONENT_STORE_CORRUPT)

Rather than fight with two I have picked one of the servers to try to resolve first. It's trying to install KB4565511 - 2020-07 CU Server 2016, after a few attempts no luck, i unapproved this on WSUS and it tried to install KB4561616 - 2020-06 CU Server 2016 instead however the same issue occurred.

I have attached the CBS zip folder.

This was the result of RestoreHealth...

Code:

PS C:\Windows\system32> Dism /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.14393.0

Image Version: 10.0.14393.0

[==                         4.5%                           ]
Error: 1168

Element not found.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

This was the output of SFCFix

Code:

Checking CheckSUR.log . . .
Checking CheckSUR.persist.log . . .

Attempting repair . . .
Stage 1
Stage 2
Stage 3

Due to the nature of your corruptions, scan times have been extended by
approximately 15-20 minutes. Please be patient and allow the operation to
complete.


Deployment Image Servicing and Management tool
Version: 10.0.14393.0

Image Version: 10.0.14393.0

[==                         4.5%                           ]
Error: 1168

Element not found.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log



SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-08-23 22:37:02.576
Microsoft Windows Server 10 Build 14393 - 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: 2020-08-23 22:39:00.831
----------------------EOF-----------------------

As I was working my way through the logs, some of the stuff which stood out to me:

Code:

Checking System Update Readiness.

(w)    CBS Package Index Package Missing    0x80070490    Microsoft-Windows-Security-LsaTrustlet-Package~31bf3856ad364e35~amd64~~0.0.0.0    Microsoft-Windows-Security-LsaTrustlet-Package~31bf3856ad364e35~amd64~~10.0.14393.0   


2020-08-23 19:55:07, Info                  CBS    Failed to get child object: Package_5269_for_KB4088� [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2020-08-23 19:55:07, Info                  CBS    Failed to enumerate packages. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2020-08-23 19:55:07, Info                  CBS    Failed to check package index [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2020-08-23 19:55:08, Info                  CBS    Failed to check CBS watchlist consistency [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2020-08-23 19:55:08, Info                  CBS    Failed to check CBS store. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]

2020-08-23 20:25:46, Info                  CBS    Failed to call EnumDeploymentReferences on deployment: amd64_0a7887f4a7c67d9afd51862b2111003c_31bf3856ad364e35_10.0.14393.479_none_689d14721155886c [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]

Would appreciate any advice or suggestions on the best way to move forward! As these are both DCs, I would prefer to try resolve this to prevent me having to re-build

Thanks,
Adam

Sysnative Windows Update · Aug 24, 2020

Hi!

I'll check this by the end of the day.

Sysnative Windows Update · Aug 24, 2020

Hi!

Please do the following:

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.

adamb · Aug 25, 2020

Hi softwaremaniac,

Many thanks for the reply, I do appreciate your assistance! - I have ran the above and got the below contents:

Code:

Fix result of Farbar Recovery Scan Tool (x64) Version: 23-08-2020
Ran by administrator (25-08-2020 20:11:37) Run:1
Running from C:\Users\Administrator.TJL\Desktop
Loaded Profiles: administrator
Boot Mode: Normal
==============================================

fixlist content:
*****************
cmd: reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_0a7887f4a7c67d9afd51862b2111003c_31bf3856ad364e35_10.0.14393.479_none_689d14721155886c]
[-HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\0a7887f4a7c..62b2111003c_31bf3856ad364e35_10.0.14393.479_689d14721155886c]
StartRegedit:
[HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_0a7887f4a7c67d9afd51862b2111003c_31bf3856ad364e35_10.0.14393.479_none_689d14721155886c]
"S256H"=hex:58,81,77,4b,ed,ce,9a,16,a5,f0,06,13,ec,3f,52,db,fb,eb,84,f9,92,d5,\
  bc,57,4a,34,b0,65,d1,71,32,02
"identity"=hex:30,61,37,38,38,37,66,34,61,37,63,36,37,64,39,61,66,64,35,31,38,\
  36,32,62,32,31,31,31,30,30,33,63,2c,20,43,75,6c,74,75,72,65,3d,6e,65,75,74,\
  72,61,6c,2c,20,56,65,72,73,69,6f,6e,3d,31,30,2e,30,2e,31,34,33,39,33,2e,34,\
  37,39,2c,20,50,75,62,6c,69,63,4b,65,79,54,6f,6b,65,6e,3d,33,31,62,66,33,38,\
  35,36,61,64,33,36,34,65,33,35,2c,20,50,72,6f,63,65,73,73,6f,72,41,72,63,68,\
  69,74,65,63,74,75,72,65,3d,61,6d,64,36,34,2c,20,76,65,72,73,69,6f,6e,53,63,\
  6f,70,65,3d,4e,6f,6e,53,78,53
"CF"=dword:0000000c
"c!0a7887f4a7c..62b2111003c_31bf3856ad364e35_10.0.14393.479_689d14721155886c"=hex:

[HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\0a7887f4a7c..62b2111003c_31bf3856ad364e35_10.0.14393.479_689d14721155886c]
"appid"=hex:30,61,37,38,38,37,66,34,61,37,63,36,37,64,39,61,66,64,35,31,38,36,\
  32,62,32,31,31,31,30,30,33,63,2c,20,43,75,6c,74,75,72,65,3d,6e,65,75,74,72,\
  61,6c,2c,20,56,65,72,73,69,6f,6e,3d,31,30,2e,30,2e,31,34,33,39,33,2e,34,37,\
  39,2c,20,50,75,62,6c,69,63,4b,65,79,54,6f,6b,65,6e,3d,33,31,62,66,33,38,35,\
  36,61,64,33,36,34,65,33,35,2c,20,50,72,6f,63,65,73,73,6f,72,41,72,63,68,69,\
  74,65,63,74,75,72,65,3d,61,6d,64,36,34,2c,20,76,65,72,73,69,6f,6e,53,63,6f,\
  70,65,3d,4e,6f,6e,53,78,53
"CatalogThumbprint"="ffc44b0bd8ec33d3ff01f14065143d5cb167eb85d9de9398737533262f7a6de0"
"p!CBS_package_3561_for_kb3213986~31bf3856ad364e35~amd64~~10.0.1.1._c780a1d4f538e44e"=hex:50,\
  00,00,00,01,00,00,00,50,61,63,6b,61,67,65,5f,33,35,36,31,5f,66,6f,72,5f,4b,\
  42,33,32,31,33,39,38,36,7e,33,31,62,66,33,38,35,36,61,64,33,36,34,65,33,35,\
  7e,61,6d,64,36,34,7e,7e,31,30,2e,30,2e,31,2e,31,2e,33,32,31,33,39,38,36,2d,\
  37,30,34,34,5f,6e,65,75,74,72,61,6c,32
"s!CBS_package_3561_for_kb3213986~31bf3856ad364e35~amd64~~10.0.1.1._c780a1d4f538e44e"=hex:50,\
  00,00,00,00,00,00,00,50,61,63,6b,61,67,65,5f,33,35,36,31,5f,66,6f,72,5f,4b,\
  42,33,32,31,33,39,38,36,7e,33,31,62,66,33,38,35,36,61,64,33,36,34,65,33,35,\
  7e,61,6d,64,36,34,7e,7e,31,30,2e,30,2e,31,2e,31,2e,33,32,31,33,39,38,36,2d,\
  37,30,34,34,5f,6e,65,75,74,72,61,6c



EndRegedit:
*****************


========= reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS =========

The operation completed successfully.


========= End of CMD: =========

HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_0a7887f4a7c67d9afd51862b2111003c_31bf3856ad364e35_10.0.14393.479_none_689d14721155886c => removed successfully
HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\0a7887f4a7c..62b2111003c_31bf3856ad364e35_10.0.14393.479_689d14721155886c => removed successfully
Registry ====> The operation completed successfully.


==== End of Fixlog 20:11:37 ====

Sysnative Windows Update · Aug 25, 2020

Please retry updates again and attach CBS.log if any fail.

adamb · Aug 25, 2020

Please find attached CBS.log - failed to install update...

Sysnative Windows Update · Aug 26, 2020

Thanks.

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a file should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

adamb · Aug 26, 2020

Hi,

Succesfully ran SFCFix - see log below:

Code:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-08-26 23:07:20.040
Microsoft Windows Server 10 Build 14393 - amd64
Using .zip script file at C:\Users\Administrator.TJL\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\WinSxS

Successfully created directory tree \\?\C:\Windows\WinSxS\amd64_microsoft-windows-security-lsatrustlet_31bf3856ad364e35_10.0.14393.0_none_120dd578956c5017.

Successfully copied file C:\Users\Administrator.TJL\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-security-lsatrustlet_31bf3856ad364e35_10.0.14393.0_none_120dd578956c5017\iumcrypt.dll to C:\Windows\WinSxS\amd64_microsoft-windows-security-lsatrustlet_31bf3856ad364e35_10.0.14393.0_none_120dd578956c5017\iumcrypt.dll.
Successfully copied file C:\Users\Administrator.TJL\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-security-lsatrustlet_31bf3856ad364e35_10.0.14393.0_none_120dd578956c5017\LsaIso.exe to C:\Windows\WinSxS\amd64_microsoft-windows-security-lsatrustlet_31bf3856ad364e35_10.0.14393.0_none_120dd578956c5017\LsaIso.exe.

Successfully restored ownership for C:\Windows\WinSxS
Successfully restored permissions on C:\Windows\WinSxS
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2020-08-26 23:11:26.976
Script hash: 0UqNJXr0qA2dzHALw2QPGlvHrtZFNX069N8Hj4JxWe8=
----------------------EOF-----------------------

Sysnative Windows Update · Aug 26, 2020

Please retry updates again and attach CBS.log if any fail.

adamb · Aug 26, 2020

Hi,

Updates retried, failed to install - CBS log attached!

Thanks,

Sysnative Windows Update · Aug 26, 2020

Hi!

Still the same issue, let's check:

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.

adamb · Aug 27, 2020

Hi,

Not sure if this will work as expected, as the "Install" works - its once it gets to the "Restart Now" button appears - when I click this it restarts and looks like its updating.

Restarts once I go into Update History it tells me failed to Install?

Thanks,

adamb · Aug 31, 2020

Hi Softwaremaniac,

As the update appears to install, its when it the server begins restarting it fails - do you still want me to run this? As I think the program will shut as soon as I click Restart Now

Thanks,

softwaremaniac said:
Hi!

Still the same issue, let's check:

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.

Sysnative Windows Update · Aug 31, 2020

No, I would prefer the following:

CBS.log and C:\Windows\Inf\setupapi.dev.log.

adamb · Sep 1, 2020

Hi softwaremaniac,

See attached CBS.log and setupapi.dev.log

Thanks,

Sysnative Windows Update · Sep 3, 2020

Hi!

Do you have access to a different Server 2016 maybe?

adamb · Sep 4, 2020

Hi

Yes - I have access to at least 10 other 2016 servers

adamb · Sep 9, 2020

Sorry to be a pain - what else do you suggest?

Server 2016 - Update Errors

Member

Attachments

Inactive

Inactive

Attachments

Member

Inactive

Member

Attachments

Inactive

Attachments

Member

Inactive

Member

Attachments

Inactive

Member

Member

Inactive

Member

Attachments

Inactive

Member

Member