Forum Discussion
Windows Update error on Windows server 2019.
I have 4 Windows Server 2019 version 1809 with errors 0x8e5e03fa, 0xca00a000, 0x80073712 and other Server that did rollback of Updates.
All the Servers are Domain Controllers.
The updates are the following:
KB4602298, KB5001342, KB5001384, KB4535680, KB4570505 and KB4601887.
The SFC /Scannow is OK - Windows Resource Protection did not find any integrity violations
I tried boot with the ISO of Windows 2019, troubleshooting and after cmd. when I execute the DISM command fail with the error 1 - Incorrect Function.
Dism /Online /Cleanup-Image /RestoreHealth /source:wim:E:\sources\install.wim:2 /limitaccess
Some others commands are the following:
1) Open administrative command prompt and copy and paste:
2) dism /online /cleanup-image /startComponentCleanup
3) dism /online /cleanup-image /analyzeComponentStore
4) dism /Online /cleanup-image /checkhealth
5) dism /online /cleanup-image /scanhealth
6) dism /online /cleanup-image /restorehealth
7) sfc scannow
đ chkdsk /scan
dism.exe /online /cleanup-image /revertpendingactions
Dism /Online /Cleanup-Image /RestoreHealth /source:wim:D:\sources\install.wim:2 /limitaccess
Repair-WindowsImage -Online -RestoreHealth -Source "D:\sources\install.wim:2" -LimitAcces
Well I wait your comments and help.
Best Regards.
Roque.
8 Replies
- dism /online /get-packages /format:table > patches.txt
DISM.exe /Online /Remove-Package /PackageName:Package_for_KB2870699~31bf3856ad364e35~amd64~~6.2.1.1 /quiet /norestartThe versions of Windows and the updates are the following:
Windows 2019 1809 (Build 17763 1339)
Security Update for Windows Server 2019 for x64-based Systems (KB4535680) - Error 0x80073712
2021-04 Servicing Stack Update for Windows Server 2019 for x64-based Systems (KB5001404) -
Error 0x80073712
Windows 2019 1809 (Build 17763 1282)
2021-04 Cumulative Update for Windows Server 2019 (1809) for x64-based Systems (KB5001342)
Install and after roll up
Windows 2019 1809 (Build 17763 1339)
2020-08 Cumulative Update for .NET Framework 3.5, 4.7.2 and 4.8 for Windows Server 2019 for x64 (KB4570505) - Error 0x80073712
2021-02 Cumulative Update for .NET Framework 3.5, 4.7.2 and 4.8 for Windows Server 2019 for x64 (KB4601887) - Error 0x80073701
2021-04 Cumulative Update for Windows Server 2019 for x64-based Systems (KB5001342) - Error 0x80073712
Security Update for Windows Server 2019 for x64-based Systems (KB4535680) - Error 0x80073712
Windows 2019 1809 (Build 17763 1518)
2021-04 Cumulative Update for Windows Server 2019 (1809) for x64-based Systems (KB5001342) - Error 0x8e5e03fa
Did you receive this error on the output of the get package? If yes, check the same warning on the Windows event viewer / Setup log and suggest you remove/rebuild the package.
Looks like your build version is July 14, 2020âKB4558998 (OS Build 17763.1339)
https://support.microsoft.com/en-us/topic/july-14-2020-kb4558998-os-build-17763-1339-ef8a3135-027e-f5ad-a79e-a41581ca842a
Try to use latest security update with n-1 logic.
In my Lab infra i have OS Build 17763.1518 , which include .Net 4.7 latest features.
October 13, 2020âKB4577668 (OS Build 17763.1518)
https://support.microsoft.com/en-us/topic/october-13-2020-kb4577668-os-build-17763-1518-a035446b-2b3f-692f-3c27-afb43ec01594
Please check the possibilities. Thanks
A much simpler solution may be to stand up a new one for replacement.
I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting any operations. Then stand up the new 2019, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to again verify health, when all is good you can decommission / demote old one.
I have a lot of Windows 2019 Domain Controllers and I try to repair the Windows without reinstall a new Server. Exist some possibility , some tool that I can run to fix the components error.
I wait your comments.
None beyond what you already mentioned. May need to rebuild the problematic ones one-at-a-time. You can also start a case here with product support.
Support for business (microsoft.com)
