Server 2019 - Unable to Install Update (#KB5028168)

Hi Maxstar,

here is my next log,

No win yet but it feels like its going further

Thanks Again,
TS
 

Attachments

  • CBS (8).zip
    5.9 MB · Views: 1
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 reboot the server and attempt to update. If it fails attach a new copy of the CBS logs.
 

Attachments

  • SFCFix.zip
    6.4 MB · Views: 3
Good Morning Maxstar!

Please see the next update attached (unsuccessful), and thanks again for your help sir :)

Kind Regards,
TS
 

Attachments

  • CollectLogs_01.zip
    22.7 MB · Views: 1
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 reboot the server and attempt to update. If it fails attach a new copy of the CBS logs.
 

Attachments

  • SFCFix.zip
    16.9 MB · Views: 4
Good Afternoon Maxstar,

Please find attached next set of logs post the last fix, Thanks again for your perseverance and assistance! I really appreciate you.

Kind Regards,
TS
 

Attachments

  • CollectLogs_02.zip
    20.7 MB · Views: 1
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 reboot the server and attempt to update. If it fails attach a new copy of the CBS logs.
 

Attachments

  • SFCFix.zip
    7.5 MB · Views: 3
Thanks again for your help Maxsar :)

Please find attached our next set of logs.

Kind Regards,
TS
 

Attachments

  • CollectLogs_03.zip
    24.3 MB · Views: 2
Rich (BB code):
  (1134)  PrestageComponent: flags: 0 app: (null) comp: Microsoft-OneCore-Secu
2024-04-29 08:16:34, Info                  CSI    reBootEncodeUEFI-Task, version 10.0.17763.5202, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
2024-04-29 08:16:34, Error                 CSI    00001784@2024/4/28:22:16:34.979 (F) Attempting to mark store corrupt with category [l:15 ml:16]'CorruptManifest'[gle=0x80004005]
2024-04-29 08:16:34, Error                 CSI    00001785@2024/4/28:22:16:34.979 (F) onecore\base\wcp\componentstore\csd_core.cpp(553): Error STATUS_SXS_COMPONENT_STORE_CORRUPT originated in function CCSDirect::GetComponentManifest expression: (null)
[gle=0x80004005]

Hi,

Now we have a different error and a weird glitch in the CBS log. But 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

  • SFCFix.zip
    99.1 KB · Views: 1
Last edited:
Sorry for the super late reply, been pretty off the grid sick :( thanks for your help! Still broken but attached are all fresh logs.
 

Attachments

  • CollectLogs_04.zip
    29 MB · Views: 1
Hi,

No problem, but hope you are feeling better now. Please run the following command in an elevated prompt and copy and paste the result in your next post.

Code:
certutil -hashfile "%systemroot%\winsxs\manifests\amd64_hyperv-computelib-core_31bf3856ad364e35_10.0.17763.5576_none_f657af55d8382ce0.manifest" SHA256
 
Feeling so much better now! Thankyou :)


Code:
C:\Windows\system32>certutil -hashfile "%systemroot%\winsxs\manifests\amd64_hyperv-computelib-core_31bf3856ad364e35_10.0.17763.5576_none_f657af55d8382ce0.manifest" SHA256
CertUtil: -hashfile command FAILED: 0x80070002 (WIN32: 2 ERROR_FILE_NOT_FOUND)
CertUtil: The system cannot find the file specified.
 
Here's the next fix.

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

  • SFCFix.zip
    18.5 KB · Views: 2
Thanks Maxstar :)

Heres the next set of logs, dism did work and the update seemed to progress further, but alas it said 100% then failed :(
 

Attachments

  • CollectLogs_05.zip
    29 MB · Views: 1
Please attempt to update again with Process Monitor running.

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.
 
Hmm, please do the following first. And how many memory is assigned to this server, and how many free disk space is available?

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. If it fails attach a new copy of the CBS logs.
 

Attachments

  • SFCFix.zip
    547.6 KB · Views: 1
Back
Top