[SOLVED] Windows Updates Failing on Server 2016 - ERROR_BADDB

L

LethalMutiny

Member
Joined
Oct 23, 2024
Posts
7
Hello - I have two servers that are exhibiting the same issue. It does not appear to be the components hive that is having an issue but rather the Schema hive. I have pasted a snippet of the CBS.log that I believe is relevant.

Code: 
2024-10-23 09:06:30, Error                 CSI    000000d6@2024/10/23:14:06:30.690 (F) onecore\base\wcp\componentstore\com\store.cpp(5260): Error NTSTATUS_FROM_WIN32(1009) originated in function Windows::COM::CComponentStore::MountSMISchemaHive expression: MountSMISchemaHive
[gle=0x80004005]
2024-10-23 09:06:30, Info                  CBS    Added C:\Windows\Logs\CBS\CBS.log to WER report.
2024-10-23 09:06:30, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20241023135754.log to WER report.
2024-10-23 09:06:30, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20241023133500.log to WER report.
2024-10-23 09:06:30, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20241023131205.log to WER report.
2024-10-23 09:06:30, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20241023124842.log to WER report.
2024-10-23 09:06:30, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20241023122536.log to WER report.
2024-10-23 09:06:30, Info                  CBS    Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2024-10-23 09:06:30, Info                  CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2024-10-23 09:06:30, Info                  CBS    Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2024-10-23 09:06:31, Error                 CSI    000000d7 (F) HRESULT_FROM_WIN32(1009) #2657698# from Windows::COM::CComponentStore::InternalTransact(...)[gle=0x800703f1]
2024-10-23 09:06:31, Error                 CSI    000000d8 (F) HRESULT_FROM_WIN32(1009) #2657696# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_Commit(Flags = 38, pSink = NULL, disp = 0)[gle=0x800703f1]
2024-10-23 09:06:31, Error                 CSI    000000d9 (F) HRESULT_FROM_WIN32(1009) #2657695# 563995 us from Windows::ServicingAPI::CCSITransaction_ICSITransaction::Commit(flags = 0x00000026, pSink = NULL, disp = 0)
[gle=0x800703f1]
2024-10-23 09:06:31, Error                 CBS    Exec: Failed to commit CSI transaction to resolve execution chain. [HRESULT = 0x800703f1 - ERROR_BADDB]

Attached is the CBS.log, Components Scanner results, as well as my schema.dat file from each server (If I need to make a separate thread for each server let me know, but since they are the same issue was hoping to handle them both at the same time). I labeled the files as such, Server1 and Server2.

Thanks!
 

Attachments

Hi @LethalMutiny,

Welcome to Sysnative Forums!

If you haven't already, please review the posting instructions here, and attach the requested log files. Without log files, our helpers will not be able to assist, and this will slow down fixing your machine.

If logs have been already been provided, our team of volunteers will analyse the provided log files to build a fix for your system. Please be aware that this may take several days from your initial post, due to the high volume of threads that we receive.


- Sysnative Windows Update Team
 
Hi and welcome to Sysnative,

Please do the following for Server 1.

Replace the SCHEMA.DAT file
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 the attached SCHEMA-S1.zip file and save it to your desktop, right-click on it and select Extract all.
  • Navigate to C:\Windows\System32\SMI\Store\Machine and rename the SCHEMA.DAT file to SCHEMA.old
  • Copy the SCHEMA.DAT file on your desktop into the above directory.

Afterwards attempt to update again and post the result. If it fails attach a new copy of the CBS logs.
 

Attachments

Hello! It appears that the replaced schema.dat file fixed Server 1, I have successful updates. I am assuming I'll have a totally different fixed file for Server 2?

Thank you so much.
 
Great, please do the following for Server 2.

Replace the SCHEMA.DAT file
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 the attached SCHEMA-S2.zip file and save it to your desktop, right-click on it and select Extract all.
  • Navigate to C:\Windows\System32\SMI\Store\Machine and rename the SCHEMA.DAT file to SCHEMA.old
  • Copy the SCHEMA.DAT file on your desktop into the above directory.

Afterwards attempt to update again and post the result. If it fails attach a new copy of the CBS logs.
 

Attachments

Rich (BB code): 
2024-10-30 11:17:59, Error                 CBS    Doqe: Failed staging driver updates [HRESULT = 0x800703f1 - ERROR_BADDB]

Please provide the DRIVERS hive from this server.

Upload your DRIVERS Hive
  • Navigate to C:\Windows\System32\config and locate the DRIVERS 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 DRIVERS.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.
 
Replace Drivers Hive Manually

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 DRIVERS.ZIP and save to your desktop.
  2. Right-click on it and select Extract all.... Make sure the "Show extracted files when complete" is checked and click Extract.
  3. Now we have the DRIVERS file that we will be using to replace your current one.
  4. Navigate to C:\Windows\System32\config
  5. Right-click on the current DRIVERS file and select rename. Rename it to DRIVERS.bad.
    Note: If you get an error that the file is in use, reboot your computer and then try again.
  6. Take the file from the Drivers folder on your desktop and paste it into C:\Windows\System32\config

Afterwards reboot the server and attempt to update. If it fails attach the latest CBS logs and the following logfile.

Upload the setupapi.dev.log file
  • Open Windows Explorer and browse to the C:\Windows\INF folder.
  • Right-click on the file setupapi.dev.log and choose Send to > Compressed (zipped) folder.
  • Now the message will appear, "Windows cannot create the Compressed (zipped) Folder here. Do you want it to be placed on the desktop instead?"
  • Click on the Yes button here.
657716925b62b-setup-api-dev-folder.png

  • Attach the file setupapi.dev.zip in your next reply.
 

Attachments

Rich (BB code): 
!!!  sto: Failed to determine status of driver update 'C:\Windows\WinSxS\amd64_dual_miradisp.inf_31bf3856ad364e35_10.0.17763.1697_none_2fd9a56a4455ccaf\miradisp.inf'. Error = 0x000003F1
!    sto: Could not unstage all driver updates. Error = 0x000003F1
<<<  Section end 2024/10/30 13:40:26.265
<<<  [Exit status: FAILURE(0x000003f1)]

Have you replaced the DRIVERS hive and rebooted the server before attemting to update again?
 
🤦‍♂️ it helps to paste the file after you've actually copied it. It's been that kind of week. Verified it's the new file now, rebooted, and got a failure. New error code this time though, 0x80070003. CBS and setupapi.dev attached.
 

Attachments

Hi,

Download
67139f7e69a58-SFCFix-ico.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.
67139f52b3c1e-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.

Afterwards attempt to update and post the result. If it fails attach a new copy of the CBS logs and the Setupapi.dev.log.
 

Attachments

You must log in or register to reply here.
Back
Top