[SOLVED] Windows Server 2022 H12 cumulative update KB5033118 failing to install with error code 0x800f081f

T

tattoofreak

Member
Joined
Jan 8, 2024
Posts
12
Hello!
I am facing the same update failure behavior as described here but the issue seems not to be the same as I have already tried to resolve the issue step-by-step with the solutions mentioned in the linked post.
@Maxstar It would be very kind if you could look into the issue I am facing, you seem to have the knowledge here, maybe you can see what is going wrong in my case.
Thanks a bunch in advance!
 

Attachments

Hi,

Please upload the CBS logs as well.

Upload a copy of the CBS folder
  • Open Windows Explorer and browse to the C:\Windows\Logs folder.
  • Right-click on the CBS folder and choose Send to > Compressed (zipped) folder.
  • Now the message will appear, "Windows cannot create the Compressed (zipped) Folder here. Do you want it to be placed on the desktop instead?"
  • Click on the Yes button here.
653a64385d891-618e949e09fef-CBS-Folder.png

  • Attach the file CBS.zip to your next reply.
 
Rich (BB code): 
2023-12-21 07:56:14, Info                  CBS    Loaded Servicing Stack v10.0.19041.3745 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.3745_none_7ded3f327ca60a41\cbscore.dll

The attached CBS.zip is from a Windows 10 system, not Server 2022???
 
Is this server still running an evaluation version, or is it converted to Standard some while ago?
 
Hi,

Open and elevated command prompt, run the following command and copy and paste the result in your next post.
Code: 
DISM /Online /Get-CurrentEdition
 
Code: 
Deployment Image Servicing and Management tool
Version: 10.0.20348.681


Image Version: 10.0.20348.2113


Current edition is:


Current Edition : ServerDatacenter


The operation completed successfully.

Sorry, it was the other way round, I think. I initially installed it as Standard Edition and changed to Datacenter afterwards.
 
Export CBS (Component Based Servicing) hive
  • Click on the Start button and type regedit
  • When you see regedit on the list, right-click on it and select Run as administrator.
  • When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.
    Code: 
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing
  • Once selected, click File > Export....
  • Change the Save as type: to Registry Hive Files (*.*).

    622dbef75cd3a-Export-CBS-hive.png

  • Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
  • Right-click on the saved file and choose Send > Compressed (zipped) Folder.
  • Attach the .ZIP file to your next post.
  • If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.
 
Please attempt to update again and provide the latest CBS logs, with a new copy of the Components Based Servicing hive. (See above post).

Upload a copy of the CBS folder
  • Open Windows Explorer and browse to the C:\Windows\Logs folder.
  • Right-click on the CBS folder and choose Send to > Compressed (zipped) folder.
  • Now the message will appear, "Windows cannot create the Compressed (zipped) Folder here. Do you want it to be placed on the desktop instead?"
  • Click on the Yes button here.
653a64385d891-618e949e09fef-CBS-Folder.png

  • Attach the file CBS.zip to 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 reboot the server and attempt to update. If it fails attach a new copy of the CBS logs.
 

Attachments

Now the original udate is not showing up anymore but two other updates appeared and are failing.

Edit: FYI: I made a snapshot of the VM before applying your patch. Just tell me when you want me to go back to the snapshot.
 

Attachments

Unfortunately, I was expecting this result and this is a known bug when Server 2022 is converted from an evaluation version to Standard or DC..

For now there's no other workaround to fix this, rather than to perform an in-place-upgrade with the retail ISO.

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.

    653263088a599-windows-server-2022-setup.png

  • In the next screen, select the image of the installed Windows Server edition and click Next.
  • Then accept the EULA. To perform a in-place upgrade, you need to check keep personal files and apps. Then click Next.
  • After clicking Next, an upgrade process will start checking for updates, when this is ready click install to start the in-place upgrade.
 
@Maxstar Sorry for being late (my time is very limited currently) and for bothering again. I wanted to start troubleshooting again but I am not able to download the according ISO image the way you told me to do. It is grayed out somehow (see the attached screenshot).
Is there another way I can get the latest image of Windows Server 2022 for that in-place upgrade?
Thank you!
 

Attachments

  • Screenshot 2024-02-16 111231.png
    Screenshot 2024-02-16 111231.png
    40.3 KB · Views: 2
Ok, I think I can find a way so get that image. Did I get this right that after in-place upgrade all following official update realeases should not make me run into the same issue anymore? Or do I always have to use the in-place upgrade for that specific VM for future updates?
 
Last edited:
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