2023-12 Cumulative Update for Windows 11 Version 22H2 for x64-based Systems (KB5033375) - Failed

[AthlonXP1800]

The .NET 3.5 files are in the ISO (e.g. D:\sources\sxs)

Enabling in Windows features will download and install from MS, same thing.

I am baffled at the error code and I think I found the solution.

Redirecting

Look like Windows 11 got a bug with install.esd caused installations and DISM repairs failed after downloaded ISO from Microsoft, Media Creation Tool or Rufus.

Someone managed to get DISM repairs fixed by download Tech Bench ISO from rg-adguard.net contained install.wim.

You can covert install.esd to install.wim in Terminal (Admin):

Get-WindowsImage -ImagePath "D:\sources\install.esd"

Export-WindowsImage -SourceImagePath D:\sources\install.esd -SourceIndex 10 -DestinationImagePath C:\esd\install.wim –CheckIntegrity

How to Convert Install.ESD to Install.WIM on Windows – TheITBros Shop

In this short tutorial we will show you how you can easily convert ESD to WIM by using Command Prompt

theitbros.com

After converted to install.wim then delete install.esd and paste install.wim in ISO source folder. Run DISM repair to see if error code 0x800f081f is gone.

 

[Mujja]

@AthlonXP1800 I know you're trying to be helpful but searching generic error codes and pasting the results for an unrelated issue doesn't help. You've done this before in previous threads.

What does an ESD, used for feature updates, have to do with a security update installation failure?

 

[AthlonXP1800]

@AthlonXP1800 I know you're trying to be helpful but searching generic error codes and pasting the results for an unrelated issue doesn't help. You've done this before in previous threads.

What does an ESD, used for feature updates, have to do with a security update installation failure?

I think 2023-12 Cumulative Update for Windows 11 Version 22H2 for x64-based Systems (KB5033375) and 2016-02 Cumulative Update for Windows 10 Version 1511 for x64-based Systems (KB3135173) with the same DISM error code 0x800f081f are both related.

It worth a try to see if it work or not!

 

[Murphy]

I'm going to guess the Windows Update Troubleshooter didn't fix anything as the OP didn't say if they'd tried that already or not, so the next things you probably want to do is try to find out what/why you're getting those errors instead of just wandering around in the dark trying random fixes in the hope of something working.

Open a powershell window and type 'Get-WindowsUpdateLog' that will save a log to the desktop, open it and scroll down to the bottom/newest entries to see if anything (Error entries) stick out. If nothing is marked as errors look for multiple (as in +10-20) of the same entries as they can be a sign of it trying the same thing again and again but failing, then if you don't find any of that you'll have to look at the date/time stamps and try to match up roughly when you last encountered the error with entries in the log.

 

[ssmacc]

Thanks for all the help and suggestions all, really appreciate...After a few weeks of trying several guides and fixes I've given up and just done a clean install, first time in a few years so probably overdue anyway.

Thanks again!