On Fri, 12/20/2024 10:10 AM, John C. wrote:
I'm running 64 bit Windows 10 Pro, build 19045.5131, version 22H2.
Update KB5048652 won't install, keeps downloading and failing with the
error codes 0x8024000b and then later, 0x800f0831.
I've installed the latest servicing stack update and that didn't help.
I've also tried downloading the update from the Windows Update catalog
and manually updating it, but that didn't work. Then I ran a DISC scan
to restore my system's health, but that also didn't work.
Anybody else run into this problem and if so, were you able to overcome
it and if so, would you please tell me how?
TIA
The 0x800f0831 may mean, that it was looking for the manifest
of a previous Cumulative Update for some reason, and not finding it.
It's possible the first install attempt, erased the last cumulative
stored in Servicing\LCU and that is why the second error showed up
on the second try.
I noticed something funny going on, with my Win10 on the 5950X machine.
I could see one of the services burning up cycles. Normally, the memory
amount moves up and down, while it computes supersedence. Well, there
was no disk activity, and also, the amount of memory used was not changing.
I selected a restart, knowing that it had the choice of continuing
the install in the shutting-down state. This did not look like it
was going to work, and it spent at least another half hour in that state, before I started my "doing stuff to break a deadlock" to it, and it
finally moved along.
The suggestions at this point, are:
skim though %WinDir%\Logs\CBS\CBS.log
and look for any sort of sign, that it can be recovered and finish the update.
The other suggestion is a Repair Install, from one of the Windows enthusiast sites.
The missing manifest error, may not be recoverable from a sequential point of view, and the Repair Install is a chance to tip the Windows Update upright again. The update sequence will be different, the "previous" update
will be different, and so on. A second chance, using fresh soup broth.
Not even resetting Windows Update could fix this. An update SHOULD NOT
be using the manifest of a previous update like this. The whole idea
behind Windows Update, is prefaced on wsusscn2.cab (a giant tree of info
about which update depends on which other update). If the turkeys at
Microsoft have abandoned their responsibility to prepare info for
the wsusscn2.cab file, and instead are relying upon "checking some
old and unreliable record keeping scheme", now... how is that
going to turn out ? Great balls of fire.
To do a Repair Install.
1) Run winver.exe and make sure you know which Win10 you are currently on.
Try to match the version, with your Windows 10 install ISO file.
the reason I did not write "use the 19045 one", is some people did not
have the hardware to finish 19045, so the instruction for them, is to
use the same version they are currently running (might be 19044).
My Optiplex 780 could not install 19045, until I put a graphics card in it.
Without the improved graphics card, it kept rolling back 19045.
2) Right click the selected ISO, and select Mount. Alternately, if in File Explorer
and Mount is not offered, try to Open the ISO while in File Explorer.
3) When the virtual DVD drive opens, run the Setup.exe on the virtual DvD.
4) An install will be done, preserving User Files and User Programs.
5) Later, there will be C:\Windows.old and that will either disappear in
ten days time on its own, or you can get rid of it with cleanmgr.exe .
Paul
--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: A noiseless patient Spider (3:633/280.2@fidonet)