[SOLVED] windows server 2022 - CU update fails - slb-mux-deployment

S

Stijn Wauters

Member
Joined
Aug 22, 2018
Posts
21
Hi,

Once again, new CU, new problems with updating it.

I hope you can help me once again.

Server: Windows Server 2022
Error when installing latest CU
"There were some problems installing updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x800f081f)"

In attachment CBS.zip and componentsScanner.txt

I took a look in the CBS logs:
2025-01-10 15:48:46, Info CSI 0000022c Warning: Unable to repair manifest for component ([l:97 ml:140]'amd64_microsoft-windows-slb-mux-deployment_31bf3856ad364e35_10.0.20348.1547_none_68ce0f932e0be5a5') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2025-01-10 15:50:48, Info CSI 0000022d Warning: Unable to repair manifest for component ([l:101 ml:140]'amd64_microsoft-windows-s..oyment-languagepack_31bf3856ad364e35_10.0.20348.946_en-us_4963a3eab6afee1f') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
 

Attachments

Hi @Stijn Wauters,

Welcome to Sysnative Forums!

If you haven't already, please review the posting instructions here, and attach the requested log files. Without log files, our helpers will not be able to assist, and this will slow down fixing your machine.

If logs have been already been provided, our team of volunteers will analyse the provided log files to build a fix for your system. Please be aware that this may take several days from your initial post, due to the high volume of threads that we receive.


- Sysnative Windows Update Team
 
Hi,

Please upload a new copy of the CBS logs, the ZIP-file in the first post is corrupted.
 
Hi,

Yes, but 7zip shows also an error:

Rich (BB code): 
D:\Forum\Stijn Wauters\CBS.zip
Kopfout
Start van het archief niet bevestigd
Waarschuwingen:
Er zijn nog gegevens na het einde van de payload
Gegevensfout : CBS\CbsPersist_20250110140702.log

But, here's the first fix.

Download
67139f7e69a58-SFCFix-ico.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.
67139f52b3c1e-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

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


Step 3. Download
61f7aba7309a1-ComponentsScanner_Icon.png
ComponentsScanner and save it to your desktop.
  • Right-click ComponentsScanner.exe and select "Run as administrator", click Yes on the UAC (User Account Control) prompt which appears.
  • Follow the on-screen instructions.
  • Once complete, a report will be saved to your desktop called ComponentsScanner.txt.
  • Post the logfile ComponentsScanner.txt as attachment into your next reply.
 

Attachments

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.
67139f52b3c1e-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,

Open an elevated prompt, run the following command and copy paste the result in your next post.
Code: 
certutil -hashfile C:\Windows\Servicing\Packages\Microsoft-Windows-AppManagement-AppV-Package~31bf3856ad364e35~amd64~~10.0.20348.2849.cat SHA256
 
Hi,

result from command:
Code: 
SHA256 hash of C:\Windows\Servicing\Packages\Microsoft-Windows-AppManagement-AppV-Package~31bf3856ad364e35~amd64~~10.0.20348.2849.cat:
6da1c331bda1bc5a47c264631f09825544d6ed98c64ecf71f58ce7c968544e83
CertUtil: -hashfile command completed successfully.
 
Hi,

Please reboot the server and attempt to update again, if it fails attach a new copy of the CBS logs.
 
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 attempt to update. If it fails attach a new copy of the CBS logs.
 

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