[SOLVED] Server 2019, Updates / .net 4.8 Install Failed

[TR3NT]

Good Morning Team,

Honestly what you guys do is amazing I have read of many of threads trying to find a fix for my current issue but it seems I and M$ support are at a loss. I have a server 2019 box here (actually a imaged server which I don't have a rollback for as it seems the issue started a long time ago.
How I discovered the issue (Tried to install .net 4.8). it failed with this message:

https://imgur.com/HZiXrsR

Also during troubleshooting i found the below.

https://imgur.com/a/fm1v1h6

I have also attached the related CBS, DISM, COMPONENTS in the hope this aids in troubleshooting.
I will also re run the DISM etc and share the logs once they complete. However they have in the past not helped me but I also don't have an expert eye / understanding of the logs.
Logs-V2.zip

Thanks in advance for your assistance.

 

[Maxstar]

2022-10-21 08:17:25, Error                 CSI    0000035f@2022/10/20:21:17:25.892 (F) Attempting to mark store corrupt with category [l:15 ml:16]'CorruptManifest'[gle=0x80004005]
2022-10-21 08:17:25, Error                 CSI    00000360@2022/10/20:21:17:25.894 (F) onecore\base\wcp\componentstore\storelayout.cpp(3218): Store corruption detected in function ComponentStore::CRawStoreLayout::FetchManifestContent expression: 0
  MissingFileSystemResource on resource '\winsxs\manifests\amd64_netfx4-workflowserv..ormancecounters_dll_b03f5f7f11d50a3a_4.0.15713.438_none_aca2fc3ed00c8cee.manifest'[gle=0x80004005]

Hi and welcome to Sysnative,

Step 1. Download

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.

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

DISM /online /cleanup-image /RestoreHealth

 

[TR3NT]

Hi Maxstar, I cant thanks you enough for your help here really! DISM command did fail see below. Attached all requested files also. thanks for your help!

c:\Temp>DISM /online /cleanup-image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.3406

Image Version: 10.0.17763.3532

[==========================100.0%==========================]
Error: 0x800f0907

DISM failed. No operation was performed.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

 

[Maxstar]

Here's the next fix, to replace the first set of missing payload files.

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.

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

DISM /online /cleanup-image /RestoreHealth

 

[TR3NT]

Thanks again for your help Maxstar,

Please see attached error logs V5 is post DISM and V6 is post attempt of .net 4.8 install.

 

[Maxstar]

Please don't perform anything else at the moment, now we have two CBS logs with different failures..

For the next fix ï'll need to setup a VM to gather missing payload from some older updates.

 

[TR3NT]

Please don't perform anything else at the moment, now we have two CBS logs with different failures..

For the next fix ï'll need to setup a VM to gather missing payload from some older updates.

Ah I see what your saying, no worries will await the payload, thankyou so much :).

 

[Maxstar]

2022-10-22 22:18:33, Error                 CSI    0000035f@2022/10/22:11:18:33.254 (F) onecore\base\wcp\componentstore\versionedindex.cpp(3604): Store corruption detected in function ComponentStore::CRawStoreLayout::CheckFamilyIndexForDeadWinnerComponent expression: (null)
  MissingWinningComponentKey on resource 'msil_uiautomationclient_31bf3856ad364e35_4.0.15713.610_none_1b59678639ce6be5'[gle=0x80004005]

Edit:

Here's the next fix with replacement files, and to restore the missing subkey in the COMPONENTS hive.

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.

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

DISM /online /cleanup-image /RestoreHealth

 

[TR3NT]

Thanks so much for your help Maxstar :)

Please find attached logs as requested.

 

[Maxstar]

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.

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

DISM /online /cleanup-image /RestoreHealth

 

[TR3NT]

Thanks for your ongoing help Maxstar! Please see attached logs,

 

[Maxstar]

Hi,

The latest CBS reports the following amount of corruptions: CSI Payload Corruption: 31465.

If you have a similar server (clone) you could try to run DISM with that server as source!

DISM /Online /Cleanup-Image /RestoreHealth /Source:\\ServerName\C$\Windows\WinSxS\ /LimitAccess

 

[TR3NT]

Thanks again Maxstar :)
Attached are the most recent logs.

 

[Maxstar]

2022-10-25 19:21:57, Info                  CBS    (p)    CSI Payload Corrupt    (n)            msil_uiautomationclient_31bf3856ad364e35_4.0.15713.610_none_1b59678639ce6be5\UIAutomationClient.dll
2022-10-25 19:21:57, Info                  CBS    Repair failed: Missing replacement payload.

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.

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

DISM /online /cleanup-image /RestoreHealth

 

[TR3NT]

Thanks heaps Maxstar! where on earth did you find that one? I checked like 20 servers and so much google even ran up my own VMs and you found it just like that! Log is looking better?

 

[Maxstar]

That component is a part of: 2021-01 Cumulatieve update voor .NET Framework 3.5 en 4.7.2 voor Windows Server 2019 voor x64 (KB4586875).

