[SOLVED] Windows 11 24H2 build 26100.2161 - system tries to install KB5044384, despite it shouldn't

[Snow_]

Hi there,

Recently, I tried to install Windows 11 24H2 build 26100.2033, but it seems something went wrong with my computer since then. Windows Update keeps showing me error 0x800f081f.

Afterwards, I performed an in-place upgrade to build 26100.2161. The system is currently running on build 26100.2161. I was hoping this would resolve the 0x800f081f error, but it didn’t help. Unfortunately, the system still attempts to install update KB5044384, which is already present. In other words, KB5044384 is literally the update for build 26100.2161.

I tried running sfc /scannow, as well as the following commands:
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
DISM /Online /Cleanup-Image /StartComponentCleanup /ResetBase

There were no errors, and everything seems to be fine. I also tried resetting Windows Update multiple times, even using a script called "Reset_Reregister_Windows_Update_Components_for_Windows11.bat". I also removed everything inside C:\Windows\SoftwareDistribution, but to no avail. The error 0x800f081f still persists no matter what I do.

I also tried running ComponentScanner, but I encountered the following error: "You are running a Windows Insider build. ComponentScanner will not run on Insider builds and will now exit."

Does anyone have any idea how to fix this strange issue? Any help would be greatly appreciated.

 

[Windows Update Bot]

Hi @Snow_,

Welcome to Sysnative Forums!

If you haven't already, please review the posting instructions here, and attach the requested log files. Without log files, our helpers will not be able to assist, and this will slow down fixing your machine.

If logs have been already been provided, our team of volunteers will analyse the provided log files to build a fix for your system. Please be aware that this may take several days from your initial post, due to the high volume of threads that we receive.


- Sysnative Windows Update Team

 

[Snow_]

New CBS log attached.

Looks like there's something related to "Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.1742.1.10", but I have no idea how to fix this.

 

[Snow_]

I fixed the issue by using:

dism /Online /Add-Package /PackagePath:YOUR\PATH\TO\Package_for_RollupFix31bf3856ad364e35amd64~~26100.1742.1.10.mum

Make sure to replace "YOUR\PATH\TO" with the actual path to the file.

I attached the file if someone needs it.

Afterwards, I executed the following command at an elevated command prompt:

sfc /scannow && DISM /Online /Cleanup-Image /CheckHealth && DISM /Online /Cleanup-Image /ScanHealth && DISM /Online /Cleanup-Image /RestoreHealth && DISM /Online /Cleanup-Image /StartComponentCleanup /ResetBase

Eventually, I restarted the computer.

Now everything seems fine, and I'm no longer getting the 0x800f081f error in Windows Update.

 

[Snow_]

Well, it looks like I was wrong... So the fix I posted earlier isn't really a fix.

After a while, 0x800f081f error started to pop up again in Windows Update...

System tries again to install KB5044384 and fails with the 0x800f081f error.

I've attached again latest logs from Windows + ComponentsScanner.txt

 

[Snow_]

I created my own SFCFix with the two missing file, that MUM and CAT (see attached). And I applied succesfully the fix to SFCFix.

But this is not enough...

If I run this command:

dism /online /get-packages | findstr /i "Package_for_RollupFix31bf3856ad364e35amd64~~26100.1742.1.10"

I don't see the package installed.

How are we supposed to install this missing package? If I try to install the updates it will fail with errors like 0x80070002.

My guess is that some packages from latest updates were installed, but not this "Package_for_RollupFix31bf3856ad364e35amd64~~26100.1742.1.10".

And even if I want to install regular updates it will fail because it somehow detects the update(s) as installed.

 

[Snow_]

Well... The error 0x800f081f is back!

I also added latest logs.

Please help.

EDIT: I also tried to search packages containing "26100.1742":

 

[Snow_]

I have finally fixed the issue after a long time! I tried multiple times to perform an in-place upgrade to 26100.2161 and even 26100.1742, but it never worked, even though I ran SFC and DISM multiple times. Unfortunately, it was of no use.

So, I tried a new strategy. Since someone DM'd me today facing the same issue, I'll describe below what I did.

My suspicion was that packages related to 26100.1742 were either misinstalled or not correctly recognized by the system. These problematic files were likely carried over during upgrades or were never successfully installed, leading to the same error repeatedly.

The following steps might work for you if you are running a build newer than 26100.1742 and your DISM.log shows something like this:
"Generating failure report for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.1742.1.10, status: 0x800f081f, failure source: Resolve, start state: Absent, target state: Staged, client id: UpdateAgentLCU".

Proceed with caution. I am not responsible if you end up bricking your computer!!!

1) Install all 26100.1742 packages to c:\Windows\servicing\Packages
In my case, many files related to 26100.1742 were missing.
To fix this, you need SFCFix.exe.
Drag the SFCFix.zip file (attached below) over the SFCFix.exe executable and release it.

[All 26100.1742 package files inside SFCFix.zip were extracted from a 26100.2161 ISO build]

2) Add "Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.1742.1.10" to the registry
Even though I was running a build newer than 26100.1742, my computer never recognized "Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.1742.1.10" as installed, even though it should have, considering that 26100.1742 is the prerequisite baseline for later Cumulative Updates.

So, I modified the registry to force the OS to recognize the existence of the package (theoretically, it should exist if you followed Step 1; I've included the MUM and CAT files for Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.1742.1.10 inside SFCFix.zip).

Find the attached "add-missing-package_for_rollupfix-26100.1742.zip" and modify the .REG file for your system. You need to change the "InstallUser" value to match your system.

For example, search for "Package_for_RollupFix" in "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages" and use the "InstallUser" value you find there for your new key at:
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.1742.1.10".

After modifying the .REG file locally, double-click it, and then press "Yes" to import the changes into your registry.

3) In-place "upgrade" to 26100.1742
This is essentially a downgrade, and you'll need the 26100.1742 ISO for this step. Perform an in-place "upgrade" to 26100.1742.

Once the system is running 26100.1742, execute the following commands:

sfc /scannow && DISM /Online /Cleanup-Image /CheckHealth && DISM /Online /Cleanup-Image /ScanHealth && DISM /Online /Cleanup-Image /RestoreHealth && DISM /Online /Cleanup-Image /AnalyzeComponentStore && DISM /Online /Cleanup-Image /StartComponentCleanup

Then, go to Windows Update and install all available updates, including KB5043080 and KB5044384.

In my case, I couldn't install KB5043080 right away, nor KB5044384. IIRC, I even received the 0x800736b3 error in Windows Update.

In case you encounter the 0x800736b3 error, you can run the following command:

dism /online /cleanup-image /restorehealth /source:wim:G:\sources\install.wim:1 /limitaccess

[Make sure to replace "G:" with the drive letter of your mounted 26100.1742 ISO file]

After running this, reboot your computer.

I had to reboot the system multiple times. Eventually, I managed to install KB5043080, and after another reboot, I was able to successfully install KB5044384.

Finally, my system is now fixed: