[SOLVED] All CU Windows patches fails on Windows Server 2016

T

TelvisTed

Member
Joined
Jun 7, 2023
Posts
24
Location
DMV
Hi,
Any related CU Windows patches since early last year has been failing. Unfortunately, I'm not sure where to look other than the gui itself showing that it failed.
I have tried to use the directions I saw online to use the Windows repair DISM in which it requires the WinSXS files, but no luck there either.
I wasn't sure if maybe upgrading it to Windows 2019 or 2022, but I was assuming if the OS is corrupted, then how will the OS upgrade succeed? Plus, not sure what it will do to the main application that is running on this server.
Attached are the CBS and Components scanner files are instructed. The CBS.zip file is too large and cannot access GoFile or WeTransfer possibly due to lock down from gov't website. So, I compressed it using 7zip...I think you should still be able to extract it with winzip. Let me know if you can't.
I apologize if I'm missing any other information..but greatly always greatly appreciated from the Sysnative team as I've seen posts of people having the same problem, but perhaps slightly unique case?

Regards,
Teddy Lim
Sys Engineer Windows
 

Attachments

Hi and welcome,

Glad you have created your own thread, we don't provide help by PM's.

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

The DISM /online /cleanup-image /RestoreHealth:
"100% The restore operation completed successfully. The operation completed successfully."
attached SFCFix.txt
 

Attachments

Hi,

Yes, please attempt to update and let me know the result. If it fails attach a new copy of the CBS logs.
 
Hi,
Unfortunately, the update failed. But the DISM (restore operation completed successfully 100%).
However, the same message on the "Update History" showing as 2024-04 Cumulative Update for Windows Server 2016 for x64-based Systems (KB5036899): Failed to install 4/25/2024
I'm wondering if it would help to remove the contents in the SoftwareDistribution folder or rename this as done a few times, but for the sake of having a successfull DISM, should I do that again? Also, perhaps use the offline pkg/manual install instead of the normal way of "Checking for updates".
In any case, attached is the latest CBS log in zip format.
Thank you for your patience.
 

Attachments

Rich (BB code): 
2024-04-25 10:17:31, Info                  CSI    00003080 Regenerating payload files from delta files on component: [l:101 ml:140]'amd64_microsoft-windows-g..rveradmintools-gpme_31bf3856ad364e35_10.0.14393.5582_none_2bce64340b6ac9a6'
2024-04-25 10:17:31, Error                 CSI    00003081@2024/4/25:14:17:31.947 (F) onecore\base\wcp\componentstore\deltastore.cpp(2879): Error STATUS_INVALID_PARAMETER originated in function ComponentStore::CRawStoreLayout::RecursivelyRegenerateComponentPayload expression: Parameter check failed
[gle=0x80004005]

TelvisTed said:
I'm wondering if it would help to remove the contents in the SoftwareDistribution folder or rename this as done a few times
Click to expand...
No this will not help to fix the problem!

Please provide a 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.
 
Hi,

Please copy the COMPONENTS hive over to another machine and then upload it to WeTransfer.
If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.
 
Unfortunately, the site is blocked. I work for fed agency. And this is a production server. :(
no matter which machine I transfer it to...let me try to find other methods.
 
Please do not circumvent any company restrictions unless you have express permission to share files with us.
 
Hi,

There's no need to use an email adress, just click on the three dots to create a transferlink to post here.
 
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.


Afterwards reboot the server and attempt to update again. If it fails attach a new copy of the CBS logs.
 

Attachments

Per your recommendation, attached is the latest SFCFix file. I will let you know the status after I reboot and try to update again.
Thank you.
 

Attachments

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