After slipstreaming Windows 11 we get for every patch error "0x800f0838"

Stefan Brutscher 0 Reputation points
2025-02-02T10:06:35.1933333+00:00

Hi, we normally Slipstream the install.wim File for the Windows unattend Installations.

Now, with Windows 11 24H2 we can't use this anymore, because every Image we tested with Slipstreaming afterward the client can't patch anymore. Every CU Update reported the Error "0x800f0838".

Normally we integrate directly .NET 3.5 and add and remove some Features. But its not the .NET or the Features that have the problem. Every change of the WIM File brings up that the Windows Installation can't be updated with the CU Patches.

If done test with several Clients and all different ISO Builds from Windows 11 24H2. All other Windows 11 Build before 24H2 works fine.

Seems, that there is a bug.

Kind regards

Stefan

Windows
Windows
A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.
5,766 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Daisy Zhou 28,736 Reputation points Microsoft Vendor
    2025-02-05T07:42:14.8566667+00:00

    Hello

    Thank you for posting in Q&A forum.

    The error code "0x800f0838" you're encountering after slipstreaming Windows 11 patches typically indicates issues with dependencies or the Windows servicing stack.

    Here are some steps you can try:

    1. Make sure there is enough disk space available to install the updates. You can use Disk Cleanup to free up space or extend the C: partition if necessary.
    2. Use the built-in Windows Update Troubleshooter to detect and fix issues related to Windows updates. Go to Settings > Update & Security > Troubleshoot > Additional troubleshooters and select Windows Update.
    3. Reset Windows Update Components:

    Open Command Prompt as an administrator and run the following commands:

    net stop wuauserv

    net stop cryptSvc

    net stop bits

    net stop msiserver

    ren C:\Windows\SoftwareDistribution SoftwareDistribution.old

    ren C:\Windows\System32\catroot2 catroot2.old

    net start wuauserv

    net start cryptSvc

    net start bits

    net start msiserver

    After running these commands, try updating again.

    1. Use DISM Tool:

    Run the following command in Command Prompt as an administrator:

    DISM /Online /Cleanup-Image /RestoreHealth

    After the process completes, restart your computer and try updating again.

    1. If the above steps do not work, you can try manually downloading and installing the updates from the Microsoft Update Catalog. Search for the specific KB numbers and download the appropriate files for your system.
    2. If you have installed any Features On Demand or language packs, they might be causing the issue. Try removing them temporarily and then attempt the update again.

    I hope the information above is helpful.

    If you have any questions or concerns, please feel free to let us know.

    Best Regards,

    Daisy Zhou

    ============================================

    If the Answer is helpful, please click "Accept Answer" and upvote it.


  2. André Kießling 0 Reputation points
    2025-02-05T14:29:59.13+00:00

    Hello together,

    we have exactly the same issue since some day with Windows 11 24H2 and CU Update, because we are also Slipstream the install.wim file for the Windows unattend Installations since Windows 10.

    All other Update via our Software distribution with included Patch Management like January 28, 2025-KB5050577 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11, version 24H2 or Windows Malicious Software Removal Tool (KB890830) can be installed without any problems.

    I've tested this on different clients with DE- and US-Windows 11 24H2 image, but every time the same error.

    The described steps not working on several clients for me.

    After I have executed these as described and tried to install one of the CU updates (windows11.0-kb5050009-x64 or windows11.0-kb5050094-x64) manually or via our patch management, the error unfortunately persists.

    Further possible solutions would be very welcome.

    Best regards from Germany (Bavaria)

    André Kießling

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.