[SOLVED] Windows Update Error Code 0x80073712 on Windows Server 2012R2

S

stroti

Active member
Joined
Jul 21, 2021
Posts
29
Hi,

I am getting a windows update error 0x80073712 on a server 2012R2.

Step #2 - Run SFC Scan
Windows Resource Protection did not find any integrity violations

Step #3 – DISM Scan
Repaired successfully.

Step #4 - Run SFCFix
No curruptions found. Output file is empty.

Step #5 – Export/Upload CBS folder
cbs.zip attached

I am really stuck atm. Any help is really appreciated.

Sebastian


---------

In the CBS.log I found errors and Warning:

2021-11-14 12:40:33, Error CSI 00000019@2021/11/14:11:40:33.357 (F) base\wcp\componentstore\storelayout.cpp(2863): Error STATUS_SXS_COMPONENT_STORE_CORRUPT originated in function ComponentStore::CRawStoreLayout::QueryTlcDataIdentity expression: (null)
[gle=0x80004005]
2021-11-14 12:40:33, Info CBS Added C:\Windows\Logs\CBS\CBS.log to WER report.
2021-11-14 12:40:33, Info CBS Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2021-11-14 12:40:33, Info CBS Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2021-11-14 12:40:33, Info CBS Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2021-11-14 12:40:33, Error CSI 0000001a (F) HRESULT_FROM_WIN32(14098) #115593# from Windows::ServicingAPI::CCSITransactionAnalysis_ICSIInventory::EnumComponentsDeployments(flags = (ICSIINVENTORY_ENUMCOMPONENTSDEPLOYMENTS_FLAG_INCLUDE_PINNED|ICSIINVENTORY_ENUMCOMPONENTSDEPLOYMENTS_FLAG_INCLUDE_INSTALLED|ICSIINVENTORY_ENUMCOMPONENTSDEPLOYMENTS_FLAG_ASSEMBLY_NOT_FOUND_RETURNS_NULL), cComponents = 1)
[gle=0x80073712]

On the DISM.log I found this:
(w) CBS Package Index Package Missing 0x80070490 Package_648_for_KB4561666~31bf3856ad364e35~amd64~~0.0.0.0 Package_648_for_KB4561666~31bf3856ad364e35~amd64~~6.3.1.10
(w) CBS Watchlist Package Missing 0x80070490 Microsoft-Windows-Client-Drivers-Package-printscan~31bf3856ad364e35~amd64~~0.0.0.0 Package_648_for_KB4561666~31bf3856ad364e35~amd64~~6.3.1.10
(w) CBS Watchlist Package Missing 0x80070490 Microsoft-Windows-Client-Features-Package-AutoMerged-admin~31bf3856ad364e35~amd64~~0.0.0.0 Package_664_for_KB4561666~31bf3856ad364e35~amd64~~6.3.1.10
(w) CBS Watchlist Package Missing 0x80070490 Microsoft-Windows-Client-Features-Package-AutoMerged-net~31bf3856ad364e35~amd64~~0.0.0.0 Package_1038_for_KB4512488~31bf3856ad364e35~amd64~~6.3.1.5
(w) CBS Watchlist Package Missing 0x80070490 Microsoft-Windows-CoreSystem-EventLog-Admin-Package~31bf3856ad364e35~amd64~~0.0.0.0 Package_664_for_KB4561666~31bf3856ad364e35~amd64~~6.3.1.10
(w) CBS Watchlist Package Missing 0x80070490 Microsoft-Windows-Server-Features-Package-AutoMerged-admin~31bf3856ad364e35~amd64~~0.0.0.0 Package_664_for_KB4561666~31bf3856ad364e35~amd64~~6.3.1.10
(w) CBS Watchlist Package Missing 0x80070490 Microsoft-Windows-ServerCore-SKU-Foundation-Package-admin~31bf3856ad364e35~amd64~~0.0.0.0 Package_664_for_KB4561666~31bf3856ad364e35~amd64~~6.3.1.10
(w) CBS Watchlist Package Missing 0x80070490 Microsoft-Windows-WIA-Server-Drivers-Package~31bf3856ad364e35~amd64~~0.0.0.0 Package_648_for_KB4561666~31bf3856ad364e35~amd64~~6.3.1.10
(w) CBS Watchlist Package Missing 0x80070490 Microsoft-Windows-WirelessNetworking-Package~31bf3856ad364e35~amd64~~0.0.0.0 Package_1038_for_KB4512488~31bf3856ad364e35~amd64~~6.3.1.5
(w) CBS Watchlist Component Missing 0x80070490 amd64_microsoft-windows-eventlog-api_31bf3856ad364e35_0.0.0.0_none_2c29934d65d1dfd3 Package_664_for_KB4561666~31bf3856ad364e35~amd64~~6.3.1.10
(w) CBS Watchlist Component Missing 0x80070490 amd64_microsoft-windows-eventlog_31bf3856ad364e35_0.0.0.0_none_5cbced4b1360dcf0 Package_664_for_KB4561666~31bf3856ad364e35~amd64~~6.3.1.10
(w) CBS Watchlist Component Missing 0x80070490 amd64_microsoft-windows-native-80211_31bf3856ad364e35_0.0.0.0_none_cf013a418f7a33ac Package_1038_for_KB4512488~31bf3856ad364e35~amd64~~6.3.1.5
(w) CBS Watchlist Component Missing 0x80070490 amd64_microsoft-windows-vwifi_31bf3856ad364e35_0.0.0.0_none_df8d3f53c40caca5 Package_1038_for_KB4512488~31bf3856ad364e35~amd64~~6.3.1.5
(w) CBS Watchlist Component Missing 0x80070490 amd64_microsoft-windows-wcn-config-registrar_31bf3856ad364e35_0.0.0.0_none_ad154501c2717411 Package_1038_for_KB4512488~31bf3856ad364e35~amd64~~6.3.1.5
(w) CBS Watchlist Component Missing 0x80070490 amd64_microsoft-windows-wlansvc_31bf3856ad364e35_0.0.0.0_none_1c3cd384056dcea4 Package_1038_for_KB4512488~31bf3856ad364e35~amd64~~6.3.1.5
(w) CBS Watchlist Component Missing 0x80070490 amd64_sti.inf_31bf3856ad364e35_0.0.0.0_none_d9d76299e14e4e3f Package_648_for_KB4561666~31bf3856ad364e35~amd64~~6.3.1.10

