[SOLVED] Need help with a Windows update failure on Server 2016

U

undoubted

Contributor
Joined
Nov 25, 2023
Posts
14
Hi there!
The updates on my server 2016 Standard virtual machine stopped working. The error being generated by the Windows update is as follows: "Error 0x80073712 Some update files are missing or have problems. We'll try to download the update again later." I attempted several diferent repairs such as scannow and many variations of DISM, including pulling files off a server 2016 .iso. All efforts have failed thus far. Hoping go get some assistance from this community. Many thanks in advance!
 

Attachments

Hi,

Step 1. Download
6530fbb0f4101-56f31e53c97da-SFCFix.PNG
SFCFix and save it to your desktop.

Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
650c22f99662d-6190d993a26f3-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code: 
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Hi there and thank you so much for your assistance! I ran the sfcfix tool as instructed and then DISM. This time it completed 100% successfully. However, Windows update is still reporting the same error when I attempt to install the update. The updated CBS.zip is attached.
 

Attachments

Hi,

Upload your COMPONENTS hive.
  • Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
  • Please copy this file to your desktop.
  • Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
  • 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.
  • If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.
 
Rich (BB code): 
2023-12-07 18:24:41, Error                 CSI    000018f2@2023/12/8:02:24:41.967 (F) onecore\base\wcp\componentstore\versionedindex.cpp(3705): Store corruption detected in function ComponentStore::CRawStoreLayout::CheckFamilyIndexForDeadWinnerComponent expression: (null)
  MissingWinningComponentKey on resource 'amd64_microsoft-windows-w..ient-printuisupport_31bf3856ad364e35_10.0.14393.4651_none_e3207e0549d97461'[gle=0x80004005]

Hi,

Step 1. Download
6530fbb0f4101-56f31e53c97da-SFCFix.PNG
SFCFix and save it to your desktop.

Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFixScript.txt and save it to your desktop.
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
650ef5dbdfd06-62151e1bebac4-SFCFix-Txt-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the following commands in an elevated prompt and copy and paste the result in your next post.
Code: 
dir /s /a %systemroot%\WinSxS\amd64_microsoft-windows-w..ient-printuisupport_31bf3856ad364e35_10.0.14393.4651_none_e3207e0549d97461
certutil -hashfile %systemroot%\WinSxS\Manifests\amd64_microsoft-windows-w..ient-printuisupport_31bf3856ad364e35_10.0.14393.4651_none_e3207e0549d97461.manifest SHA256
 

Attachments

Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\Users\administrator>dir /s /a %systemroot%\WinSxS\amd64_microsoft-windows-w..ient-printuisupport_31bf3856ad364e35_10.0.14393.4651_none_e3207e0549d97461
Volume in drive C has no label.
Volume Serial Number is 5841-AD13

Directory of C:\windows\WinSxS\Temp\InFlight\707fdcddb7aed701010000003c256440

09/20/2021 11:23 PM <DIR> amd64_microsoft-windows-w..ient-printuisupport_31bf3856ad364e35_10.0.14393.4651_none_e3207e0549d97461
0 File(s) 0 bytes

Total Files Listed:
0 File(s) 0 bytes
1 Dir(s) 261,483,724,800 bytes free

C:\Users\administrator>certutil -hashfile %systemroot%\WinSxS\Manifests\amd64_microsoft-windows-w..ient-printuisupport_31bf3856ad364e35_10.0.14393.4651_none_e3207e0549d97461.manifest SHA256
CertUtil: -hashfile command FAILED: 0x80070002 (WIN32: 2 ERROR_FILE_NOT_FOUND)
CertUtil: The system cannot find the file specified.

C:\Users\administrator>
 
Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
650c22f99662d-6190d993a26f3-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code: 
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Both executed successfully. However, the update still fails due to the same error. The updated CBS is attached.
 

Attachments

Hi,

Here's the next fix.

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
650c22f99662d-6190d993a26f3-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code: 
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Your last fix has resolved the issue and I was able to install the previously failing KB. I am grateful for your help!! However, after my Windows queued up the next update, it failed with a new error, as follows:

There were problems installing some updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: Windows Malicious Software Removal Tool x64 - v5.115 (KB890830) - Error 0x80248007

I have attached the updated CBS.zip.
 

Attachments

Hi,

Here's the next fix.

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
650c22f99662d-6190d993a26f3-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code: 
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Already tried that - it just downloads the "Microsoft Windws Maclicious Sfotware removal tool" as an exe and opens a GUI with options to do a scan. I have completed a scan, closed the tool, checked the updates, and still getting the same error. :( Is there a way to check if this is the only update that is/will fail or will all future updates also fail as a result? If this is the only one, I am not too worried about this tool as I can always download and run it manually
 
Hmm, please post a screenshot of the Windows Update window and attach the latest CBS logs. I assume this server is connected to an WSUS server, is that correct?
 
no WSUS, though I do use na RMM tool to manage some updates. However, in this case, I am using native windows updates as there are no restrictions from the policy to do so
 

Attachments

  • CBS.zip
    CBS.zip
    705.6 KB · Views: 2
  • Screenshot 2023-12-12 113247.png
    Screenshot 2023-12-12 113247.png
    45.8 KB · Views: 1
Okay, please hide KB890830 using the following tool of Microsoft. Reboot the server > search for new updates and post the result.

Download
62877701aaac2-WusWowHide24.png
wushowhide.diagcab to hide an update.
  • Double click on the wushowhide.diagcab file and press Next.
  • Now the tool will search for updates and performs a scan to detect problems.
  • When this process is complete click on Hide updates.
  • Now an overview will appear with updates that have not yet been installed.
  • Select the update you want to hide and press Next.
  • When the troubleshooting has complete you can close the tool.
 
When you run Windows Update again KB890830 is still pending (as failed) update?
 
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