[SOLVED] Windows Server 2019 Update Problem - 0x800703f1 - Something with the Drivers Hive

[tbj]

Hello everybody,

After a huge amount of time investigating this problem now I'm here with maximum desperation.

The main problem is: After downloading and installing updates the w2k19 server stops applying updates at 7% on next reboot and then just shows me the "we couldn't complete the updates - Undoing changes" screen.

What have I done so far:

• checked the eventlog for Update errors and encountered 0x800703F1 error
• checked the CBS Log for 0x800703F1 error and got the following:

  • 2022-03-16 12:01:30, Info                  CBS    Perf: Doqe: Staging started.
    2022-03-16 12:01:30, Info                  CBS    Doqe: [Forward] Staging driver updates, Count 81
    2022-03-16 12:01:30, Info                  CBS    Shtd: Changing shutdown timeout to a sliding window timeout: 900000
    2022-03-16 12:01:30, Info                  CBS    Progress: UI message updated. Operation type: Update. Stage: 0 out of 0. Percent progress: 0.
    2022-03-16 12:01:30, Info                  CBS            STAGE index: 63, phase: 1, result 1009, inf: oposdrv.inf
    2022-03-16 12:01:30, Info                  CBS    Doqe: Recording result: 0x800703f1, for Inf: oposdrv.inf
    2022-03-16 12:01:30, Info                  CBS    DriverUpdateStageUpdates failed [HRESULT = 0x800703f1 - ERROR_BADDB]
    2022-03-16 12:01:30, Error                 CBS    Doqe: Failed staging driver updates [HRESULT = 0x800703f1 - ERROR_BADDB]
    2022-03-16 12:01:30, Info                  CBS    Perf: Doqe: Staging ended.
    2022-03-16 12:01:30, Error                 CBS    Failed staging drivers, rebooting and trying again [HRESULT = 0x800703f1 - ERROR_BADDB]
    2022-03-16 12:01:30, Info                  CBS    Shtd: progress thread terminating. [HRESULT = 0x00000000 - S_OK]
    2022-03-16 12:01:30, Info                  CBS    Shtd: progress thread terminated normally
    2022-03-16 12:01:30, Info                  CBS    Doqe: Unlocking driver updates, Count 159
    2022-03-16 12:01:30, Info                  CBS    Winlogon: Simplifying Winlogon CreateSession notifications
    2022-03-16 12:01:30, Info                  CBS    Shtd: Shutdown processing complete.
    2022-03-16 12:01:30, Info                  CBS    Flush: registry...
    2022-03-16 12:01:30, Info                  CBS    Flush: registry took: 4 ms.
    2022-03-16 12:01:30, Info                  CBS    Flush: system volume...
    2022-03-16 12:01:32, Info                  CBS    Flush: system volume took: 1277 ms.
    2022-03-16 12:01:32, Info                  CBS    Failed to call Shutdown Processing on Worker process. [HRESULT = 0x800703f1]
    2022-03-16 12:01:32, Info                  CBS    Failed to execute shutdown processing. [HRESULT = 0x800703f1]
    2022-03-16 12:01:32, Info                  CBS    Ending the TrustedInstaller main loop.
    2022-03-16 12:01:32, Info                  CBS    Starting TrustedInstaller finalization.
    2022-03-16 12:01:32, Info                  CBS    Winlogon: Stopping notify server
    2022-03-16 12:01:32, Info                  CBS    Winlogon: Unloading SysNotify DLL
    2022-03-16 12:01:32, Info                  CBS    Ending TrustedInstaller finalization.

• after that I run sfc /scannow
• after that I run dism /Online /Cleanup-image /Restorehealth
• after that I replaced DRIVERS File from a healthy server but ran into other PATH_NOT_FOUND errrors, so I re-replaced the DRIVERS file with original one
• after that I tried to run SFCFix.exe but with no errrors and nothing fixed

That's it for now.

I attached the CBS Log and the DRIVERS File.

Hope, someone can help me.
Thank you & best regards,
Toni

 

[tbj]

Recently after creating the thread I wanted to upload the files and realized that the drivers files size changed to 8 kb?!
Maybe it happened because after replacing the DRIVERS file I rerrun the dism command again.

And then, to collect the CBS.log i Run the update process a very last time.
The unimaginable happened... The updates completed.

But I'm not sure what I have done to fix this issue?!

I must have to do with the replacement of the drivers file, a reboot and the rerun of the sfc /scannow, dism command and the SFCFix.exe and one final reboot.
I lost the for VXNET3 adapters but after rerunnning vmware tools installation everything is fine now.

Maybe this helps someone who runs into the same issues.

Sorry for consuming your webspace with creating an account for a problem that solves itself...

Best regards,
Toni

 

[x BlueRobot]

But I'm not sure what I have done to fix this issue?!

Looking at the CBS excerpt you provided and what you mentioned about the size of your DRIVERS hive, it would certainly seem that your DRIVERS hive was corrupt. I'm glad you managed to resolve the issue.