Solved Update fails with error: 0x80073712

Well, Patch Tuesday didn't go that well. Most of my machines updated just fine, but my primary system that's running 25H2 was not so happy.



I initially got a different error, so I did a component store cleanup with DISM and an SFC /SCANNOW. I then check to see that both the component store and running system was clean and tried again. Now I get error 0x80073712.

One of the definitions for error code 0x80073712 ERROR_SXS_COMPONENT_STORE_CORRUPT The component store is in an inconsistent state.


Run

dism /online /cleanup-image /startcomponentcleanup

and

dism /online /cleanup-image /restorehealth

Just posted this to another user here as I was kind of surprised to see a couple people having issues installing todays builds as mine went smoothly for a change. Now the last build .5074 I and others had issues with that one and similar install issues as well on a couple earlier builds as well.

Anyhow, the easiest workaround for you to get it installed is to go into Settings/Recovery/Fix problems using Windows Updates and select the Reinstall Now button. That will save all your apps, settings, etc. while doing a repair install and should bump you up to the .6584 new build. Fair warning, it's time consuming so be prepared to wait a while on it even with a fast machine.

As to cause, can't say but I only have WU issues if after the previous update I use DISM component store cleanup to remove reclaimable and/or unreclaimable packages. If I leave those packages alone my following updates go smoothly but when I remove them it's a 50/50 chance of error 0x800f081f or similar. I left the four reclaimable packages from the .5074 update and todays went smooth as silk so I definitely see a trend. Someone posted the other day that those packages shouldn't be removed and can cause errors and problems if they are so I'm leaving them now.

​

FrancoDT said:

Anyhow, the easiest workaround for you to get it installed is to go into Settings/Recovery/Fix problems using Windows Updates and select the Reinstall Now button. That will save all your apps, settings, etc. while doing a repair install and should bump you up to the .6584 new build. Fair warning, it's a time consuming so be prepared to wait a while on it even with a fast machine.

Click to expand...

I was contemplating that exact step.

FrancoDT said:

As to cause, can't say but I only have WU issues if after the previous update I use DISM component store cleanup to remove reclaimable and/or unreclaimable packages. If I leave those packages alone my following updates go smoothly but when I remove them it's a 50/50 chance of error 0x800f081f or similar. I left the four reclaimable packages from the .5074 update and todays went smooth as silk so I definitely see a trend. Someone posted the other day that those packages shouldn't be removed and can cause errors and problems if they are so I'm leaving them now.

Click to expand...

That's something I've not done with this installation.

zbook said:

One of the definitions for error code 0x80073712 ERROR_SXS_COMPONENT_STORE_CORRUPT The component store is in an inconsistent state.


Run

dism /online /cleanup-image /startcomponentcleanup

and

dism /online /cleanup-image /restorehealth

Click to expand...

I did the restorehealth step, I tend not to do component cleanup unless I feel I need to. However, it's worth a shot since the update has failed twice.

Odd... I did both steps, but when I went into Update again, it was busy downloading a different update...

Windows 11 Insider Preview 10.0.26220.5790 (ge_release_upr)

I'll let that finish and see if that changes things.

OK, a little odd... I gave up on the update, did a cleanup of the system and decided to try a system repair. It fired up and immediately decided there was an update. It's not the update that was first offered, but rather this one.



That installed just fine, and now Windows Update says I'm just fine.

I did a and SFC /SCANNOW and found no issues.

The KB5065426 that was previously offered is nowhere to be found in Windows Update now.

To answer the obvious question, the update was simply presented in Windows Update as normal, but my guess it wasn't intended to be an Insider release. That's the only reason I can think that it was failing and suddenly they decided to switch horses and send a different update.

Microsoft presents a way too complicated moving target with the updates nowadays!