[SOLVED] Server 2022: Updates failing with 0x800f081f

[rampie22]

Good afternoon, Team.

It seems to be a recurring theme with the latest installment of Windows Server (Server 2022).
My previous case, last year, was very similar. The fix you provided really helped me and that particular server has shown no problems since. So I was more than happy to donate
to Sysnative.

Server 2022 (21H2), OS build 20348.2322
Server is failing whilst running updates with error 0x800f081f

I have of course tried all the standard solutions, just in case, this problem is different from the last time.

- Tried to install the update through the MS Catalog Server
- running the built-in troubleshooter
- scan /sfc
- renaming softwaredistribution and catroot2 folder and trying the update again

All efforts to no avail!

I hope you are able to assist. I have attached the CBS log and ComponentsScanner log as well. If there is anything else you require, please let me know.

Best regards,
Ray

 

[Sunfish]

I am a Windows Update Academy trainee on my final stage of training, and I can assist in your update problem(s). My posts will need prior approval so there may be a slight delay with responses.

---

Hello, looking to get some update logs.

Can you please repeat step number 1-4? Windows Update Forum Posting Instructions

 

[rampie22]

G'day Sunfish,

Please find attached the Log files of the repeated steps.
Hope you are able to assist.

Cheers,
Ray

 

[Sunfish]

Step 1
Retrieve Components Hive
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. 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.
3. 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.
4. The file will likely be too large to upload here so please upload to a file sharing service.
5. Attach the file COMPONENTS.zip to your next reply. If the file is too large to attach, upload the COMPONENTS.zip file to www.wetransfer.com and post the link in your next reply.

Step 2
Farbar Recovery
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.

 

[rampie22]

Good morning, Sunfish.

Please find attached the 2 requested files.

Best regards,
Ray

 

[rampie22]

Hey Sunfish,

Just checking whether there is any progress on the thread. You have received the files, but I have not heard back.

Cheers,
Ray

 

[Sunfish]

Apologies on the delay. I have one more portion to finish up.

 

[Sunfish]

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
3. Save any open documents and close all open windows.
4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
6. SFCFix will now process the script.
7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
8. Copy (Ctrl+C) and Paste (Ctrl+V)the contents of this file into your next post for me to analyse please - put
   
   
   tags around the log to break up the text.

 

[rampie22]

Good morning, Sunfish.

Please find attecht the SFCFix.txt file.
It seemed that changes were succesfully processed by SFCFix.
Not sure if you wanted me to check whether this fix already fixed the problem, but I first did a restart and then tried to install the cumulative update again, unfortunately with the same result and windows error code as initially reported.

Is there anything else you need from me?

Regards,
Ray

 

[Sunfish]

Thanks!

Can you send me a copy of the CBS logs to review?

1. Open Windows Explorer and browse to the C:\Windows\Logs folder.
2. Right-click on the CBS folder and choose Send to > Compressed (zipped) folder.
3. Now the message will appear, "Windows cannot create the Compressed (zipped) Folder here. Do you want it to be placed on the desktop instead?"
4. Click on the Yes button here. A file called CBS.zip will be created on your desktop

 

[rampie22]

Please find attached the CBS log.

Cheers,
Ray

 

[Sunfish]

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
3. Save any open documents and close all open windows.
4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
6. SFCFix will now process the script.
7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
8. Copy (Ctrl+C) and Paste (Ctrl+V)the contents of this file into your next post for me to analyse please - put
   
   
   tags around the log to break up the text.

 

[rampie22]

Good morning, Sunfish.

I ran the fix last night, did a restart of the Server and now it seems that the latest Cumulative update for May has been installed normally. For bookkeeping I have attached the SFCFix.txt for you.
So far so good. Please keep the ticket open for now until the next round of Microsoft updates , but first impression is that it is fixed.

Would it be possible to get a short explanation of what the problem was? Of course I can see quite the number of registery (a lot refering to language packs..) changes present in the fix but a bit more explanation would be great.

Great work!

Cheers,
Ray

 

[Sunfish]

Glad you are up and running again!

In regard to leaving the ticket open, I am unsure as I do not mark them solved. I defer this question to @Maxstar

The issue was due to missing manifest files. The reg keys were needed due to references in the registry to the missing manifest files. As for why the manifest files are missing on your system in the first place, I am unsure of the reason. According to others on this site, it is a rather common issue seen on Windows Server 2022.

 

[Sunfish]

Just got word this thread will be marked as solved, but not closed. You should be able to still respond if the error comes back. I will leave notifications on for this thread as well so I don’t miss any comments!

Thanks!

 

[rampie22]

Ok, no worries Sunfish. I would think the problem is solved and will reply if the error comes back.

Thanks again for your assistance and good luck with your final stages of training ;-).

Cheers,
Ray

 

[rampie22]

Good afternoon, Sunfish.

I hope you are keeping well! I have some disappointing news, the problem I had in April has unfortunately returned, the May/June updates were successful but the Cumulative July update was not installing, the exact same error message has reappeared as when I started this thread. But I thought I'd give the August update a chance, unfortunately with the same result. I hope you don't mind me re-opening this thread.

I went through the 4 steps and created the requested files. I hope you are able to assist me again.

Best regards,
Ray

 

[Maxstar]

Hi,

@Sunfish informed me that he is currently very busy, so I will take over this thread.

Please do the following first.

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.

 

[rampie22]

Goedemorgen Maxstar,

No worries, I am just glad someone is able to assist .
Please find attached the components.zip file.

If there is anything else your require, please let me know.

Cheers,
Ray

 

[Maxstar]

Good morning too.

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