Welcome to Microsoft Q&A!
Thank you for reaching out and for providing detailed information about the issue.
Based on the symptoms described, the issue may be related to corruption in the Windows component store or missing servicing files. Windows updates may fail when corruption is present, and DISM can help repair certain Windows corruption errors.
Since this server does not have Internet access, you can use a known-good repair source running the same Windows Server operating system version. The following example when a working Windows installation is used as the repair source:
DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:\\servername\c$\windows /LimitAccess
Replace servername with the computer name of the system being used as the repair source. The repair-source computer must be running the same operating system version.
If DISM reports that the restore operation completed successfully, run:
sfc /scannow
Afterward, restart the server if appropriate and retry the cumulative update.
The above procedure uses DISM to service and repair the local Windows image. However, since DISM is already failing in your environment, the exact cause cannot be determined from the symptoms alone. This is a recommendation to review:
C:\Windows\Logs\CBS\CBS.log
The CBS log records issues that DISM found or repaired and can help identify missing or corrupted components.
If DISM continues to fail even after you provide a correct repair source, the issue has reached a point where further investigation is beyond what can reasonably be performed through Microsoft Q&A.
Because Microsoft Q&A is a public community-based forum. I can provide documented troubleshooting guidance and help explain supported repair approaches, but I do not have access to your server environment and cannot perform the detailed, environment-specific servicing investigation that may be required in this situation. In particular, cases involving persistent component-store corruption can require detailed review of servicing logs and the specific state of the affected server before the appropriate recovery action can be determined.
For that reason, if the documented DISM repair continues to fail, I would recommend opening a Microsoft Support request rather than continuing with additional repair changes through the forum. A support engineer can work with the diagnostic information from your affected environment.
I hope this helps clarify the appropriate repair path
Reference:
Fix Windows Update corruptions and installation failures - Windows Server | Microsoft Learn
If you find it useful, please click Accept Answer.
Thank you for choosing Microsoft Q&A.