Summary:
Operation: Detect and Repair
Operation result: 0x0
Last Successful Step: Entire operation completes.
Total Detected Corruption: 16
CBS Manifest Corruption: 0
CBS Metadata Corruption: 16
CSI Manifest Corruption: 0
CSI Metadata Corruption: 0
CSI Payload Corruption: 0
Total Repaired Corruption: 0
CBS Manifest Repaired: 0
CSI Manifest Repaired: 0
CSI Payload Repaired: 0
CSI Store Metadata refreshed: True
 

Attachments

Hello stroti,

It would be helpful to see your Registry Hives in order to work out what needs fixing.

Step#1 - Export CBS hive
  • Click on the Start button and type regedit
  • When you see regedit on the list, right-click on it and select Run as administrator.
  • When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing
  • Once selected, click File > Export....
  • Change the Save as type: to Registry Hive Files (.).
  • Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
  • Right-click on the saved file and choose Send To -> Compressed (zipped) Folder.
  • Attach the .ZIP file to your next post.
  • If the file is too large to upload here, upload to Dropbox or OneDrive or SendSpace and just provide the link here.

Step#2 - Export SideBySide
  1. Click on the Start button and type regedit
  2. When you see regedit on the list, right-click on it and select Run as administrator
  3. When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide
  4. Once selected, click File > Export....
  5. Change the Save as type: to Registry Hive Files (.)
  6. Name this file SxS (with no file extension) and save it to your Desktop.
  7. Once done please upload this file via Dropbox or OneDrive or SendSpace.

Step#3 - Export Components Hive
  1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
  2. 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.
  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. The file will likely be too large to upload here so please upload to a file sharing service. Examples of services to upload to are Dropbox or OneDrive or SendSpace and then just provide the link in your reply.

Many thanks!
 
Hi stroti,

I have found that a deployment key is missing its entries in your registry. Please apply the following fix.

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.

  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  8. Attatch this file into your next post for me to check please.

    Once this is done, please try the DISM scan again and post the new CBS.log
 

Attachments

Another deployment key is missing entries.

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.

  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  8. Attatch this file into your next post for me to check please.

    Once this is done, please try the DISM scan again and post the new CBS.log
 

Attachments

Hi Stroti, I think you attached the wrong files they are the same as the previous ones.
 
Let me know if windows update is still throwing errors. You could also try SFC /scannow
 
It's working fine! The server installed all missing updates. Thank you very much!
 
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