[SOLVED] Windows update errors on 3 systems, 2 fixed by ComponentsScanner.exe

[benum47]

Good day all, I just joined Sysnative forum as viewing the historical postings on here has been very helpful.

I have several servers that have applied the July Microsoft update via WSUS and 3 of them errored out and now get 0x800703f1.

I ran ComponentsScanner.exe from here and it repaired 2 of them (so thanks!)

On the 3rd one however the ComponentsScanner.exe came back clean but I still get 0x800703f1 on update

I'm wondering if it could be the DRIVERS rather than COMPONENTS that could be the issue on this third server? In the Windows update log I see ERRORS after "SR.Device Driver Retrieval Client ID 7"

SRV1 - Server 2019 Standard fixed by ComponentsScanner
SRV2 - Server 2019 Standard fixed by ComponentsScanner
SRV3 - Server 2019 DataCenter not fixed yet (ComponentsScanner came back clean)

 

[Maxstar]

Hi and welcome to Sysnative,

Please upload the following file from SRV3.

Upload the SCHEMA.DAT file

• Navigate to C:\Windows\System32\SMI\Store\Machine and copy the SCHEMA.DAT file to your desktop.
• Right-click on this file on your desktop and select Send To > Compressed (zipped) folder. This will create a file named SCHEMA.ZIP on your desktop.
• Attach this ZIP-file to your next reply.

 

[benum47]

Thanks for getting back! Please find requested file attached.

 

[Maxstar]

Hi,

This file looks good, are you sure this file is from the same server as the SRV3_CBS.zip file..?

 

[benum47]

Yes, its Windows 2019 Datacenter.
I jumped back on the server and copied to CBS to the SCHEMA.ZIP just to make sure I didn't mix any files up

 

[Maxstar]

2024-08-07 14:48:50, Error                 CBS    Doqe: Failed staging driver updates [HRESULT = 0x800703f1 - ERROR_BADDB]

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.

 

[benum47]

File attached

 

[Maxstar]

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 logs as well as 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.

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

 

[benum47]

After replacing DRIVERS and rebooting update failed again. The files requested are attached.

Thanks

 

[Maxstar]

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.

• 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 a new copy of the CBS logs and the Setupapi.dev.log file.

 

[benum47]

Update successful! Thanks, any theories on what caused the issue and could you summarize the fix?

I will be donating to help support the site, you do great work for the community.

 

[Maxstar]

You're welcome. Glad to hear this issue has been resolved, in this case the DRIVERS was corrupted and in many cases it has to due with power cycle failures, forced shutdowns, system crashes, lack of space on the system drive etc...

And thanks for your donation to Sysnative...