[SOLVED] 2019 Server getting 0x800703f1 or 0x8024001e errors with Windows Updates

BroncoMarc

Well-known member
Joined
Aug 2, 2023
Posts
77
Server has not successfully installed a CU in a while. It looks like it's been giving 0x800703f1 each month when the patches ran. The most recent try gave a 0x8024001e error.

I've tried resetting the SoftwareDistribution folder and CatRoot.
I've tried disabling antivirus.
Tried installing CU update from a downloaded MSU file.
Patches still fail.

SFC didn't show any errors
DISM doesn't show any errors
SFCFix did not show any errors.
Component Scanner said no corruptions found.

Thanks,
- Marc
 

Attachments

Rich (BB code):
2024-07-24 18:01:28, Error                 CBS    Doqe: Failed staging driver updates [HRESULT = 0x800703f1 - ERROR_BADDB]

Hi and welcome to Sysnative,

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.
 
Step 1. 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 a new copy of the CBS log, as well as the following log file.

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

Open an elevated prompt, run the following command and post the result.
Code:
net stop wuauserv
net stop cryptSvc
net stop bits
ren %SystemRoot%\SoftwareDistribution SoftwareDistribution.old 
net start wuauserv
net start cryptSvc
net start bits
 
I reset the software distribution folder, then tried installing the update again. The update says it installed successfully! I'll give it a reboot tonight and see what happens. Thanks!
 
Great, let me know the result tomorrow, fingers crossed 🤞 and let's hope it will not result in an rollback due to an driver issue since the DRIVERS hive was also corrupted...

If it fails attach a new copy of the CBS logs and a new copy of the Seupapi.dev.log
 
Hi,

Here's the next fix.

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.

Afterwards attempt to update again. If it fails attach an new copy of the CBS logs and the Setupapi.dev.log.
 

Attachments

Hi,

And the next fix.

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.

Afterwards attempt to update again. If it fails attach an new copy of the CBS logs and the Setupapi.dev.log.
 

Attachments

Hi,

You're welcome. Glad to hear this server is up-to-date now! (y)
So I will mark this thread as solved.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top