[SOLVED] Server 2019 Version 1809 Build 17763.2114 Windows Update errors

Hi,

Step 1.
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.
650c22f99662d-6190d993a26f3-SFCFix-Zip-Eng.gif

  • 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.


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code: 
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Hi,

Some update files are missing or have problems. We'll try to download the update again later. Error code: (0x80073712)

DISM is OK SFC is OK, just the update dont work.

Logfile.rar

Loggile from Procmon, last 5 min than the error code (0x80073712) appears.

Tomas
 
Please post a new copy of the COMPONENTS hive.

Upload your COMPONENTS hive.
  • Navigate to C:\Windows\System32\Config and locate the COMPONENTS 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 COMPONENTS.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.
 
Rich (BB code): 
4/14/2024 3:04:18 PM	TiWorker.exe	RegQueryValue	HKLM\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.5695 (WinBuild.160101.0800)\ComponentFamilies\x86_microsoft-windows-d..files-x86-minkernel_31bf3856ad364e35_none_b523c4bcefcac60c\v!10.0.17763.5696\MCP_a79dc719	NAME NOT FOUND	Length: 0
4/14/2024 3:04:18 PM	TiWorker.exe	RegCloseKey	HKLM\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.5695 (WinBuild.160101.0800)\ComponentFamilies\x86_microsoft-windows-d..files-x86-minkernel_31bf3856ad364e35_none_b523c4bcefcac60c\v!10.0.17763.5696	SUCCESS	
4/14/2024 3:04:18 PM	TiWorker.exe	CreateFile	C:\Windows\WinSxS\Manifests\x86_microsoft-windows-d..files-x86-minkernel_31bf3856ad364e35_10.0.17763.5696_none_f522c8577906c8c3.manifest	NAME NOT FOUND	Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Open For Backup, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a, Impersonating: NT AUTHORITY\SYSTEM

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.
650c22f99662d-6190d993a26f3-SFCFix-Zip-Eng.gif

  • 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 reboot the machine and attempt to update again. If ti fails attach a new copy of the CBS logs.
 

Attachments

Hi there,

Hi, so the server update took about 12 hours. It was successfully deployed on this test server, since it does not work empirically and it cannot be trained even on the test server, your support will be needed, I would like to start the deployment on the production servers this Wednesday, if it is OK for you, I will be happy if you help me this time for production server.

Thank you

Tomas
 
Hi there again,
production server scanned.

ComponentsScanner Version 1.5.1.0 by sysnative.com
Windows Version: Windows Server 2019 Datacenter x64 (10.0.17763.2114)
Start time: 2024-04-17T21:05:23
Hive scanned: %windir%\System32\config\COMPONENTS
Number of keys: 309253
Number of values: 1015495

==== Critical Errors ====
None

==== Corrupt Key Names ====
None

==== Corrupt Value Names ====
None

==== Corrupt Value Data Type ====
None

==== Corrupt Value Data ====
None

==== Repair Log ====
No possible repairs

==== Warnings ====
None


Storing 0KB in C:\Users\administrator\AppData\Local\Sysnative\ComponentsScanner

Finish Time: 2024-04-17T21:18:09. Corruption scan time: 747.525926s
===========================EOF===========================
 

Attachments

Hi,

Step 1. Download
6530fbb0f4101-56f31e53c97da-SFCFix.PNG
SFCFix and save it to your desktop.

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.
650c22f99662d-6190d993a26f3-SFCFix-Zip-Eng.gif

  • 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.


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code: 
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Hi MaxStar,

I start it after 18:00 as it is a production server and I can't interfere with the live operation due to its busyness. When I have it today after 18:00 I will write to you.

Thank you

Tomas
 
Okay, and when DISM completed without any errors I would try to update again.
 
CBS.log

Some updates didn't finish downloading. We'll keep trying. Error code: (0x80246007)

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

Attachments

new log
2024-04 Cumulative Update for Windows Server 2019 (1809) for x64-based Systems (KB5036896) - Error 0x800f0986
 
Hi,

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.
650c22f99662d-6190d993a26f3-SFCFix-Zip-Eng.gif

  • 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.
 

Attachments

Hello Maxstar, thank you very much for your help the server update took 18 hours more than test server.
You’ve been very helpful, and as a token of my appreciation, I’m sending another donation for your professional work.

Thank you
 
Hi,

You're welcome. Glad to hear I could help and thanks for your donations to Sysnative. (y)

I suppose it took a very long time because a clean-up task was set after the last fix and attempt to update again.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top