Windows Server 2019 v1809 Update Error 0x800703f1

Erhardt24 6 Reputation points
2021-06-21T20:03:20.173+00:00

I have 3 Windows servers running 2019 v1809 that have the same error. Error 0x800703f1. For the same KB4535680. I have already attempted; sfc, dism, chkdsk, in-place upgrade. All fail. Any ideas or suggestions??

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,896 questions
Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
13,655 questions
{count} vote

6 answers

Sort by: Most helpful
  1. Anonymous
    2021-06-21T20:07:44.86+00:00

    You can also try the manual steps here.
    https://learn.microsoft.com/en-us/windows/deployment/update/windows-update-resources#how-do-i-reset-windows-update-components

    but time may be better spent standing up a new one, patch fully, migrate roles over, and move on.

    --please don't forget to upvote and Accept as answer if the reply is helpful--


  2. Anonymous
    2021-06-21T20:10:28.95+00:00

    Sounds good, you're welcome.

    --please don't forget to upvote and Accept as answer if the reply is helpful--


  3. Anonymous
    2021-06-21T20:44:56.853+00:00

    Yea, I did not expect it to be honest. What roles are installed? Debugging the \cbs.log is beyond scope of forums support. Something here might help.
    https://learn.microsoft.com/en-us/troubleshoot/windows-client/deployment/analyze-sfc-program-log-file-entries

    or you can also start a case here with product support.
    https://support.serviceshub.microsoft.com/supportforbusiness

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    0 comments No comments

  4. Docs 15,566 Reputation points
    2021-06-21T22:25:49.227+00:00

    This Windows update error 0x800703f1 = The configuration registry database is corrupt.

    Perform the following steps:

    1) Open administrative command prompt (ACP) and type or copy and paste:
    2) sfc /scannow
    3) dism /online /cleanup-image /scanhealth
    4) dism /online /cleanup-image /restorehealth
    5) sfc /scannow
    6) chkdsk /scan
    7) findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"
    8) Findstr /c:"[SR]" "C:\Windows\Logs\CBS\CBS.log" > %UserProfile%\Desktop\Cbs.txt

    9) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

    10) Find the new text files on the desktop > zip as needed > post share links

    11) Run setupdiag > post a share link including all files:
    https://learn.microsoft.com/en-us/windows/deployment/upgrade/setupdiag

    .
    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    On the left side of each post: Vote = a helpful post
    .
    .
    .
    .
    .

    0 comments No comments

  5. Percival Yang 731 Reputation points
    2021-06-22T06:22:06.583+00:00

    Hi Erhardt24,

    As you have said that your 3 Servers ran into the same problems, so it’s feasible for us to infer whether they come from the same original equipment manufacturer (OEM) or have executed same operations before.

    Some OEM might not support KB 4535680 referred to the link: you can check whether your Servers’ condition apply to this docx and contact the OEM to verify,
    https://support.microsoft.com/en-us/topic/kb4535680-security-update-for-secure-boot-dbx-january-12-2021-f08c6b00-a850-e595-6147-d0c32ead81e2

    If else, you can extract the CBS logs and compare them with each other to find out differences by usage below

    To view CBS.log, you can go to the path %windir%\Logs\CBS\CBS.log and double-click CBS.log file to open it.

    To view the logs generated by SFC in CBS.log file, you can run cmd as administrator, execute the command findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfclogs.txt. Then, double-click the newly-created file on the Desktop to open it

    Hope above information can help you.

    ============================================
    If the Answer is helpful, please click "Accept Answer" and upvote it.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.