Cumulative Update 2024-12 (KB5048652) fails to install

[Jay Freedman]

I have an old laptop, plus two virtual machines in HyperV on a Win11 desktop, all three running Win10 22H2. I've successfully installed Cumulative Update 2024-12 (KB5048652) on one of the VMs. However, the other VM and the laptop have repeatedly failed to install the same update.

The update gets to "Installing... 100%" and then quits with the message that "an update did not install...", and the update history shows error 0x80073701. That's apparently a catchall error for "something interfered, but we can't tell you what it was".

I've attempted installing again after each of these supposed remedies found online:

• Restart or cold boot. (Repeated after each attempt)
• Run the Windows update troubleshooter, several times. The first time it found a missing registry entry. Didn't help.
• Reset the Windows update cache.
• Run DISM /Online /Cleanup-image /Restorehealth followed by sfc /scannow
• Download the update package from the Microsoft catalog and run manually.

The one procedure I haven't tried yet is clean booting Windows, because it's likely to be a huge time-sink without much promise of success.

I'm particularly puzzled by the difference between the two VMs. The one that updated successfully includes Office 2019, while the failed one runs only LibreOffice; otherwise they should be identical. The failed laptop has Microsoft 365 Family and a bunch of other stuff.

I'd appreciate any suggestions for progress!

[HansV]

It looks like you already tried most of the recommended remedies. Did you run

dism /online /cleanup-image /startcomponentcleanup

[Leif]

I'm particularly puzzled by the difference between the two VMs.

There isn't a difference in free space by any chance?

[stuck]

I can't help you but I can tell you that KB5048652 installed without any problem on my Win 10 Pro 22H2 desktop PC.

Ken

[Jay Freedman]

It looks like you already tried most of the recommended remedies. Did you run

dism /online /cleanup-image /startcomponentcleanup

Thanks!

No, the -RestoreHealth parameter was the only one I saw in my down-the-rabbit-hole research. I'll try this and report the results.

[Jay Freedman]

I'm particularly puzzled by the difference between the two VMs.

There isn't a difference in free space by any chance?

Not much. Each VM is allocated 4 GB of memory, of which 550 MB to 1.2 GB is free depending on what processes are running at "idle". I may try bumping the allocation to 8 GB temporarily -- the host has plenty.

[Jay Freedman]

It looks like you already tried most of the recommended remedies. Did you run

dism /online /cleanup-image /startcomponentcleanup

Thanks!

No, the -RestoreHealth parameter was the only one I saw in my down-the-rabbit-hole research. I'll try this and report the results.

Still no success, in the VM or the laptop.

[HansV]

One of all these should have solved it...