[SOLVED] (Win11 24H2 build 26100.2314) - Error code 0x800f0991 when installing every cumulative updates

MaXeLL

New member
Joined
Dec 4, 2024
Posts
4
Hello,

i've upgraded three computers from Win11 23H2 to Win11 24H2, two supported and one with an unsupported CPU, and now everytime I try to update the OS with the latest cumulative updates I receive the error code 0x800f0991. The strange thing is my main computer (the fourth one) didn't faced the same issue.

I followed the posting instructions and I have uploaded two CBS.log files and the ComponentScanner.txt.

"sfc /scannow", "Dism /Online /Cleanup-Image /RestoreHealth" and the component scanner app gave no error, everything fine.

CBS (1) is after I tried the command above and the component scanner, while CBS (2) is after i tried updating the OS.

Thank you in advance for any help you could give me.
 

Attachments

Hi @MaXeLL,

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
 
And this is the CBS log after i tried the command

Dism.exe /online /Cleanup-Image /StartComponentCleanup

I get error code 0x800f081f.
 

Attachments

Ok, i'm marking this thread solved because i fixed the problem.

The issue was the same as this thread:


I searched for build .1742 files on computers with the issue and, in fact, were missing, instead in the main computer were present.

I cooked a new ISO with the latest cumulative update KB5048667 (OS Build 26100.2605) thanks to uupdump.net and i've done an in-place upgrade.

Then I verified if build .1742 were present and they did! Finally i've done updates and DISM checks, all went ok, no errors at all.

With the january updates i'll make a new report to confirm if I have definitively resolved the issue.
 
With the january updates i'll make a new report to confirm if I have definitively resolved the issue.
Bumping this thread just to report that the January Windows updates worked as expected, so the solution I found (simply doing an in-place upgrade after creating a new Windows 11 rom on uupdump.net) was the correct one.

Maybe this could help anyone who has this issue.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top