[SOLVED] 2024-03 Cumulative Update for Windows Server 2019 (1809) for x64-based Systems (KB5035849) - Error 0x800703f1

[dmichaelis]

Hello everyone, I sometimes have issues updating our Hypervisor hosts and in this case I have VM that will not update. I found this site and immediately signed up. I cannot believe how nice everyone is and there is no shaming that I have seen.

Anyways, the server is giving me this error.

2024-03 Cumulative Update for Windows Server 2019 (1809) for x64-based Systems (KB5035849) - Error 0x800703f1

I saw that I am supposed to try things in order before I post but I cannot even get past step 1.

Step #1 - Run SFC Scan​

I get "Windows Resource Protection could not perform the requested operation."

Tried to run step two "dism /online /cleanup-image /restorehealth" and i get this error "The configuration registry database is corrupt."

[== 4.5% ]

Error: 1009

I am so confused, but reading more on this site I was reading about a hive being corrupt but dont want to go any farther.

If one of you smart people could help me solve this one I would be forever greatful.

thanks

David

 

[dmichaelis]

I have attached my CBS.zip and componentsscanner.txt.

 

[dmichaelis]

Just adding a little more, than i am going to bed. Its midnight here.

After running the Componentscanner.exe and running the repairs, i was able to get the update to install.

I did pop my error into google "The error message "Sequence mismatch! Primary = 107836. Secondary = 107835" typically occurs in the context of Dell PowerEdge servers and indicates a discrepancy between the primary and secondary BIOS firmware versions."

We have a clustered two host (Dell Power-edge R740) environment. We use the clustered fail over, which i was told lets me fail over VM's from host to host, which we see when rebooting hosts for updates. I noticed that the two hosts (which are identical) have two different Bios. HV08 is on Bios 2.10.0 (2020-11-12) and HV09 is on 2.14.2 (2022-03-21). It looks like the MSP updated one host but didn't update the other... could that be the issue here?

 

[Maxstar]

Hi and welcome to Sysnative,

Error 0x800703f1 has nothing to do with BIOS firmware versions. This error means that an registry HIVE file is corrupted, also indicated as ERROR_BADDB. And as you can see in the ComponentsScanner log, the tool repaired the primary and secondary sequence numbers of the COMPONENTS hive.

==== Repairs Attempted ====
Repair Type: ERROR_BADDB
    * Pre Repair Stage: Nothing to do
    * Repair Stage: Successfully updated primary and secondary sequence numbers to 107837
    * Post Repair Stage: Hive successfully loaded in Regedit without error

 

[dmichaelis]

Can someone tell me how this happens? Is it nice to know how to fix it now :)

 

[Maxstar]

Hi,

The exact reason is quite complex to explain, but technically it means that changes in the registry has not being applied correctly, or when this hive was not correctly unloaded from the registry. This can happen when a system crashed, after a forced restart and/or power failures.

 

[dmichaelis]

Thank you Maxstar. I appreciate the response. I woke up to one of the Hosts being rebooted around 1215 am this morning. This has happened a lot. I think your "system crashed, after a forced restart and/or power failures" is spot on. Does this forum have users that help with Hyper-v clustering issues?

 

[Maxstar]

Does this forum have users that help with Hyper-v clustering issues?

Hi,

This subforum for Windows Update issues is limited to response, so I would suggest to start a new thread in the General Help Section.

Please provide in the new thread information about the used hardware of the server and VM's which are running and their config.