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

Great please attempt to update, if it fails provide the latest CBS logs then I can provide the next fix...
 
Rich (BB code): 
2024-04-12 16:52:52, Info                  CSI    0000181d Hashes for file member [l:12]'mrxsmb10.sys' do not match.
 Expected: {l:32 ml:4096 b:c48db46f6a96de34b353227d8f4c61ab60da3567b552e0dcd40fa774382a4f68}.
 Actual: {l:32 b:4ecf00d69422dd460a9737ef05cac55c020048b5cdcc15c5f4753076db6ef065}.

Here's the next fix:

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,

i think like the last time the process is frozen.

C:\windows\system32>DISM /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.1697

Image Version: 10.0.17763.2114
 
Hi,

Are you sure it is frozen and not the output is blocked because the edit mark is set into the console?
 
Yes its frozen, it was running like 12 hours and to change was made .... I restarted the server did the patch again with the same result. Its pretty funny that for the same VM is the repair not the same. hmm
 
It seems the previous fix completed sucessfully, that corruption is not reported again. So here's the next fix.

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

C:\windows\system32>DISM /online /cleanup-image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.1697

Image Version: 10.0.17763.2114

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

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

Attachments

Rich (BB code): 
2024-04-13 13:03:41, Error                 CSI    00002eec@2024/4/13:11:03:41.151 (F) Attempting to mark store corrupt with category [l:15 ml:16]'CorruptManifest'[gle=0x80004005]
Please run the File Checker, if it fails attach a new copy CBS logs.
Code: 
SFC /Scannow
 
And the next fix.

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 System File Checker again and post the result. If it fails attach a new copy of the CBS log.
Code: 
SFC /Scannow
 

Attachments

C:\windows\system32>SFC /Scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.
 
Rich (BB code): 
2024-04-13 14:35:15, Error                 CSI    00001777@2024/4/13:12:35:15.914 (F) Attempting to mark store corrupt with category [l:15 ml:16]'CorruptManifest'[gle=0x80004005]
2024-04-13 14:35:15, Error                 CSI    00001778@2024/4/13:12:35:15.914 (F) onecore\base\wcp\componentstore\csd_core.cpp(553): Error STATUS_SXS_COMPONENT_STORE_CORRUPT originated in function CCSDirect::GetComponentManifest expression: (null)
[gle=0x80004005]

Still the same issue, please attempt to update with Process Monitor running. This because the CBS log does not reveal the issue...

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the square (CTRL +E) on the toolbar as shown below.



4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up the LogFile.PML and upload it to WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free and provide the link.
6. Attach also a new copy of the CBS logs for the time stamps.
 
C:\windows\system32>DISM /online /cleanup-image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.1697

Image Version: 10.0.17763.2114

[===========================84.6%================= ]
Error: 0x800f081f
 

Attachments

You must log in or register to reply here.
Back
Top