[SOLVED] Issues with updating Server 2022 | 0x800f081f(DISM) | 0x80070490

FransJvr

New member
Joined
Jan 15, 2024
Posts
2
Hey Guys,

We have been having some issues with one of our 2022 servers failing to install the new CU's.

Troubleshooting this issue I have found there is quite a bit of errors being thrown up when running DISM.

Code:
2023-12-01 09:29:18, Info                  CBS    Total Detected Corruption:    396
2023-12-01 09:29:18, Info                  CBS        CBS Manifest Corruption:    396
2023-12-01 09:29:18, Info                  CBS        CBS Metadata Corruption:    0
2023-12-01 09:29:18, Info                  CBS        CSI Manifest Corruption:    0
2023-12-01 09:29:18, Info                  CBS        CSI Metadata Corruption:    0
2023-12-01 09:29:18, Info                  CBS        CSI Payload Corruption:    0
2023-12-01 09:29:18, Info                  CBS    Total Repaired Corruption:    0
2023-12-01 09:29:18, Info                  CBS        CBS Manifest Repaired:    0
2023-12-01 09:29:18, Info                  CBS        CSI Manifest Repaired:    0
2023-12-01 09:29:18, Info                  CBS        CSI Payload Repaired:    0
2023-12-01 09:29:18, Info                  CBS        CSI Store Metadata refreshed:    True
2023-12-01 09:29:18, Info                  CBS    Staged Packages:
2023-12-01 09:29:18, Info                  CBS        CBS Staged packages:    0
2023-12-01 09:29:18, Info                  CBS        CBS Staged packages removed:    0

with a few examples being:

Code:
2023-12-05 08:52:17, Info                  CBS    Checking System Update Readiness.
2023-12-05 08:52:17, Info                  CBS   
2023-12-05 08:52:17, Info                  CBS    (p)    CBS Catalog Missing    (n)            Containers-Dynamic-Image-Package~31bf3856ad364e35~amd64~~10.0.20348.1906
2023-12-05 08:52:17, Info                  CBS    Repair failed: Missing replacement mum/cat pair.
2023-12-05 08:52:17, Info                  CBS    (p)    CBS Catalog Missing    (n)            Containers-Server-HNS-Package~31bf3856ad364e35~amd64~~10.0.20348.1906
2023-12-05 08:52:17, Info                  CBS    Repair failed: Missing replacement mum/cat pair.
2023-12-05 08:52:17, Info                  CBS    (p)    CBS Catalog Missing    (n)            Containers-Server-merged-Package~31bf3856ad364e35~amd64~~10.0.20348.1850
2023-12-05 08:52:17, Info                  CBS    Repair failed: Missing replacement mum/cat pair.
2023-12-05 08:52:17, Info                  CBS    (p)    CBS Catalog Missing    (n)            Containers-Server-Package~31bf3856ad364e35~amd64~~10.0.20348.1906
2023-12-05 08:52:17, Info                  CBS    Repair failed: Missing replacement mum/cat pair.
2023-12-05 08:52:17, Info                  CBS    (p)    CBS Catalog Missing    (n)            Containers-Server-SDN-Package~31bf3856ad364e35~amd64~~10.0.20348.1850
2023-12-05 08:52:17, Info                  CBS    Repair failed: Missing replacement mum/cat pair.
2023-12-05 08:52:17, Info                  CBS    (p)    CBS Catalog Missing    (n)            HyperV-Chipset-Package~31bf3856ad364e35~amd64~~10.0.20348.1726

I have tried doing a DISM repair pointing at a new ISO, and running the below pointing to a up to date similar 2022 server:

Dism /Online /Cleanup-Image /RestoreHealth /Source:f:\sources\sxs /LimitAccess

Where f is mapped to \\othermachine\c:\windows\servicing\packages
We also tried mapping it to Manifests and Winsxs but we could not get this repaired this way.

Lastly, we were advised to wait for the latest CU(now for Jan 24) but this is still failing on our end.

I have attached CBS/DISM logs and the Componentscanner logs, not sure if anything else is needed in this instance?
 

Attachments

Hi and welcome to Sysnative,

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

Hi and welcome to Sysnative,

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
Hey Maxtar,

I just wanted to thank you for the assistance, there were another 22 files after running your fix, but thanks to seeing how you did it I was able to pull these files from updates and other servers.

Not only did you help me with creating the files, but you also taught me how to fix this in the future.

Again, thank you and I really do appreciate the assistance!
 
Hi,

You're welcome. Glad you managed to resolve the remaining issues. See also this article for more information how to resolve these kind of issues.
I will mark this thread as solved.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top