[SOLVED] Update issue on several Windows Server 2022 (0x800f081f)

N

nk_007

Contributor
Joined
Dec 17, 2023
Posts
11
Hi,

i do have several Windows 2022 Servers which i'm struggling to update for weeks already. The Error code 0x800f081f sometimes differs but at the end it does not get the CU installed.

Tried all the hints related to this topic posted on the web already but without success. Hope to get some help from you guys.
Did follow your posting instructions and attached as requested.

Thanks!
 

Attachments

Hi and welcome to Sysnative,

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.
 
Hi,

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.

Afterwards attempt to update. If it fails attach a new copy of the CBS logs.
 

Attachments

Hi,

Each time the CBS log shows only one corrupted component, so here's the next fix.

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.

Afterwards attempt to update. If it fails attach a new copy of the CBS logs.
 

Attachments

Hi,

Unfortunately, there's no public tutorial to fix such kind of corruptions due to the complexity. So here's the next fix.

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.

Afterwards attempt to update. If it fails attach a new copy of the CBS logs.
 

Attachments

It seems a large number of components are missing / corrupted...

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.

Afterwards attempt to update. If it fails attach a new copy of the CBS logs.
 

Attachments

Open an elevated command prompt and run the following command. Attach Dirlist.txt to your next post.
Code: 
dir /s /a %systemroot%\WinSxS\amd64_microsoft-windows-n..ller-imos-unmanaged_31bf3856ad364e35_10.0.20348.1_none_9e424e90cc60f89f > "%userprofile%\Desktop\Dirlist.txt"
 
no. pretty stable. it is not the only one we are having issues. different installations different locations. this is just one.
 
Are all those servers configured based on a particular template / image?
 
different VMWare templates. but most deployments work nice and some - minor - do not.
 
Hmm, since a huge number of RTM components are missing (registry keys, payload and manifest files) I would suggest to perform an in-place-upgrade. This is the quickest way to resolve this issue, manually fixing could be time consuming for both of us.

In-place upgrade Server 2022 with the MSDN (Retail) ISO.
  • Navigate to the URL below and sign-in with your MSDN registered account.
  • https://msdn.microsoft.com/subscriptions/securedownloads/
  • Use the search field to find and download the correct ISO file.
  • Mount the Windows Server ISO and run Setup.exe.
  • Use the option Download updates, drivers, and optional features (recommended) and click Next.
  • Note: If you don't want to update during the in-place upgrade, press Change how setup downloads updates and select Not right now - !!! Not recommended !!!
  • When the following screen is prompted enter your (25 digit) product key. Note: Do not use the public KMS key as listed here.
 
Great, in cases like this it is the most efficient way to get a server up and running again...(y)
 
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