2022-10-25 20:12:06, Info                  CSI    00000007 Warning: Unable to repair manifest for component ([l:97 ml:140]'amd64_netfx4-uiautomationclientsideproviders_b03f5f7f11d50a3a_4.0.15713.610_none_51c7703fa1e22157') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-10-25 20:12:16, Info                  CSI    00000008 Warning: Unable to repair manifest for component ([l:78 ml:140]'msil_system.configuration_b03f5f7f11d50a3a_4.0.15713.481_none_c2873af8c255019e') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-10-25 20:12:26, Info                  CSI    00000009 Warning: Unable to repair manifest for component ([l:88 ml:140]'msil_system.web.applicationservices_31bf3856ad364e35_4.0.15713.545_none_0a76e5ab4fdfe211') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-10-25 20:12:53, Info                  CSI    0000000a Warning: Unable to repair manifest for component ([l:75 ml:140]'x86_netfx4-system.core_b03f5f7f11d50a3a_4.0.15713.610_none_7e4dfed50e4ab404') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-10-25 20:13:39, Info                  CSI    0000000b Warning: Unable to repair manifest for component ([l:79 ml:140]'amd64_netfx4-system.speech_b03f5f7f11d50a3a_4.0.15713.492_none_472fdd7a8a1f77bb') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-10-25 20:14:11, Info                  CSI    0000000c Warning: Unable to repair manifest for component ([l:81 ml:140]'amd64_netfx4-system.security_b03f5f7f11d50a3a_4.0.15713.571_none_3a93e8beb1fe13e9') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-10-25 20:14:33, Info                  CSI    0000000d Warning: Unable to repair manifest for component ([l:80 ml:140]'x86_netfx-msbuild_data_files_b03f5f7f11d50a3a_10.0.17763.1_none_38abb6a6db59d373') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-10-25 20:14:33, Info                  CSI    0000000e Warning: Unable to repair manifest for component ([l:76 ml:140]'x86_netfx-sbs_iehost_dll_31bf3856ad364e35_10.0.17763.1_none_ac5f7903e2362213') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-10-25 20:14:33, Info                  CSI    0000000f Warning: Unable to repair manifest for component ([l:96 ml:140]'x86_microsoft.vsa.vb.co..mprocessor.registry_31bf3856ad364e35_10.0.17763.1_none_96da4993e186f66f') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-10-25 20:16:16, Warning               CBS    Current tick count: 800 lower than last tick count: 1089. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
2022-10-25 20:16:16, Error                 CSI    00000010@2022/10/25:09:16:16.217 (F) Attempting to mark store corrupt with category [l:15 ml:16]'CorruptManifest'[gle=0x80004005]

Here's the next fix to replace the missing *.manifest-files.

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.

• 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, please try to install .NET Framework 4.8 and let me know the result.

 

[TR3NT]

Sorry did I miss the attachment here? So keen to try :)

 

[Maxstar]

Oops, here's the attachement...

 

[TR3NT]

Thankyou! Heres the next attachment. One post .net not working and one dism afterwards.

 

[Maxstar]

2022-10-25 22:12:20, Info                  CSI    000003e8 Warning: Unable to repair payload file ([l:35]'UIAutomationClientsideProviders.dll') for component ([l:97 ml:140]'amd64_netfx4-uiautomationclientsideproviders_b03f5f7f11d50a3a_4.0.15713.610_none_51c7703fa1e22157') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-10-25 22:12:33, Info                  CSI    000003e9 Warning: Unable to repair payload file ([l:24]'System.Configuration.dll') for component ([l:78 ml:140]'msil_system.configuration_b03f5f7f11d50a3a_4.0.15713.481_none_c2873af8c255019e') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-10-25 22:12:45, Info                  CSI    000003ea Warning: Unable to repair payload file ([l:34]'System.Web.ApplicationServices.dll') for component ([l:88 ml:140]'msil_system.web.applicationservices_31bf3856ad364e35_4.0.15713.545_none_0a76e5ab4fdfe211') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-10-25 22:13:14, Info                  CSI    000003eb Warning: Unable to repair payload file ([l:15]'System.Core.dll') for component ([l:75 ml:140]'x86_netfx4-system.core_b03f5f7f11d50a3a_4.0.15713.610_none_7e4dfed50e4ab404') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-10-25 22:14:03, Info                  CSI    000003ec Warning: Unable to repair payload file ([l:17]'System.Speech.dll') for component ([l:79 ml:140]'amd64_netfx4-system.speech_b03f5f7f11d50a3a_4.0.15713.492_none_472fdd7a8a1f77bb') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-10-25 22:14:29, Info                  CSI    000003ed Warning: Unable to repair payload file ([l:19]'System.Security.dll') for component ([l:81 ml:140]'amd64_netfx4-system.security_b03f5f7f11d50a3a_4.0.15713.571_none_3a93e8beb1fe13e9') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-10-25 22:14:48, Info                  CSI    000003ee Warning: Unable to repair payload file ([l:22]'Microsoft.Common.Tasks') for component ([l:80 ml:140]'x86_netfx-msbuild_data_files_b03f5f7f11d50a3a_10.0.17763.1_none_38abb6a6db59d373') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-10-25 22:14:48, Info                  CSI    000003ef Warning: Unable to repair payload file ([l:14]'sbs_iehost.dll') for component ([l:76 ml:140]'x86_netfx-sbs_iehost_dll_31bf3856ad364e35_10.0.17763.1_none_ac5f7903e2362213') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-10-25 22:16:10, Error                 CSI    000003f0 (F) Failed to clear possible corruptions file with status STATUS_SUCCESS and disposition 3[gle=0x80004005]
2022-10-25 22:16:10, Error                 CSI    000003f1@2022/10/25:11:16:10.689 (F) Attempting to mark store corrupt with category [l:18 ml:19]'CorruptPayloadFile'[gle=0x80004005]

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.

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

DISM /online /cleanup-image /RestoreHealth